syslog.txt

 

 

Overnight my cache drive is falling over and causing all sorts of havoc. The drive isn't that old... It is an SSD. 

 

 

What can I do? 

SSD dropped offline:

 

Feb 27 03:04:33 Tower kernel: ata10: softreset failed (1st FIS failed)
Feb 27 03:04:33 Tower kernel: ata10: reset failed, giving up
Feb 27 03:04:33 Tower kernel: ata10.00: disabled

With SSDs this happens mostly when there's a cable problem.

I've rebooted the system... unraid says the disk needs to be formatted..

 

 

Feb 27 08:39:37 Tower emhttp: shcmd (50): mkdir -p /mnt/cache
Feb 27 08:39:37 Tower emhttp: shcmd (51): set -o pipefail ; mount -t btrfs -o noatime,nodiratime /dev/sdb1 /mnt/cache |& logger
Feb 27 08:39:37 Tower kernel: BTRFS info (device sdb1): disk space caching is enabled
Feb 27 08:39:37 Tower kernel: BTRFS info (device sdb1): has skinny extents
Feb 27 08:39:37 Tower kernel: BTRFS info (device sdb1): detected SSD devices, enabling SSD mode
Feb 27 08:39:37 Tower kernel: BTRFS warning (device sdb1): sdb1 checksum verify failed on 1035763712 wanted E23EB638 found 50A857D5 level 1
Feb 27 08:39:37 Tower kernel: BTRFS: error (device sdb1) in btrfs_recover_log_trees:5619: errno=-5 IO failure (Couldn't read tree log root.)
Feb 27 08:39:37 Tower kernel: BTRFS: error (device sdb1) in btrfs_replay_log:2506: errno=-5 IO failure (Failed to recover log tree)
Feb 27 08:39:37 Tower kernel: BTRFS info (device sdb1): delayed_refs has NO entry
Feb 27 08:39:37 Tower kernel: BTRFS error (device sdb1): cleaner transaction attach returned -30
Feb 27 08:39:37 Tower root: mount: /dev/sdb1: can't read superblock
Feb 27 08:39:37 Tower emhttp: err: shcmd: shcmd (51): exit status: 32
Feb 27 08:39:37 Tower emhttp: mount error: No file system (32)
Feb 27 08:39:37 Tower emhttp: shcmd (52): umount /mnt/cache |& logger
Feb 27 08:39:37 Tower kernel: BTRFS error (device sdb1): open_ctree failed
Feb 27 08:39:37 Tower root: umount: /mnt/cache: not mounted
Feb 27 08:39:37 Tower emhttp: shcmd (53): rmdir /mnt/cache

Anything I can do about this or do I need to format it? 

If there's important data you can try these recovery options:

 

https://lime-technology.com/forums/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490

 

If there's no important data or none of the recovery options work format it.

--repair got things rolling again. 

 

Strange that this has happened two nights in a row now. 

Don't forget to replace the cables.

I did. swapped it right away.