after hard reboot, filesystem mounts read only

Message

Drewgrange · Post by **Drewgrange** » Sat Apr 17, 2004 11:35 pm

I had a crash that required a hard boot. Afterwards, my /storage partition loads up as read only. I can't figure out whats wrong with it.

I can umount it and mount it again, and this will allow me to write something once as far as I've found,, and then it won't let me do anything again. Nothing about my fstab file has changed, and it worked fine in the past. Filestystem is reiserfs.

Any thoughts?

Drewgrange · Post by **Drewgrange** » Sat Apr 17, 2004 11:58 pm

nautilus shows that the drive is set for read write execute permissions correctly. Set at 777. But it says that the disk itself is read only.

speed_bump · Post by **speed_bump** » Sun Apr 18, 2004 12:55 am

Have you checked to see if the fsck succeeded after the hard boot? Depending on filesystem type, an fsck may not be necessary, but judging from your description, it sounds as though that filesystem is at least somewhat corrupted. Mounting the filesystem read-only is typical behavior in these circumstances in order to avoid further corruption of the filesystem and possible loss of data.

You can unmount the filesystem, and run

reiserfsck /storage

Check the man page for options, but I'd do that before going too far. If nothing else, it will tell you that the filesystem is clean. Most likely, it will end up fixing a few things.

Hope this helps.

Best of luck.

Drewgrange · Post by **Drewgrange** » Sun Apr 18, 2004 1:28 am

Actually I'm not sure why I said it is reiserfs, its a FAT32 drive that I share with windows and linux. What would I use to check that under linux?

speed_bump · Post by **speed_bump** » Sun Apr 18, 2004 2:32 am

I'm not quite sure. It's possible that fsck may be able to fix it, but that seems unlikely. However, it may be best to boot to windows and let checkdisk do its thing (I know, I know

). If you can still read the filesystem, it's probably a wise idea to move any vital data to another partition (full backup is best) to avoid loss. Checkdisk should be OK, but much evil lurks in the heart of Redmond, so anticipating possible problems is well advised.

Drewgrange · Post by **Drewgrange** » Sun Apr 18, 2004 8:08 pm

Norton's disk checker found a bunch of corrupted folders, and had to convert them each into a (useless) file. Oh well. Also the drive was 92% fragmented, don't know if that had anything to do with the corruption. Currently de-fragging, so I'm not sure if this will fix the problem of the drive being read only in linux, but it works fine under windows

bdonlan · Post by **bdonlan** » Mon Apr 19, 2004 1:55 am

sys-fs/dosfstools has a fsck.vfat - that might help in the future.

Drewgrange · Post by **Drewgrange** » Mon Apr 19, 2004 2:11 am

My filesystem got completely messed up. The defrag got stuck at 71% and now everything is random scrambled characters. I'm running a disk check/repair tool, and its going through every cluster saying "bad links in lost chain at cluster _____ corrected" .. obviously its taking a long time, I'm guessing that for a 160GB FAT 32 partition there are around 5 million clusters. Hopefully this fixes something.

Well, this has taught me that I need to start backing things up more often.

bdonlan · Post by **bdonlan** » Mon Apr 19, 2004 2:26 am

Are you sure that the disk is physically sound? I'd do a surface check myself. Also, this time don't run a defrag until you run a disk check twice, it seems the first check missed something, and caused the defrag to corrupt things more.

Drewgrange · Post by **Drewgrange** » Mon Apr 19, 2004 2:56 am

Well, the check made it through and did nothing, it said there were irrepairable errors on the disk. I had to format (losing 160 gigs of data

recorded tv shows, 40 gigs worth of live music, other things best unsaid) and now it's working fine again.

Time to start rebuilding

Might be time to look into buying a DVD drive for some backups