well, it WAS ext3, now it is NONE...how can i bring it back without losing my data?

[kr0m3]

so, i had to completely blow away hda and reinstall everything from scratch....

thinking i was smart, i backed-up all my important stuff to hdb5, a 6gig ext3 partition.

i am ashamed to say that for work-purposes, i had to dual-boot my Redhat8 with XP Pro (back in the clutches, sigh...) so i successfully installed grub to the first sector on hdb, set up my "/", "/boot" and "/swap" on hdb as well, but made sure that i left hdb5 intact (according to disk druid)
then i exported the proper "linux.bin" to C:\ and modified my boot.ini ...

all of that worked great! i even modified my /etc/fstab to show the shared vfat partition that is on hda...works like a charm! woo-hoo!!

*******
however... :(
My hardware manager (in Gnome, i am going to download KDE 3.1 and install later) shows hdb5's file system as "none" !! oh crud! :eek:

everything went so well, i had no issues....WHAT WENT WRONG??

I suppose, more to the point, how can i get it back? I even tried to "fake" it by attempting to mount it as ext3, i even added the appropriate field to /etc/fstab and rebooted...no-go.

i really dont want to lose all of my back-ups....can anyone help me out here?

thank you very much in advance, have a great day!
~k

[Raoul_Duke]

What error messages do you get when you try to mount it? :)

[kr0m3]

:rolleyes:

sorry, i thought i was giving all of the info needed and forgot the damn error.

just the typical one...
*****************
[root@jezebel root]# mount -t ext3 /dev/hdb2 /mnt/hdb2
mount: wrong fs type, bad option, bad superblock on /dev/hdb2,
or too many mounted file systems
[root@jezebel root]#
*****************

(and yeh, it is hdb2, not 5 as i mentioned above, sorry again)

thanx for your interest!
~k

[JohnT]

ext3 filesystems may still be mounted by ext2 as long as they have been cleanly unmounted. ext2 will refuse to mount ext3 filesystems which have not been cleanly shut down, because there is live data still in the journal which ext2 does not know how to deal with.

The e2fsck application from e2fsprogs can perform journal replay, so running
e2fsck -fy /dev/hdXX on a damaged ext3 filesystem will repair it, allowing ext2 to mount it.

ext3 software will refuse to mount an ext2 filesystem - at present there must be a journal file on the filesystem.

http://www.zip.com.au/~akpm/linux/ext3/ext3-usage.html

[kr0m3]

i'll give it a try tonight! appreciate it a bunch...have a great day!

~k