better yet if you have the gentoo cd handy ...boot and run fsck.ext3 /dev/yourpartition|drivehere reboot and see what happens, if it doesnt boot hopefully you will be able to mount it under the gentoo cd and see if you can retreive the files that way .....
Cheers Dale. ----- Original Message ----- From: "Gareth Williams" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, December 09, 2003 9:19 PM Subject: Re: Ext3 Fs Broke > On Tuesday 09 December 2003 19:08, Benjamin Devine wrote: > <snip> > > I did the normal fixers mounted the problem device in write mode then I > > ran fsck2fs (I think cant remember) as fsck is not on my system. After I > > manually went through and fixed it. I rebooted my system and I kernel > > panic on boot. I was planning to install gentoo anyway but now seems the > > right time. I have some VERY important files on ext3 fs has anyone had any > > success in the past where they have booted from say Knoppix and mounted > > the fs then copied it across? Does anyone know of any solutions to this > > problem? > <snip> > > Firstly, you probably don't want to fsck your filesystem with it mounted > read-write, if it isn't mounted read-only then you should 'remount -ro /' (or > something like it. Off the top of my head...) before running fsck. I would > suggest booting either Knoppix (if you have a CD), or a tomsrtbt floppy if > you don't have a knoppix CD (you can download the floppy image and write it > to the floppy disk using something like 'rawrite' in windows if you can't > boot your linux partition). Try running fsck from that, and then try mounting > your filesystem somewhere if you can get fsck to run cleanly. (note that if > you don't have ext3 support in your kernel, as I don't think(?) the tomsrtbt > one does, you can mount it as ext2, put -t ext2 in your mount command). Hang > on... ext3 you say? Wait, what am I saying... do you / can you / should you > even fsck ext3? I'm not sure.. I still run ext2, heh. Someone who knows might > like to comment... > > My other idea is... if all else fails, what kind of data do you need to > retrieve? Do you know / remember any part of it? If it's a text file, for > instance, you could try the old "grep through all the raw data" trick. > Something like: > # cat /dev/hda | grep -B 200 -A 200 "text you know was in your file" > > (arguments -B and -A indicate to display 200 lines before and after the > located text string, read the man page for details. And obviously replace > /dev/hda with whatever your hard drive is called) > > Hope this helps. Good luck Ben. > > Cheers, > Gareth > > >
