|
Home > Archive > Unix administration > January 2004 > filesystem error: question on recovery
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
filesystem error: question on recovery
|
|
| Rob Baxter 2004-01-23, 4:50 pm |
| Hi,
Recently I rebooted my computer into Windows 98, after running linux
for over 5 months. Right before I left linux, I was doing a lot of
work with my /dev/hdb1 moving files onto it off several CDROMs. Once
I rebooted from win98 back into linux again, I received notice that
the file system wasn't right on boot, and after a manual run was
forced on me I finally got this notice:
Restarting e2fsck from the beginning...
superblock has a bad ext3 journal (inode 8).
Clear<y>? yes
*** ext 3 journal has been deleted - filesystem is now ext2 only ***
My filesystem on /dev/hdb1 is indeed now ext2, and I had to actually
change /etc/fstab to reflect that before it could be auto mounted on
bootup. I'm very concerned about this - the drive is 40G and less
than a year old. What can cause this type of problem and is there any
way for me to get that drive back to an ext3 fs?
I also have a number of files in my lost+found directory on that drive
- but I can't seem to do anything with them. What is the lost and
found for? Is it useful? Could I use it to recover any of my files
lost during this?
I'm using Redhat 8.0. Sorry for the long post - any help is
appreciated as always, thank you.
Rob
| |
| Bill Marcum 2004-01-23, 4:50 pm |
| On 13 Oct 2003 18:17:26 -0700, Rob Baxter
<rbaxter@cyence.com> wrote:quote:
> Hi,
>
> Recently I rebooted my computer into Windows 98, after running linux
> for over 5 months. Right before I left linux, I was doing a lot of
> work with my /dev/hdb1 moving files onto it off several CDROMs. Once
> I rebooted from win98 back into linux again, I received notice that
> the file system wasn't right on boot, and after a manual run was
> forced on me I finally got this notice:
>
> Restarting e2fsck from the beginning...
> superblock has a bad ext3 journal (inode 8).
> Clear<y>? yes
>
> *** ext 3 journal has been deleted - filesystem is now ext2 only ***
>
> My filesystem on /dev/hdb1 is indeed now ext2, and I had to actually
> change /etc/fstab to reflect that before it could be auto mounted on
> bootup. I'm very concerned about this - the drive is 40G and less
> than a year old. What can cause this type of problem and is there any
> way for me to get that drive back to an ext3 fs?
>
tune2fs -j and install SMART utilities.
quote:
> I also have a number of files in my lost+found directory on that drive
> - but I can't seem to do anything with them. What is the lost and
> found for? Is it useful? Could I use it to recover any of my files
> lost during this?
>
The lost+found directory is similar to the FILE????.CHK files created by
Windows Scandisk. The files in lost+found were found by fsck with no
directory entries pointing to them.
for x in lost+found/*; do file $x; done
quote:
> I'm using Redhat 8.0. Sorry for the long post - any help is
> appreciated as always, thank you.
>
> Rob
--
Cheops' Law:
Nothing ever gets built on schedule or within budget.
|
|
|
|
|