First of all, my hard drive with one large ext3 partition is not getting mounted at startup. The device is located at /dev/hdb1.
/# mount /320
mount special device /dev/disk/by-uuid/5f8794bc-a47d-4a18-a93a-ad87aaffddbc does not exist
Ok, no problem. I'll just mount it manually.
/# mount /dev/hdb1 /320
/# cd 320
???.?? ??8???8?.??8 ??y.??y
WTF?!? Where are all my files?
/# umount 320
/# mount /dev/hdb1 /320 -t ext3
/# cd 320
jared lost+found pics
Thank alah! All of my pr0n and *ahem* important documents are still there. So, what's the problem?
/# vol_id /dev/hdb1
Ok, I remembered from school that FAT12 was for FLOPPY DISKS and had no support for directories. The question is, why would this partition decide all of a sudden that it is VFAT? When I run a e2fsck it claims that the partition is clean. Running a search on google for "ID_FS_VERSION=FAT12" comes up with one (!) result.
Linux deneb 2.6.17-10-generic #2 SMP Fri Oct 13 18:45:35 UTC 2006 i686 GNU/Linux