mount harddisk problem

kenwong · 11-28-2007, 10:01 AM

Dear All

While I try to mount my harddisk(sdb) to my system it come out the following error, sdb before still can mount on FC6, after I install FC7, it come the follow error out, How can I fix that?

[root@test ~]# mount -t ext3 /dev/sdb2 /backup
mount: wrong fs type, bad option, bad superblock on /dev/sdb2,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

[root@test ~]# dmesg | tail
r8169: eth0: link up
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
r8169: eth0: link down
r8169: eth0: link up
eth0: no IPv6 routers present
IPv6 over IPv4 tunneling driver
sit0: Disabled Privacy Extensions
r8169: eth0: link up
eth0: no IPv6 routers present
VFS: Can't find ext3 filesystem on dev sdb2.

[root@test ~]# e2fsck -b 8193 /dev/sdb2
e2fsck 1.39 (29-May-2006)
e2fsck: Bad magic number in super-block while trying to open /dev/sdb2

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

I have many information inside it, I must mount it up and take the data back, Please HELP~~
thanks

Vincent_Vega · 11-28-2007, 10:04 AM

Are you sure it's an ext3 filesystem? Try mounting without the '-t':

Code:

mount /dev/sdb2 /backup

jschiwal · 11-28-2007, 10:10 AM

Look at the output of "sudo file -s /dev/sdb2". If it is a different filesystem, it will tell you which.

Also try "sudo /sbin/dumpe2fs /dev/sdb2". It may tell you the location of other superblocks.

Code:

example:
Group 0: (Blocks 0-32767)
  Primary superblock at 0, Group descriptors at 1-1
  Reserved GDT blocks at 2-321
  Block bitmap at 322 (+322), Inode bitmap at 323 (+323)
  Inode table at 324-823 (+324)
  0 free blocks, 15989 free inodes, 2 directories
  Free blocks:
  Free inodes: 12-16000
Group 1: (Blocks 32768-65535)
  Backup superblock at 32768, Group descriptors at 32769-32769
  Reserved GDT blocks at 32770-33089
  Block bitmap at 33090 (+322), Inode bitmap at 33091 (+323)
  Inode table at 33092-33591 (+324)
  31080 free blocks, 16000 free inodes, 0 directories
  Free blocks: 34456-65535
  Free inodes: 16001-32000
Group 2: (Blocks 65536-98303)
  Block bitmap at 65536 (+0), Inode bitmap at 65537 (+1)
  Inode table at 65538-66037 (+2)
  32266 free blocks, 16000 free inodes, 0 directories
  Free blocks: 66038-98303
  Free inodes: 32001-48000
Group 3: (Blocks 98304-131071)
  Backup superblock at 98304, Group descriptors at 98305-98305

Is this a new drive? Did you remember to create a filesystem?

wmakowski · 11-28-2007, 10:35 AM

If it is a different filesystem you could run fsck -N /dev/sdb2 to see what fstype comes up. Then you'll know if it isn't ext2 or ext3 and can mount it properly.

Bill

kenwong · 11-28-2007, 08:05 PM

[root@test ~]# sudo file -s /dev/sdb2
/dev/sdb2: LVM2 (Linux Logical Volume Manager) , UUID: izGB1I9ex6g15BUHFmKhMp6F5mNxl6A

[root@test ~]# sudo /sbin/dumpe2fs /dev/sdb2
dumpe2fs 1.39 (29-May-2006)
/sbin/dumpe2fs: Bad magic number in super-block while trying to open /dev/sdb2
Couldn't find valid filesystem superblock.

[root@test ~]# fsck -N /dev/sdb2
fsck 1.39 (29-May-2006)
[/sbin/fsck.ext2 (1) -- /dev/sdb2] fsck.ext2 /dev/sdb2

is this mean it is ext2 system?
but I mount it on ext2 it came out the same error

and this is not a new drive, it is FC4 before I change the server, I have install FC7 now, and I want to take the data back from FC4.
thanks for help

v00d00101 · 11-28-2007, 08:20 PM

How about you try the following.

Code:

mdadm -Q -v /dev/sdb

I suspect your drive is an LVM volume, in which case it may need to be mounted using a different method.

Also check to see if /dev/md(x) exists (where x is a number).

michaelk · 11-28-2007, 08:31 PM

Quote:

root@test ~]# sudo file -s /dev/sdb2
/dev/sdb2: LVM2 (Linux Logical Volume Manager) , UUID: izGB1I9ex6g15BUHFmKhMp6F5mNxl6A

As already suggested a LVM partition can not be mounted like a standard filesystem.

http://forum.fedoraforum.org/forum/s...ght=VolGroup00

kenwong · 11-28-2007, 08:57 PM

I found that it only can vgscan for sda but can't use on sdb how can I check for sdb ?

michaelk · 11-29-2007, 12:50 PM

Post the output of the command
fdisk -l /dev/sdb (that is a small L and you must be root)

lvm.conf might be configured to ignore sdb.

jschiwal · 11-29-2007, 11:21 PM

Is this a new drive that you are adding to the system? You could run the LVM manager to add it . This would allow you more space for /home for example.

kenwong · 12-02-2007, 05:47 PM

Dear All
Thanks for help
I have solve this problem after I change the old Harddisk name to VolGroup01
then it can mount successfully
thanks for all help.

Ken