Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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'm not sure if this is correct, although you might want to try it. Try rummaging through /dev to see if you can find anything relating to your /dev/hdbX, or /dev/hdaX. (X meaning the partition number.)
Example:
Quote:
$ mount /dev/hdb5 /mnt/backup
Or whatever the case might be.
Something like this happened to me before. It was odd, some how the partition name was changed and it ended up being hdb5 for some odd reason. You might want to check it out.
Seriously.
Here is a thought - I dunno if it works - but you can try it.....
code:
file /dev/hdb1
See if it gives you the format.....ext2, 3, reiser, etc........
result
Code:
# file /dev/hdb1
/dev/hdb1: block special (3/65)
Quote:
I'm not sure if this is correct, although you might want to try it. Try rummaging through /dev to see if you can find anything relating to your /dev/hdbX, or /dev/hdaX. (X meaning the partition number.)
Example:
quote:
$ mount /dev/hdb5 /mnt/backup
Or whatever the case might be.
Something like this happened to me before. It was odd, some how the partition name was changed and it ended up being hdb5 for some odd reason. You might want to check it out.
result
there is no folders named hdbX, but there are some files called hdb, hdb1, hdb2 and so on up to hdb63
Quote:
And here comes crunch - with sumpin' I forgot about....
I have had that same issue - def try that.......do this:
code:
ls /mnt/hdb
Such a good idea - I feel like a moron - lol
result
Code:
# ls /mnt/hdb
/bin/ls: /mnt/hdb: No such file or directory
Alright - I'm getting tired of this thread, so let's fix it already, eh?
Do this:
Code:
zaphyr@suse$ su
Password:
root@suse# fdisk /dev/hdb
Command (m for help): p
Disk /dev/hdb: 80.0 GB, 80026361856 bytes
240 heads, 63 sectors/track, 10337 cylinders
Units = cylinders of 15120 * 512 = 7741440 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 * 1 65 491368+ 83 Linux
/dev/hdb2 66 10337 77656320 5 Extended
/dev/hdb5 66 131 498928+ 82 Linux swap
/dev/hdb6 132 10337 77157328+ 83 Linux
Command (m for help):q
root@suse#
Find in that list (the one that prints on your box) the partition closest in size you the one you are trying to recover. Attempt to mount it using the fs specified. If this doesn't work, we are indeed moving onto recovery options.........
# fdisk /dev/hdb
The number of cylinders for this disk is set to 14593.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/hdb: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 1 14592 117210208+ 83 Linux
Command (m for help): q
then i should mount it....i still get error
Code:
# mount -t reiserfs /dev/hdb1 /mnt/backup
mount: wrong fs type, bad option, bad superblock on /dev/hdb1,
or too many mounted file systems
i even tried with
Code:
# mount -t linux /dev/hdb1 /mnt/backup
mount: fs type linux not supported by kernel
If you can, download a copy of Knoppix 2.6 (under Download Linux on this website), burn it to disk, boot it up (it's a LiveCD), and it should mount all of your filesystems. When it finishes booting, move all your files to hda, and then re-install SuSE on hdb.
Distribution: LFS 5.0, building 6.3, win98se, multiboot
Posts: 288
Rep:
What's happened is that the fs on hdb1 is suffering from some degree of corruption. That's why mount fails. The good news is that you may be able to recover with the fs appropriate fsck command, most likely something like:
fsck.reiserfs /dev/hdb1
The actual name of the command varies with the distro. (reiserfsck, fsck.reiser, etc.) The bad news is that while reiser is very resistant to powerfailure corruption, when reiser does fail, it tends to go down _hard_. Good luck.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.