mount: wrong fs type, bad option, bad superblock on /dev/sdc1, New hard drive install
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've managed to get as far as the final command on that page:
Quote:
mount -t ext3 /dev/hdb1 /opt2
except for my situation it looks like:
Quote:
mount -t ext3 /dev/sdc1 /opt2
that command is giving me this error:
Quote:
mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
says to check syslog, here is the result of that:
Quote:
[ 12.759076] e1000e 0000:00:19.0: irq 41 for MSI/MSI-X
[ 14.105874] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[ 14.105881] e1000e 0000:00:19.0: eth0: 10/100 speed: disabling TSO
[ 14.191824] NET: Registered protocol family 17
[ 18.530315] bootsplash: status on console 0 changed to on
[ 149.096427] EXT4-fs (sdb2): re-mounted. Opts: acl,user_xattr,commit=0
[ 149.305466] EXT4-fs (sdb3): re-mounted. Opts: acl,user_xattr,commit=0
[ 298.263456] attempt to access beyond end of device
[ 298.263461] sdc1: rw=0, want=4, limit=2
[ 298.263466] EXT3-fs (sdc1): error: unable to read superblock
last three entries there looking fishy. first of last 3 might suggest new drive is not partitioned correct.
I'm guessing something is messed up with partition table, or new drive is simply not partitioned correctly?
here is the result of fdisk -l:
Quote:
Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x1549f232
Device Boot Start End Blocks Id System
/dev/sda1 63 438205004 219102471 7 HPFS/NTFS/exFAT
/dev/sda2 * 606164580 625137344 9486382+ 7 HPFS/NTFS/exFAT
/dev/sda3 438208510 442413055 2102273 f W95 Ext'd (LBA)
/dev/sda5 438208512 442413055 2102272 82 Linux swap / Solaris
Partition table entries are not in disk order
Disk /dev/sdb: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x88e51acc
Device Boot Start End Blocks Id System
/dev/sdb1 63 208571956 104285947 7 HPFS/NTFS/exFAT
/dev/sdb2 208572416 250533887 20980736 83 Linux
/dev/sdb3 250533888 625141759 187303936 83 Linux
Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x000d7a43
Device Boot Start End Blocks Id System
/dev/sdc1 2048 3907028991 1953513472 f W95 Ext'd (LBA)
you'll notice sdc1 is not in fstab, when I do try to add an entry for it (as directed in tut) and restart the system, Linux fails to boot after spewing some error that resembles "bad superblock" into root terminal (tty0). so I'm guessing I'll need to figure out that mount error before I add an entry into fstab for new drive.
should be enough info in this thread to see where the problem is, please check it out and let me know if you can help, if you need more info let me know, would just like to get new hdd working asap.
Adding a new hard drive is usually a pretty simple task. I would recommend you to leave out the "-t ext3" option and let the mount command figure out the file system itself. If this fails, you should repeat the partitioning-mkfs step again. In particular, /dev/sdc1 does not look like a linux partition.
/dev/sdc1 2048 3907028991 1953513472 f W95 Ext'd (LBA)
What I expect is something like:
Code:
siim@shiva:/etc/lightdm$ sudo fdisk -l /dev/sda
Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xe2d9e2d9
Device Boot Start End Blocks Id System
/dev/sda1 * 63 208844 104391 83 Linux
/dev/sda2 208845 321299999 160545577+ 8e Linux LVM
/dev/sda3 321300000 488392064 83546032+ 83 Linux
BTW, do you have a special reason to use ext3 instead of ext4?
Go back into fdisk, delete the partition (d) - if it asks for a number (unlikely), just enter 1.
Then create a new partition, but make it primary - (p). Give it all the space by taking the defaults. Then print the list (p) to ensure it has the correct type = x83. If not change it with (t) - should be straightforward for you by now ...
Write the updates (w) then quit (q). Best to re-boot, then mkfs - BTW, I agree ext4 would be better.
You may also want to tell us what do you want to do with this drive -- a single partition may or may not be OK. You may also tell a few words about your distro and computer.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.