Lsof|grep MD0 # check what is using the device (killall rsync could help ) e2fsck -p -f -v -C 0 /dev/md0 # check filesystem reboot # reboot afterwards # someone here recommends this: e2fsck -cDfty -v -C 0 /dev/md0 # check filesystem and check for badblocks as well /etc/init.d/services.sh stop Script filename: FilesystemCheck.sh /etc/init.d/services.sh stop # stop all services umount /dev/md0 # umount the filesystem -> if you get a determine the name of your raid device (usually md0) cat /etc/nf ARRAY /dev/md0 devices=/dev/sda3,/dev/sdb3 Session, so it will keep running if you get disconnected.ġ. Recommend you to run this in a screen -S FileSystemCheck (because full set of data on both harddisks) Imho QNAPs are hardware wise nice, but software wise they are a bloat (too much stuff, it shall only store files AS RELIABLY AS POSSIBLE (here it does not shine per default)) paranoid mode on: do a 1:1 dd copy of the “broken” filesystem over ssh to external backup system before proceeding any further! you have been warned! if it is raid1: it is safe to: 1) power down system 2) take one harddisk out (just in case) 3) power up and proceed QNAP – Filesystem check fails – Examination failed(Cannot unmount disk by sh) Volunteer computing / World Community Grid / WCG.Virtualization / KVM / VirtualBox / xenserver.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |