April 13, 201214 yr I've been having issues for about a month or so with my server ever since, I tried to replace a Samsung F4 drive to update its FW, which I didn't have to even do. When I replaced the drive with a WD, I had all my drives with errors, and all my drives were set to read only. I've fix those errors, and I've added the F4 drive to the array. Now, I've got 10979 parity errors, which I would like your help on fixing them prior to jumping to unraid version 5.0betas. Thank you for all your help in advanced. syslog-2012-04-13.txt
April 13, 201214 yr Author New system log. After the parity check was completed, I ran Zappiti because I added a new movie. After scanning my media with Zappiti, it stated a movie need to be cleaned up, which mean a movie pretty much was deleted. I check the movie, and the folder was there, but the file was gone. This is weird because my kids watched the movie yesterday, and today is gone after the parity check. I'll going to run the check scrip on all my drives (except parity) to make sure they are all ok. syslog-2012-04-13_1.txt
April 13, 201214 yr Disk 1 has a file system error. Apr 13 11:50:33 Tower kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=3, free_space=38959 rdkey Apr 13 11:50:33 Tower kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 72357202. Fsck? Apr 13 11:50:33 Tower kernel: REISERFS (device md1): Remounting filesystem read-only See here: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems This can be caused by an unclean shutdown. Always use the unRAID web GUI to shutdown or reboot. Power problems can also cause this.
April 13, 201214 yr Author Disk 1 has a file system error. Apr 13 11:50:33 Tower kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=3, free_space=38959 rdkey Apr 13 11:50:33 Tower kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 72357202. Fsck? Apr 13 11:50:33 Tower kernel: REISERFS (device md1): Remounting filesystem read-only See here: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems This can be caused by an unclean shutdown. Always use the unRAID web GUI to shutdown or reboot. Power problems can also cause this. I just finished running the Check Disk for all of my drives. MD1 was aborted. I ran the check disk again, and it found not errors. I ran it a third time just to make sure, and it found no errors. I ran the check disk for the remaining disk, and all 5 came up with not errors. But now, I've got new error ata 2 in my system log, which I've attached. syslog-2012-04-13_1.txt
April 13, 201214 yr This describes the error a how to troubleshoot: http://lime-technology.com/wiki/index.php/The_Analysis_of_Drive_Issues#Drive_interface_issue_.233
April 14, 201214 yr Author This describes the error a how to troubleshoot: http://lime-technology.com/wiki/index.php/The_Analysis_of_Drive_Issues#Drive_interface_issue_.233 Thanks, I turned off my server, and re-arranged my drives power power connector, and the issue went away. I'm going to run another parity check and see if the parity errors are still present.
April 14, 201214 yr Author I do not show any more parity errors, but I still show Apr 14 02:37:56 Tower kernel: NTFS driver 2.1.29 [Flags: R/O MODULE]. (System) Why does it keep doing this when all of my drives have been precleared prior to being set in my array? Furthermore, what's the meaning of the minor errors? I will run another parity check. syslog-2012-04-14.txt
April 14, 201214 yr because the module loads no matter if you need it of not. Do not worry about the message
April 14, 201214 yr Author because the module loads no matter if you need it of not. Do not worry about the message Okie dokie. Sounds good! I will close the post unless I get more errors when I conduct another parity check tonight. Thanks for your help.
Archived
This topic is now archived and is closed to further replies.