I just installed Winbloze 98 on a second HD.
Strangely, now when I'm trying to boot my Linux on the first HD, I got this error msg:

Fat: Bogus Logical Sector Size 0
UMSDOS: Ms-Dos_Read_Super Failed, Mount aborted
Fat: Bogus Logical Sector Size 0
Fat: Bogus Logical Sector Size 0
Read_Super_Block : Can't find a ReiserFs FileSystem on (Dev 03:41,Block 64, Size 1024)
Read_Super_Block : Can't find a ReiserFs FileSystem on (Dev 03:41,Block 8, Size 1024)

Kernel Panic: VFS : Unable to Mount Root FS on 03:41


Partition Magic tell me that my root partition is EXT2 but it can't find error on it (my root partition should be Ext3, so I have a very big problem). So well, I suppose the damn winbloze corrupt my root fs. Is there a ways to fix it or to get my data?

Try qith FSCK, if you didn't mess up with the redundant superblock you should be able to save your partition.

If that dowsn't work you could try rebuilding you FS, but obviously you will have to reinstall you linux.

AFAIK windows install can't corrupt EXT3 partitions, it just can't read them.

I have one more question: did you scanned your Linux HDD with the installer's scandisk? I did so while installling ME on a Mandrake's box and it completley crashed my linux partitions. If that happend you are screwd, I hope you didn't have anything important on your linux partitions....

That's why I hate M$, they can't stand that people use Linux, thay just like destroying it's partitions.


Sorry to hear about another nice person that fell under the windoze's curse... hehe.


I think green peace should park the rainbow warrior in front of Micro$oft t seatle, they are trying to eliminate the penguin lovers!!!! hahah.

sorry about your root partition.

Always at your service (except when sleepin)

Ciccio Bortiman
GANDALF.-

hehehe I didn't scan my *nux partition with the installer scandisk, but I think maybe Winbloze wrote something on the first partition on the first disk (in nux word: /dev/hda1) without checking so it destroyed my partition table or something like that.

Well, now how can I fsck if I can't boot? 'til I have no root partition, even the boot cd can't do anything for me. I guess I should check with a root floppy but how can I get one if I don't have a *nux system before?
...
hehehe such a newbie question I think


Anyways, thanx for your help Gandalf

Of course suckin windows wrote something on your /dev/hda1 it is Windows boot loader. DID YOU USE AUTOMATIC PARTITIONING? or just manually?? anyway, teh first 5 or 6 blocks sholud be dedicated to /boot, it is there where win installs it's boot loader. if you started your root partition at the first block you've lost a few blockgroups at least.

You should have never installed windows with linux installed. If you have more than one HDD you could have unplugged your lin drive, installed windows and then replugged linux's hdd. then running LILO should solve the boot problem, if not you modify /etc/lilo.conf and that is it.

was your data SO important that is worth a BIG solution??? I mean, it is the root partition, you shouldnt have files there (i mean user files), they should be at /var or /home.
...
If you are sure you won't lose any ESSENTIAL data i suggest you to reinstall linux, it may not be the BEST solution, but it is quicker and easyer. The first rule of solution providers is that the solution must prevent dta lost as well as time lost. and my personla rule is that it should also prevent capital lost (hehe, i can't afford to buy a new hdd or to send mi computer to a shop, so i fix thigs as well as i can and i am happy with things the way they come out)



that is indeed a question! try tldp.org or even google.com (a little bit harder)


Save the whales, save the penguins

At your service

.:8yT3 H4n73R:.

Ok, I finally got a root disk... I done few fsck check on my lost partition (got some problem to found the first magic number, I was forced to use the "back-up" number). Now my partition is mountable, readable...
But the only thing I can read on is the "lost+found" directory that contain... pfff... ten pages of numbers (inode number right?).

Can I do something now to get my data back or it's the proof that everything is lost?

I guess you could use the explore2fs program from windows and then copy the data you need from linux to your windows drive.

Ok, now I'm lost....

you say that you mount your root partition from a boot disk but you can't read any other data but lost+found????

how was done your original HDD partitioning?

try booting now from that drive, because if you can boot all your data should be there. There is an fsck option that retrieves the backup superblocks and i-nodes and then rebuilds it. I suggest that you first try with that software pgal said and then if that doesn't work try fsck -b (i think... it was something like backup so it is probably -b)

Save the penguin!!!!

I said I finally get a <B>floppy</B> root disk... I can mount and read my old <B>HD</B> root, but instead of my directory name, I have a bunch of inode number (?). My data seems Ok but my system can't boot (of course, now my /boot directory name is #124567 or something like this).

are you sure you didn't run scandisk??? because that looks like a windows repaired directory... It happend to me a few months ago... if that happen ALL your data is lost.

Sorry about your partitions

Save thepenguin