Cheers for the reply. In answer - I cannot think why the mem stick would need reformatting. It was working approx 2 weeks ago in the way I would've expected and now, after I rebooted my machine today it wouldn't.
Upon further digging around however, it does provide an msg that the file system type could not be identified and that nothing from /proc/filesystems worked. The options under /proc/filesystems are as follows:
From this I would hazard a guess that there are 7 fs types it has modules loaded for - reiserfs (my fs), iso9660 (CD-R/W), vfat, msdos, unsdos (all Win related), and ext2 & ext3 (other fs options for Linux). The most obvious option would be is usbfs.
The /etc/fstab reads auto for the fs flag.
The two questions are still the same though:
1. How to fix, or am I looking to compile the usbfs into my kernel?
2. WTF happened in the first place when I rebooted?
Here's some context:
I loaded 2 x 512MB Matrix PC133 SDRAM chips into an ASRock K7VT2 running with an AMD Athlon XP2400 chip. Sometimes the boot up process gets stuck on the NVRAM check or before Lilo kicks in since I rebooted it. However, it is hard to say precisely if the "invalid block device" stderr is a result of the new chips or something else, because before I changed the chips the box was running for about 3 straight months. It is feasible something could have happened during that time and is not associated with the chips at all. I do
know that the camera loaded just fine in a short space of time prior to rebooting. Maybe I have some kind of corruption booting, but as far as I can tell with rootkit and clamav there doesn't seem to be any boot sector corruption, and all other file systems appear to boot quite nicely.
In all other ways my Slack 10 box is working just as smoothly and easily as always ... except for this glitch.