abhi.ko

Members
 View Profile  See their activity

  • Posts

    344

  • Joined

  • Last visited

 Content Type 

Report Comments posted by abhi.ko

    Unraid OS version 6.9.0-rc1 available

    in Prereleases

    Posted

    8 hours ago, touz said:

    Did you solve this issue? I'm on RC2 and everytime I reboot via the WebUI I get a parity check. It wasn't happening on the latest stable release.

    No I did not, and that was exactly what was happening with my upgrade too. So I downgraded and went back to 6.8.3 stable and everything is fine, no issues what so ever, nothing changed other than the version of unRaid. I had this happen twice - once with 6.9beta and RC1 - so I am pretty sure it is something related to the code changes, I have no idea what. I did post my diagnostics but did not get any feedback on it.

     

    Another thing, which I believe is related, is what happened with my NVME cache drive, 6.9 RC showed errors related to the NVME drive (Samsung 980 Pro 1TB on an M.2 slot) and after that it became unavailable and all my cache content with it. So I switched to another SSD on hand and rebuilt everything again, was planning to remove the m.2 drive and RMA it but strangely enough on the next reboot it came back as unassigned with no data loss - with all the appdata and VM's intact. I was running it on 6.8.3 until recently, moved it to my windows machine last week. So something is up, doesn't seem like 6.9.3RC doesn't like my hardware/setup.

     

    @touz do you have any nvme drives in your build - what hardware are you using?

    Unraid OS version 6.9.0-rc1 available

    in Prereleases

    Posted · Edited by abhi.ko

    5 hours ago, trurl said:

     

    I understand the reasons why for an unclean shutdown. 

     

    Just trying to figure out why this wasn't a problem before the upgrade on 6.8.3, I had even rebooted the server yesterday morning and it had gracefully shutdown and came back up without any issues. I did not change the location of the flash drive or anything else between that reboot and the upgrade reboot. Hence the thought that this might be an issue with the upgrade.

     

    In fact I had tried to upgrade previously (beta 35 I believe) and had the same issue while stopping and starting the array, it always comes back as unclean and starts parity check. So decided to go back to the stable version, now the rc came out and decided to try again and wanted to report it. Seems like there is at least another user with the same issue, @ClunkClunk. 

     

    Was there anything in the logs and what is with the error related to my nvme drive, that is also new after the upgrade.