randall526 Posted May 24, 2015 Share Posted May 24, 2015 I have someone I recommend unraid for and has a few TB's worth of paid for media data and such. She had a sync utility end up wiping out well over half her data and naturally I got a call. I unmounted the disks and ran a reiserfsck --rebuild-tree --scan-whole-partition /dev/md1 and md2 for each disk. I though about trying to get the data that was left off of there but I don't have enough room on any of my spare drives for that much data. Now I am in a little more hot water as I come in the morning and found my laptop went to sleep and lost the telnet output as it ran all night. I checked ps and top to see if it was still running and no and tried to start the array. The disks are all showing unformated I pulled this out of the syslog May 24 08:50:05 Tower emhttp: shcmd (22): mkdir /mnt/disk1 May 24 08:50:05 Tower emhttp: shcmd (23): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md1 /mnt/disk1 |& logger May 24 08:50:05 Tower kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal May 24 08:50:05 Tower kernel: REISERFS (device md1): using ordered data mode May 24 08:50:05 Tower kernel: reiserfs: using flush barriers May 24 08:50:05 Tower kernel: REISERFS (device md1): journal params: device md1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 May 24 08:50:05 Tower kernel: REISERFS (device md1): checking transaction log (md1) May 24 08:50:05 Tower logger: mount: /dev/md1: can't read superblock May 24 08:50:05 Tower emhttp: _shcmd: shcmd (23): exit status: 32 May 24 08:50:05 Tower emhttp: disk1 mount error: 32 May 24 08:50:05 Tower emhttp: shcmd (24): rmdir /mnt/disk1 May 24 08:50:05 Tower emhttp: shcmd (25): mkdir /mnt/disk2 May 24 08:50:05 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 65534 May 24 08:50:05 Tower kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 0. Fsck? May 24 08:50:05 Tower kernel: REISERFS (device md1): Remounting filesystem read-only May 24 08:50:05 Tower kernel: REISERFS error (device md1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [1 2 0x0 SD] May 24 08:50:05 Tower kernel: REISERFS (device md1): Using r5 hash to sort names May 24 08:50:05 Tower emhttp: shcmd (26): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md2 /mnt/disk2 |& logger May 24 08:50:05 Tower kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal May 24 08:50:05 Tower kernel: REISERFS (device md2): using ordered data mode May 24 08:50:05 Tower kernel: reiserfs: using flush barriers May 24 08:50:05 Tower avahi-dnsconfd[3511]: DNS server with port address != 53 found, ignoring May 24 08:50:06 Tower kernel: REISERFS (device md2): journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 May 24 08:50:06 Tower kernel: REISERFS (device md2): checking transaction log (md2) May 24 08:50:06 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 65534 May 24 08:50:06 Tower kernel: REISERFS error (device md2): vs-5150 search_by_key: invalid format found in block 0. Fsck? May 24 08:50:06 Tower logger: mount: /dev/md2: can't read superblock May 24 08:50:06 Tower emhttp: _shcmd: shcmd (26): exit status: 32 May 24 08:50:06 Tower emhttp: disk2 mount error: 32 May 24 08:50:06 Tower emhttp: shcmd (27): rmdir /mnt/disk2 May 24 08:50:06 Tower kernel: REISERFS (device md2): Remounting filesystem read-only May 24 08:50:06 Tower kernel: REISERFS error (device md2): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [1 2 0x0 SD] May 24 08:50:06 Tower kernel: REISERFS (device md2): Using r5 hash to sort names I am currently running reiserfsck -rebuild-tree /dev/md1 again. The utility atleast saw it as a reiserfs file system which is a good sign. Any thoughts as to what my next steps should be and also is there a need to run these checks against the sdb and sdc dev files instead of the md devices perhaps? Quote Link to comment
randall526 Posted May 24, 2015 Author Share Posted May 24, 2015 -rebuild tree is still running again with out the scan whole partition this time as I will be thankfull just to get the disks recognized and mountable at this time Based off the logs, I wonder if I need to run it again with this option, --rebuild-sb to rebuild the superblock Quote Link to comment
randall526 Posted May 25, 2015 Author Share Posted May 25, 2015 I was able to get the disk back with out the scan whole partition option and then running it again with the option. Think I'm good. My heart dropped when I saw the unformated disks. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.