October 27, 201015 yr I was attempting to copy some of my files last night. Everything was going well until the system just stopped. Looking at my syslog, I see the following errors. Oct 27 06:38:12 datacenter2 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 13817 does not match to the expected one 3 Oct 27 06:38:12 datacenter2 kernel: REISERFS error (device md10): vs-5150 search_by_key: invalid format found in block 200783002. Fsck? Oct 27 06:38:12 datacenter2 kernel: REISERFS (device md10): Remounting filesystem read-only Oct 27 06:38:12 datacenter2 kernel: REISERFS error (device md10): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [1558 1563 0x0 SD] Oct 27 06:38:12 datacenter2 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 13817 does not match to the expected one 3 Oct 27 06:38:12 datacenter2 kernel: REISERFS error (device md10): vs-5150 search_by_key: invalid format found in block 200783002. Fsck? Oct 27 06:38:12 datacenter2 kernel: REISERFS error (device md10): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [1558 1563 0x0 SD] Oct 27 06:38:12 datacenter2 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 13817 does not match to the expected one 3 Oct 27 06:38:12 datacenter2 kernel: REISERFS error (device md10): vs-5150 search_by_key: invalid format found in block 200783002. Fsck? Oct 27 06:38:12 datacenter2 kernel: REISERFS error (device md10): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [1558 31287 0x0 SD] Oct 27 06:38:12 datacenter2 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 13817 does not match to the expected one 3 Oct 27 06:38:12 datacenter2 kernel: REISERFS error (device md10): vs-5150 search_by_key: invalid format found in block 200783002. Fsck? Oct 27 06:38:12 datacenter2 kernel: REISERFS error (device md10): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [1558 31287 0x0 SD] Oct 27 06:38:12 datacenter2 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 13817 does not match to the expected one 3 Oct 27 06:38:12 datacenter2 kernel: REISERFS error (device md10): vs-5150 search_by_key: invalid format found in block 200783002. Fsck? This error goes one for a while, but I thought this should be enough to get a clue as to what is going on. I can actually access the drive, but I have a red dot next to this drive. Can someone help me figure this out? Thanks!!
October 27, 201015 yr I was attempting to copy some of my files last night. Everything was going well until the system just stopped. Looking at my syslog, I see the following errors. Oct 27 06:38:12 datacenter2 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 13817 does not match to the expected one 3 Oct 27 06:38:12 datacenter2 kernel: REISERFS error (device md10): vs-5150 search_by_key: invalid format found in block 200783002. Fsck? Oct 27 06:38:12 datacenter2 kernel: REISERFS (device md10): Remounting filesystem read-only Oct 27 06:38:12 datacenter2 kernel: REISERFS error (device md10): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [1558 1563 0x0 SD] Oct 27 06:38:12 datacenter2 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 13817 does not match to the expected one 3 Oct 27 06:38:12 datacenter2 kernel: REISERFS error (device md10): vs-5150 search_by_key: invalid format found in block 200783002. Fsck? Oct 27 06:38:12 datacenter2 kernel: REISERFS error (device md10): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [1558 1563 0x0 SD] Oct 27 06:38:12 datacenter2 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 13817 does not match to the expected one 3 Oct 27 06:38:12 datacenter2 kernel: REISERFS error (device md10): vs-5150 search_by_key: invalid format found in block 200783002. Fsck? Oct 27 06:38:12 datacenter2 kernel: REISERFS error (device md10): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [1558 31287 0x0 SD] Oct 27 06:38:12 datacenter2 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 13817 does not match to the expected one 3 Oct 27 06:38:12 datacenter2 kernel: REISERFS error (device md10): vs-5150 search_by_key: invalid format found in block 200783002. Fsck? Oct 27 06:38:12 datacenter2 kernel: REISERFS error (device md10): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [1558 31287 0x0 SD] Oct 27 06:38:12 datacenter2 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 13817 does not match to the expected one 3 Oct 27 06:38:12 datacenter2 kernel: REISERFS error (device md10): vs-5150 search_by_key: invalid format found in block 200783002. Fsck? This error goes one for a while, but I thought this should be enough to get a clue as to what is going on. I can actually access the drive, but I have a red dot next to this drive. Can someone help me figure this out? Thanks!! First... you have a drive that has been marked as invalid because a "write" to it failed. That is why it is "RED" Second, you can still get to the files and contents of the drive because they are being simulated by the parity drive in combination with all the other data disks in your array. The failures you provided on your prior post are an indication of corruption in the file-system on disk10, but that is not as big an issue as the failed drive. It will prevent you from writing to the disk (even the simulated disk) until it is corrected, but one thing at a time. (The simulated disk has the corruption..., so it is not writable) First you must determine the cause of the failed write to disk10. It might be as simple as a loose connector, or it could be a defective disk, or a power supply unable to handle the combined load of all your disks and the one disk least able to deal with the poor supply voltage failed to complete a "write" operation. Step 1 is to attach a copy of your syslog to the next post you make. Since we have no idea which version of unRAID you are running we cannot give specific advice. DO NOT set a new disk configuration or press a "Restore" button. Either of those will immediately invalidate parity and make re-construction of a replacement disk impossible. Either will cause the loss of the contents of disk10.
October 27, 201015 yr Author First... you have a drive that has been marked as invalid because a "write" to it failed. That is why it is "RED" Second, you can still get to the files and contents of the drive because they are being simulated by the parity drive in combination with all the other data disks in your array. The failures you provided on your prior post are an indication of corruption in the file-system on disk10, but that is not as big an issue as the failed drive. It will prevent you from writing to the disk (even the simulated disk) until it is corrected, but one thing at a time. (The simulated disk has the corruption..., so it is not writable) First you must determine the cause of the failed write to disk10. It might be as simple as a loose connector, or it could be a defective disk, or a power supply unable to handle the combined load of all your disks and the one disk least able to deal with the poor supply voltage failed to complete a "write" operation. Step 1 is to attach a copy of your syslog to the next post you make. Since we have no idea which version of unRAID you are running we cannot give specific advice. DO NOT set a new disk configuration or press a "Restore" button. Either of those will immediately invalidate parity and make re-construction of a replacement disk impossible. Either will cause the loss of the contents of disk10. I have attached the syslog. I am running UnRaid 4.5.6 using a Corsair 650 PS. I have 19 drives + Parity. I did run the reiserfsck tool and it instructed me to run reiserfsck with the --rebuild-tree switch. Seeing you remark about the Power Supply, that stands out since I have so many drives. I will probably replace it with a heftier one since I am probably pushing it. syslog.zip
November 9, 201015 yr Author I thought that I had this fixed, but I am unable to write to my UnRaid system now. Looking at the syslog, it looks like I do have problems. I am not sure what they are, but something is not right. syslog.zip
November 9, 201015 yr I thought that I had this fixed, but I am unable to write to my UnRaid system now. Looking at the syslog, it looks like I do have problems. I am not sure what they are, but something is not right. Disk18, ( /dev/md18 ) has some file-system corruption: Nov 8 19:18:10 datacenter2 shfs: shfs_mkdir: mkdir: /mnt/disk18/Movies1/Blu-Ray/SPIDERMAN-II/BDMV (5) Input/output error Nov 8 19:18:10 datacenter2 kernel: REISERFS error (device md18): reiserfs-2025 reiserfs_cache_bitmap_metadata: bitmap block 207028224 is corrupted: first bit must be 1 Nov 8 19:18:10 datacenter2 kernel: REISERFS (device md18): Remounting filesystem read-only Nov 8 19:18:31 datacenter2 shfs: shfs_create: open: /mnt/disk18/Movies1/Blu-Ray/SPIDERMAN-II/BDMV/index.bdmv (30) Read-only file system
November 9, 201015 yr How to I correct the corruption of this block? Same method you used to repair the other file system corruption on the other disk. http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems
November 10, 201015 yr Author Just to put some closure on this issue. I ran the reiserfsck tool as Joe L. suggested. At first it took forever to boot up after I rebooted when the reiserfsck tool was totally completed. I looked at the syslog and all was clean. I am now able to write to my array once again. Thank you Joe L. for the help and patience you have in assisting us users!!
Archived
This topic is now archived and is closed to further replies.