October 9, 201411 yr Hi, This is my first "real" problem with UNRAID. Today one data disk (disk 7) shows UNFORMATTED (green ball). What to do next with no data loss ? Thanks in advance ! Here is a part of the system log where it goes wrong. Oct 9 22:35:28 Tower emhttp: shcmd (110): mkdir -p /mnt/disk7 Oct 9 22:35:28 Tower emhttp: shcmd (111): set -o pipefail ; mount -t reiserfs -o noatime,nodiratime /dev/md7 /mnt/disk7 |& logger Oct 9 22:35:28 Tower kernel: REISERFS (device md7): found reiserfs format "3.6" with standard journal Oct 9 22:35:28 Tower kernel: REISERFS (device md7): using ordered data mode Oct 9 22:35:28 Tower kernel: reiserfs: using flush barriers Oct 9 22:35:28 Tower kernel: REISERFS (device md7): journal params: device md7, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Oct 9 22:35:28 Tower kernel: REISERFS (device md7): checking transaction log (md7) Oct 9 22:35:28 Tower kernel: REISERFS (device md7): Using r5 hash to sort names Oct 9 22:35:33 Tower kernel: REISERFS (device md7): Removing [258 259 0x0 SD].. Oct 9 22:35:33 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 60526 does not match to the expected one 1 Oct 9 22:35:33 Tower kernel: REISERFS error (device md7): vs-5150 search_by_key: invalid format found in block 15878227. Fsck? Oct 9 22:35:33 Tower kernel: REISERFS (device md7): Remounting filesystem read-only Oct 9 22:35:33 Tower kernel: done Oct 9 22:35:33 Tower logger: mount: warning: /mnt/disk7 seems to be mounted read-only. Oct 9 22:35:33 Tower emhttp: shcmd (112): set -o pipefail ; mount -t reiserfs -o remount,user_xattr,acl,noatime,nodiratime /dev/md7 /mnt/disk7 |& logger Oct 9 22:35:33 Tower logger: mount: /dev/md7: can't read superblock Oct 9 22:35:33 Tower emhttp: shcmd: shcmd (112): exit status: 32 Oct 9 22:35:33 Tower emhttp: mount error: 32 Oct 9 22:35:33 Tower emhttp: shcmd (113): rmdir /mnt/disk7 Oct 9 22:35:33 Tower emhttp: shcmd: shcmd (113): exit status: 1
October 9, 201411 yr Unformatted just means it cannot mount most likely file system corruption. Happened to be me a 2 months ago on a drive. A checkdsk will be in order. If on resierfs http://lime-technology.com/wiki/index.php/Check_Disk_Filesystems stop array, check maintenance mode and start. go to terminal on server or telnet in (preferably use screen) reiserfsck --check /dev/md# (1 for disk 1, 2 for disk 2 etc). it will report back what to do most likely it will want you to run it with --rebuild-tree afterwards. worked for me.
October 10, 201411 yr Author The check finished with 1 error and suggested the --rebuild-tree option. Running it now... To Be Continued...
Archived
This topic is now archived and is closed to further replies.