htpcguru Posted September 24, 2017 Share Posted September 24, 2017 It has happened before. After a power-cycle/SSD re-seat, the cache pool came back alright. Just now one of the Windows 10 VM prompted an updated, which caused a crash of another running Windows 10 VM. After a "forced" reboot of unraid, the cache pool came back unmountable. It has happened before... power-cycling the box and re-seating the 2 SSD's fixed the issue. Any help is appreciated! tower-diagnostics-20170914-2105.zip (Cache pool good) tower-diagnostics-20170924-1601.zip (Cache pool unmountable) Quote Link to comment
JorgeB Posted September 24, 2017 Share Posted September 24, 2017 Lots of read and writes errors on one of your cache devices (cache2): Sep 24 16:01:11 Tower kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 38, rd 8855, flush 1, corrupt 0, gen 0 wr=write errors rd=read errors These are hardware errors, with SSDs this is usually a bad cable, replace it. Quote Link to comment
htpcguru Posted September 25, 2017 Author Share Posted September 25, 2017 15 hours ago, johnnie.black said: Lots of read and writes errors on one of your cache devices (cache2): Sep 24 16:01:11 Tower kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 38, rd 8855, flush 1, corrupt 0, gen 0 wr=write errors rd=read errors These are hardware errors, with SSDs this is usually a bad cable, replace it. Thanks for the tip. I replaced the cable AND moved cache2 to another SATA port on the motherboard as the new cable had the same issue. Had to re-install one of the Windows 10 VM's. The original ports are SATA1_2 (with 2 being on top of 1), cache1 still in SATA1, and now I've moved cache2 to SATA3 of SATA3_4. Not sure if SATA2 was the culprit. It's also possible the cache2 SSD could have some H/W issue. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.