May 30, 201214 yr Using 5.0RC3 with 4 data disk plus parity and cache. Syslog shows the repeated ioctl so im afraid a syslog wont help me. My array was spinning up the disks and could not figure out why they would not spin down. Looked thru the syslog and the only error shown is this: May 30 05:43:09 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 1 does not match to the expected one 2 (Minor Issues) May 30 05:43:09 Tower kernel: REISERFS error (device md2): vs-5150 search_by_key: invalid format found in block 450408190. Fsck? (Errors) May 30 05:43:09 Tower kernel: REISERFS (device md2): Remounting filesystem read-only (Drive related) May 30 05:43:09 Tower kernel: REISERFS error (device md2): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2305 2766 0x0 SD] (Errors) May 30 05:43:32 Tower kernel: scsi_verify_blk_ioctl: 40 callbacks suppressed (Drive related) I brought the server down to add a new disk which is being currently precleared. Nothing is red balled but the drives are being read not sure what the issues is. Im running a reiser check on disk 2. I will report results. Update: No errors with check. Dunno what to do next all still is well with the array.
June 13, 201214 yr Just to verify, you ran reiserfsck on Disk 2? That would be the correct thing to do, and if it found no issues, then Disk 2 should be fine, and the ReiserFS corruption was only in memory, and rebuilt on reboot. Even if the syslog contains a lot of noise, it can still be useful, just harder to analyze. I would run reiserfsck on all of your data drives, just to be safe. See Check Disk File systems. (Caution: the SMB instructions on that wiki page were written for UnRAID v4, and I don't know if they need updating for v5. Joe L or any one?)
June 13, 201214 yr Author Thanks ROBJ I did run reiserfsck on Disk 2, nothing reported as corrupted...I think I may have run into an issue with the new RC3 release. I downgraded to B14 and everything is just dandy, no noise from the syslog. Weird I guess?
June 13, 201214 yr It is very weird. I would still run another reiserfsck check on all of your data drives. I don't believe it is related to RC3 or any specific release, at least I cannot think of a single reason why it would be.
June 14, 201214 yr Author I will run a check on all the drives just to give myself the extra reassurance. Thanks for the help.
Archived
This topic is now archived and is closed to further replies.