Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
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
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.
[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.
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.