Ashley Reynolds wrote: > > Hi All, > > I've got a bit of a problem. Recently, I compiled a new kernel and booted > it alongside my current one, 2.4.17-1mdk - after booting with the new > kernel, /dev/hda1 (a FAT32 partition on my primary hard disk), didn't > mount. > > I figured that I hadn't compiled VFAT support into the kernel, > thought nothing of it, and went to boot the old kernel so that I could > recompile the new kernel with the necessary filesystem support. > > However, I was faced with the same issue. > > So, I tried to boot Windows XP, which resides on that partition, with > no avail. LILO just refreshes the display. > > After poking around the logs, I turned up the following: > > dmesg: > MSDOS FS: IO charset iso8859-1 > MSDOS FS: Using codepage 850 > FAT: bogus logical sector size 5376 > VFS: Can't find a valid FAT filesystem on dev 03:01. > FAT: freeing iocharset=iso8859-1 > > boot.log: > Feb 19 21:39:01 gumby mount: mount: wrong fs type, bad option, bad > superblock on /dev/hda1, > Feb 19 21:39:01 gumby mount: or too many mounted file systems > > I don't believe this has been caused by the new kernel, as I have compiled > and run countless kernels without such trouble. I do, however, have a > feeling that the filesystem may have been corrupted when the machine was > earlier rebooted unintentionally. > > My question is this: Is there any possible way to fix the corrupted > partition/filesystem, as it has some crucical data on it, that I *really* > don't want to lose. > > I look forward to any help that you guys can offer. > > Regards,
man that gotta hurt. i am still pretty much a newbie, but what i would try to do is put in the mandrake cd and boot from it. when it comes to the disk partitioning part check to see if it recognises the FAT32 partition. if it does then maybe all is not lost yet. discontinue the install and then connect the hdd to another windoz pc and see if that will read the partition. if yes then recover your data from there. or if you have a spare hdd, load windblows on that and then boot of that with your orig hdd connected as slave, and try. OR since you said FAT32, maybe you can boot of a win 98 se floppy with windblows fdisk on it and try 'fdisk /mbr' it is possible that only your mbr is corrupt. you will lose lilo though, but this is easily recovered IF you make a linux bootdisk first or simply "upgrade" your linux with the same distro that you have. keeping my fingers crossed and hoping for the best, mario -- "The software said 'runs on Win95 or better,' so I installed it on Linux"
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
