LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 05-03-2012, 01:07 AM   #1
ronniekl
LQ Newbie
 
Registered: May 2012
Posts: 1

Rep: Reputation: Disabled
mount: wrong fs type, bad option, bad superblock on /dev/sdc1, New hard drive install


hello
I am trying to add a new hard disk drive to my PC using this tut:

http://www.yolinux.com/TUTORIALS/Lin...HardDrive.html

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)
and my /etc/fstab:

Quote:
/dev/disk/by-id/ata-Hitachi_HDT725032VLA380_VFJ201R2ED9PNX-part5 swap $
/dev/disk/by-id/ata-Hitachi_HDT725032VLA380_VFJ201R2ED8RWX-part2 / $
/dev/disk/by-id/ata-Hitachi_HDT725032VLA380_VFJ201R2ED8RWX-part3 /home $
/dev/disk/by-id/ata-Hitachi_HDT725032VLA380_VFJ201R2ED9PNX-part1 /windows/C $
/dev/disk/by-id/ata-Hitachi_HDT725032VLA380_VFJ201R2ED9PNX-part2 /windows/D $
/dev/disk/by-id/ata-Hitachi_HDT725032VLA380_VFJ201R2ED8RWX-part1 /windows/E $
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
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.

-ron.kl
 
Old 05-03-2012, 01:49 AM   #2
otoomet
Member
 
Registered: Oct 2004
Location: Tartu, Århus,Nürnberg, Europe
Distribution: Debian, Ubuntu, Puppy
Posts: 619

Rep: Reputation: 45
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?
 
Old 05-03-2012, 02:02 AM   #3
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,120

Rep: Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120Reputation: 4120
Ugh - not your fault; (very) bad instructions.

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.
 
Old 05-03-2012, 02:16 AM   #4
yars
Member
 
Registered: Apr 2012
Location: Russia
Distribution: Slackware64-current
Posts: 249

Rep: Reputation: 24
Quote:
Originally Posted by ronniekl View Post
I'm guessing something is messed up with partition table, or new drive is simply not partitioned correctly?
Yes, you have on a /dev/sdc1 only extended partition, without a primary and/or logical partitions, like is:
Code:
# fdisk -l
Disk /dev/hdc: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xa1ada1ad

   Device Boot      Start         End      Blocks   Id  System
/dev/hdc1   *           1        1305    10482381    7  HPFS/NTFS
/dev/hdc2            1306       19457   145805940    f  W95 Ext'd (LBA)
/dev/hdc5            1306        2610    10482381   83  Linux
/dev/hdc6            2611        2643      265041   82  Linux swap
/dev/hdc7            2644       19457   135058423+   7  HPFS/NTFS

Last edited by yars; 05-03-2012 at 02:19 AM.
 
Old 05-03-2012, 02:28 AM   #5
otoomet
Member
 
Registered: Oct 2004
Location: Tartu, Århus,Nürnberg, Europe
Distribution: Debian, Ubuntu, Puppy
Posts: 619

Rep: Reputation: 45
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.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
mount: wrong fs type, bad option, bad superblock on /dev/sda1 dvalente Ubuntu 17 01-31-2016 01:14 PM
mount: wrong fs type, bad option, bad superblock on /dev/hdc3 Lordandmaker Linux - Hardware 15 06-05-2011 08:55 AM
usb drive won't mount - error: wrong fs type, bad option, bad superblock on /dev/sda1 bluecog6 Linux - Hardware 4 01-27-2007 09:07 AM
mount: wrong fs type, bad option, bad superblock on /dev/cdrom, Adil_uk Linux - Hardware 9 02-16-2005 05:50 PM
mount: wrong fs type, bad option, bad superblock on /dev/sdb1 pmoreira Linux - Hardware 5 02-26-2004 10:31 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 04:31 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration