I can't blame the upgrade, but I wanted to post

 

Just got home after working away, the plan was to add 2x 8TB drives following upgrading to the latest release. 11PM at night after being home 5 mins seemed like a good time to attempt this.

 

Upgraded, Rebooted and my motherboard wouldn't post with 0d error. Great start.

After checking everything many times, my monitor cable wasn't plugged in. Not sure why this would stop my system even posting.

System booted up OK and the SSD was still present. I had just removed 1 drive that was unassigned as well.

 

Realised there isn't a DVB update yet and I should have waited. Even more so after this.

 

Added the two 8TB drives and attempted to power on my system the leds just flashed once. PSU cuts out. I check everything again, remove the new drives. End up unplugging most stuff on the PSU. Progress.

End result highlighted my system will not post with the  SSD that's only a few months old power cable plugged in.

Verified it's not the power cable, wherever I place the SSD I can't post. 

 

That did not go to plan.

 

Edit.... Lost the 2TB drive too. I can rebuild that but need to preclear. See if the rest lasts as well

Edited September 22, 20178 yr by Tuftuf

This is much more a hardware related issue than anything implied by the new unRAID release.

 

Yes, unlike HDDs that's usually how an SSD fails, it's working fine, you reboot or power cycle and it's gone.

I blame myself for power cycling the machine so many times when doing the 0d post error and somehow it just meant no display connected.

 

It killed a 500GB SSD that amazon will replace as its 3 or 5 months old and a 4-5 year old 2TB drive. 

Instead of just adding two drives I now need to rebuild 2TB onto an 8TH and then replace parity with 8TB.

 

Think it might be easier to copy the data of the emulated disk and reset config.