October 13, 20169 yr Hi All, I was trying to make VirtualBox + Vagrant work under my Ubuntu VM but found that this was not supported in the current version. I upgraded to 6.2.1 and although the VM is now working and fully supports VirtualBox, it seems I am no longer able to select a Parity. Upon boot it says that the Parity disk is not recognized. I tried moving it to Disk 2, it goes through a check, but then shows the same error. Setup is as follows: Parity: 4tb wd red Disk 1: 4tb wd red Cache 1: 250gb corsair bx100 Cache 2: 250gb corsair bx100 Am I missing something? Thanks, Rj ein-diagnostics-20161014-1543.zip
October 14, 20169 yr Community Expert I would suggest that you attach a diagnostics file with your next post. (That will give the real gurus something to work with!) 'Tools' >>> 'Diagnostics'
October 14, 20169 yr Author Thanks Frank1940! I've attached the diagnostics file. ein-diagnostics-20161014-1543.zip
October 16, 20169 yr Author I tried the procedure listed on this thread: https://lime-technology.com/forum/index.php?topic=48812.0 Stop Array, Remove Disk, Start Array, Stop Array, Add Disk, Rebuild. Still no luck. Attaching latest diagnostics report. ein-diagnostics-20161016-1815.zip
October 16, 20169 yr Community Expert You are getting a lot of what look like interface errors, try swapping both disk cables and a different SATA port. If issue remains do an extend SMART test on that disk.
October 16, 20169 yr Author Hi johnnie.black, thanks for the response! Whenever I try to do an extended SMART test I get the error: Interrupted (host reset) Attaching latest SMART report generated by the download button... ein-smart-20161016-1851.zip
October 16, 20169 yr Community Expert If you swapped both disk cables and SATA port it's probably a bad disk.
October 16, 20169 yr Author Decided to swap the drives' sata port on the motherboard. Rebooted and it is now doing a parity-sync/data-rebuild. Will leave it to do its thing overnight, will come back to this thread to report. Cross fingers things are now good. Do you know the reason why this happen to have happened same time as my upgrade to 6.2.1? Thank you so much johnnie.black.
October 16, 20169 yr Community Expert Do you know the reason why this happen to have happened same time as my upgrade to 6.2.1? Coincidence.
Archived
This topic is now archived and is closed to further replies.