Filesystem corruption on flash drive
I have a home server that currently runs off a flash drive, and serves up content from a hard disk. The system is Intrepid 32-bit.
Recently when attempting to do updates, the / filesystem went read-only due to filesystem errors. I ran fsck manually twice and the problem was "fixed"; I was holding down the "y" key for a couple of minutes, there were so many errors on the disk.
Now I've got the same problem again - the filesystem has become read-only.
In future, what can I do to prevent filesystem corruption? Is it a bad idea to run a server off a flash drive, even though the main body of data is going to an HDD? Should I reboot the server every week so it can run fsck on a regular basis? Because it was a flash drive, I was using ext2; should I use a different filesystem?
Also, if I switch to running Ubuntu off an HDD, would a 2.5 inch USB HDD be fine for /, bearing in mind that it would basically be spinning all the time?
Thanks.
I try to treat the cause, not the symptom. I avoid the terminal in instructions, unless it's easier or necessary. My instructions will work within the Ubuntu system, instead of breaking or subverting it. Those are the three guarantees to the helpee.
Bookmarks