November 28, 201312 yr hi! Just upgraded from 4.7 (after parity check and system check with 0 errors) and during the new permission script run, I got 19 errors on disk1 so far. Is that normal for this procedure? (upgraded to 5.03 stable) logs.txt
November 28, 201312 yr Author also my disks went to sleep and the procedure just stopped. Had to wake them up to continue..
November 28, 201312 yr hi! Just upgraded from 4.7 (after parity check and system check with 0 errors) and during the new permission script run, I got 19 errors on disk1 so far. Is that normal for this procedure? (upgraded to 5.03 stable) Errors are never normal. Disk1 is having read errors. Post a SMART report.
November 28, 201312 yr also my disks went to sleep and the procedure just stopped. Had to wake them up to continue.. This is odd. Disable spin-down and run it again.
November 29, 201312 yr Author I did run it again but unfortunately the procedure after a period of time stops... I memtesting at the moment ( i m pretty sure its ok. I did a couple of hours before the upgrade but I am retesting just to be sure) is there a way I can do the same procedure using the shell? is there a script available or something?
November 29, 201312 yr Author just to mention that I am running the script locally (newperms execution) and the procedure seems to work pretty nice and fast... dont know though what causes this issue when I run it from the web interface.
November 30, 201312 yr Author no but just realized that suspicious traffic was coming out from an old access point I have got... I replaced it with more advanced ap and mac filtered my wifi... I am sure that this was the problem as my unraid 5.03 no longer wakes up on its own (I had also this issue after the upgrade). I ll report when i double check everything...
November 30, 201312 yr Author thats sounds like a good reason for stopping the script I had some issues with the network the last few days which now are fixed... I believe that this also had to do with my script not running from the web... disk doesnt show any reallocated sectors and everything was fine before the update. Just to be sure I virus checked my PC, I ran 13 hours of memtest, checked every network station and everything looks clear... For an unknown reason ethtool wol option was changed to ug instead of g and that was the reason for those sudden wake ups... I am parity testing at the moment with no errors till now... hope I ll get it running soon...
Archived
This topic is now archived and is closed to further replies.