mount: wrong fs type, bad option, bad superblock on /dev/hdc1,

mount: wrong fs type, bad option, bad superblock on /dev/hdc1,

Post by Till Halbac » Thu, 18 Oct 2001 20:31:10



Experts

There once was a system administrator (not me) who made an unknown file
system on a disk. The disk is rather old, IBM 8.4 GB, and the fdisk
listing looks like:

Disk /dev/hdc (Sun disk label): 10 heads, 320 sectors, 11199 cylinders
Units = cylinders of 3200 * 512 bytes
   Device Flag    Start       End    Blocks   Id  System
/dev/hdc1             0     11167  17867200   83  Linux native
/dev/hdc2  u      11167     11199     51200   82  Linux swap
/dev/hdc3             0     11199  17918400    5  Whole disk

Anyway, with df, I saw the right amount of available space (8.3 MB
something), so I didn't care and copied some GB with important data on
it. Now I upgradet my version to RH-7.1, and what happens?

mount -o ro,ufstype=sun -t ufs /dev/hdc1 /mnt/private/
mount: wrong fs type, bad option, bad superblock on /dev/hdc1,
       or too many mounted file systems
       (could this be the IDE device where you in fact use
       ide-scsi so that sr0 or sda or so is needed?)

In fact, I tried all systems, including ext2, and nothing is working. I
would really appreciate appropriate help here. Hopefully, I gave you all
the necessary information, otherwise you have to tell me. Thanks in
advance,

Till

--
E-mails from unregistered mailing lists will not get through.

 
 
 

mount: wrong fs type, bad option, bad superblock on /dev/hdc1,

Post by David Efflan » Fri, 19 Oct 2001 11:54:44



> Experts

> There once was a system administrator (not me) who made an unknown file
> system on a disk. The disk is rather old, IBM 8.4 GB, and the fdisk
> listing looks like:

> Disk /dev/hdc (Sun disk label): 10 heads, 320 sectors, 11199 cylinders
> Units = cylinders of 3200 * 512 bytes
>    Device Flag    Start       End    Blocks   Id  System
> /dev/hdc1             0     11167  17867200   83  Linux native
> /dev/hdc2  u      11167     11199     51200   82  Linux swap
> /dev/hdc3             0     11199  17918400    5  Whole disk

> Anyway, with df, I saw the right amount of available space (8.3 MB
> something), so I didn't care and copied some GB with important data on
> it. Now I upgradet my version to RH-7.1, and what happens?

> mount -o ro,ufstype=sun -t ufs /dev/hdc1 /mnt/private/
> mount: wrong fs type, bad option, bad superblock on /dev/hdc1,
>        or too many mounted file systems
>        (could this be the IDE device where you in fact use
>        ide-scsi so that sr0 or sda or so is needed?)

> In fact, I tried all systems, including ext2, and nothing is working. I
> would really appreciate appropriate help here. Hopefully, I gave you all
> the necessary information, otherwise you have to tell me. Thanks in
> advance,

Have you checked your kernel configuration to see if you have the
necessary sun and ufs filesystem support (built in or as modules)?

--
David Efflandt - All spam is ignored - http://www.de-srv.com/
http://www.autox.chicago.il.us/  http://www.berniesfloral.net/
http://cgi-help.virtualave.net/  http://hammer.prohosting.com/~cgi-wiz/

 
 
 

1. NFS wrong fs type, bad option, bad superblock, etc

When I try to mount a TCPware VMS NFS export, I get this message:
"mount: wrong fs type, bad option, bad superblock on
server.domain.com:/mnt/mountpoint,
or too many mounted file systems . "
I have an NT box running Intergraph NFS that can successfully mount this
export.
I can also mount the NT NFS export with the Caldera
2.2 Linux box using the same mount command syntax.
Anyone get this message and get it to work?

Thanks,

John Eberhardt

2. GETPWENT()

3. 'wrong fs type or bad superblock on /dev/hdb1'

4. Error message in starting X

5. Help wanted: mount: wrong fs type or bad superblock

6. Diamond Stealth Pro 2Mb VRAM

7. bad partition on good disk won't mount or fsck (bad magic number/superblock)

8. yellow tinted screen corruption

9. wrong fs/bad superblock..help!

10. wrong fs/bad superblock..huh?

11. Bad Superblock -> Bad Magic Number ->Segmentation fault?

12. mount: wrong fs type,... What's wrong?

13. growfs says: Bad superblock; wrong magic number