B1G Posted October 20, 2016 Share Posted October 20, 2016 I am on version 5.0.6. I haven't changed a thing in over a year, apart from changing up two drives a few months ago. Now for the fourrh time in a little over a week everything freezes up. It all seems random. This is what the screen looks like At this point the only thing I can do is press reset! Can anyone shed some light on this for me.. I don't see anything abnormal in the logs... actually I can't see a log dated with the actual crash time Sent from my iPhone using Tapatalk Link to comment
JorgeB Posted October 20, 2016 Share Posted October 20, 2016 Check file system on all disks. Link to comment
B1G Posted October 21, 2016 Author Share Posted October 21, 2016 Disk all are working properly. Parity check came out with no errors. What should I be looking for in the File System ? Link to comment
JorgeB Posted October 21, 2016 Share Posted October 21, 2016 You'd be looking for file system corruption, since the crash seems to be caused by reiserfs, this as nothing to do with disk health and/or parity. https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_ReiserFS_using_unRAID_v5_or_later Link to comment
itimpi Posted October 21, 2016 Share Posted October 21, 2016 Disk all are working properly. Parity check came out with no errors. What should I be looking for in the File System ? You should stop the array and restart it in Maintenance mode. Having done that for each disk from a console/telenet session run a command of the form: reiserfsck --check /dev/mdX where X corresponds to the disk to be checked. Note that this command can take a long time to run (hours) so if using a telnet session to run the command you need to keep it open for the duration. If any errors are found then reiserfsck normally suggest the extra parameters that need to be used on a rerun to fix the detected corruption, but it might be a good idea to check back here first as running the wrong command can lead to data loss. Link to comment
B1G Posted October 23, 2016 Author Share Posted October 23, 2016 Thank you both. I will be doing that now and reporting back what ever I get Link to comment
B1G Posted October 23, 2016 Author Share Posted October 23, 2016 Quick question... I just had to RESET again... Now the system is doing a parity check. Can I stop the partiy check.. Put the parity offline and then do the reiserfsck check ? Link to comment
JorgeB Posted October 23, 2016 Share Posted October 23, 2016 You can cancel the parity check, no need to put the parity offline, whatever that means, just start in maintenance mode and check filesystem on all disks. Link to comment
B1G Posted October 23, 2016 Author Share Posted October 23, 2016 .. lol... I meant Array offline .... Thanks Link to comment
itimpi Posted October 23, 2016 Share Posted October 23, 2016 .. lol... I meant Array offline .... Thanks you want the array to be online in Maintenance mode. You can then run the file system check against the /dev/mdX devices (where X corresponds to the disk number in the unRAID GUI). This will ensure that parity remains valid while doing the check (and any subsequent repair). Link to comment
B1G Posted October 24, 2016 Author Share Posted October 24, 2016 Ok, got the following message from reiserfsck.... Sent from my iPhone using Tapatalk Link to comment
JorgeB Posted October 24, 2016 Share Posted October 24, 2016 You need to run reiserfsck with --rebuild-tree for that disk. Link to comment
B1G Posted October 24, 2016 Author Share Posted October 24, 2016 Sent from my iPhone using Tapatalk Link to comment
B1G Posted October 24, 2016 Author Share Posted October 24, 2016 That is the screen message I got from disk 2 . Link to comment
JorgeB Posted October 24, 2016 Share Posted October 24, 2016 You need to run reiserfsck with --rebuild-tree for that disk. Link to comment
B1G Posted October 24, 2016 Author Share Posted October 24, 2016 Sent from my iPhone using Tapatalk Thanks... And sorry from the post mixup ... I did something on the iphone and then on the computer and it got mixed up Link to comment
B1G Posted October 24, 2016 Author Share Posted October 24, 2016 You need to run reiserfsck with --rebuild-tree for that disk. I guessing this is done in Maintenance mode? Link to comment
JorgeB Posted October 24, 2016 Share Posted October 24, 2016 Yes, start in maintenance mode and run: reiserfsck --rebuild-tree /dev/md2 Link to comment
B1G Posted October 25, 2016 Author Share Posted October 25, 2016 Yes, start in maintenance mode and run: reiserfsck --rebuild-tree /dev/md2 Thanks, that did the job. I love the quick replies on this forum. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.