-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 6/2/2010 8:05 PM, Sean Crago wrote:
Andrew: I'm assuming md0 is on one or more of my two disks, but still investigating whether this is safe to do. Researching mdadm-style software RAID is top of my list of things to do in 9-10 hours after work, but not comfortable popping it out just yet/not sure how to tell if this /dev/md0 device is only on one of my disks and not on both, or a third device/onboard flash.
What's in /proc/mdstat ?
This will tell you what sort of RAID device /dev/md0 is (likely a RAID1 mirror), and which devices it consists of.
Is there a way to safely fix the problem on a live filesystem, due to Synology's custom distro ignoring tune2fs's check interval settings on boot?
You mentioned the ARM system won't boot from a USB device, but can it see one once it's running? If so (or if you've got enough ram or space elsewhere), you can try to copy the existing OS files to a new location, do a pivot_root, and then unmount/fsck the old (broken) root filesystem:
http://linux.die.net/man/8/pivot_root
Also, if you have any way to play with the kernel boot command line (ie: alter the boot-loader settings), you might try some tricks like setting init=/bin/sh. You should then be able to fsck the root filesystem when it's mounted read-only and there's very little running (ie: similar to what most init scripts do check the root fs).
First, however, I'd look to see if there's a /forcefsck flag or similar you can pass to the init scripts (ie: "touch /forcefsck" on a debian based system, then reboot). Look through the init scripts for anything that runs fsck, and see if there's a way to force it into operation.
- -- Charles Steinkuehler charles@steinkuehler.net