April 9, 201610 yr I was starting to notice an issue with my docker containers. the question is, is the issue my cache disk or my docker img file? Apr 8 23:15:05 Tower kernel: btrfs_dev_stat_print_on_error: 319324 callbacks suppressed Apr 8 23:15:05 Tower kernel: BTRFS: bdev /dev/sdd1 errs: wr 120, rd 251246343, flush 0, corrupt 0, gen 0 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#17 CDB: opcode=0x28 28 00 10 ab 34 e0 00 00 20 00 Apr 8 23:15:05 Tower kernel: blk_update_request: I/O error, dev sdd, sector 279655648 Apr 8 23:15:05 Tower kernel: BTRFS: bdev /dev/sdd1 errs: wr 120, rd 251246344, flush 0, corrupt 0, gen 0 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#18 CDB: opcode=0x28 28 00 10 ab 34 e0 00 00 20 00 Apr 8 23:15:05 Tower kernel: blk_update_request: I/O error, dev sdd, sector 279655648 Apr 8 23:15:05 Tower kernel: BTRFS: bdev /dev/sdd1 errs: wr 120, rd 251246345, flush 0, corrupt 0, gen 0 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#19 CDB: opcode=0x28 28 00 10 ab 34 e0 00 00 20 00 Apr 8 23:15:05 Tower kernel: blk_update_request: I/O error, dev sdd, sector 279655648 Apr 8 23:15:05 Tower kernel: BTRFS: bdev /dev/sdd1 errs: wr 120, rd 251246346, flush 0, corrupt 0, gen 0 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#20 CDB: opcode=0x28 28 00 10 ab 34 e0 00 00 20 00 Apr 8 23:15:05 Tower kernel: blk_update_request: I/O error, dev sdd, sector 279655648 Apr 8 23:15:05 Tower kernel: BTRFS: bdev /dev/sdd1 errs: wr 120, rd 251246347, flush 0, corrupt 0, gen 0 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#21 CDB: opcode=0x28 28 00 10 ab 34 e0 00 00 20 00 Apr 8 23:15:05 Tower kernel: blk_update_request: I/O error, dev sdd, sector 279655648 Apr 8 23:15:05 Tower kernel: BTRFS: bdev /dev/sdd1 errs: wr 120, rd 251246348, flush 0, corrupt 0, gen 0 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#22 CDB: opcode=0x28 28 00 10 ab 34 e0 00 00 20 00 Apr 8 23:15:05 Tower kernel: blk_update_request: I/O error, dev sdd, sector 279655648 Apr 8 23:15:05 Tower kernel: BTRFS: bdev /dev/sdd1 errs: wr 120, rd 251246349, flush 0, corrupt 0, gen 0 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#23 CDB: opcode=0x28 28 00 10 ab 34 e0 00 00 20 00 Apr 8 23:15:05 Tower kernel: blk_update_request: I/O error, dev sdd, sector 279655648 Apr 8 23:15:05 Tower kernel: BTRFS: bdev /dev/sdd1 errs: wr 120, rd 251246350, flush 0, corrupt 0, gen 0 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#24 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#24 CDB: opcode=0x28 28 00 10 ab 34 e0 00 00 20 00 Apr 8 23:15:05 Tower kernel: blk_update_request: I/O error, dev sdd, sector 279655648 Apr 8 23:15:05 Tower kernel: BTRFS: bdev /dev/sdd1 errs: wr 120, rd 251246351, flush 0, corrupt 0, gen 0 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#25 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#25 CDB: opcode=0x28 28 00 10 ab 34 e0 00 00 20 00 Apr 8 23:15:05 Tower kernel: blk_update_request: I/O error, dev sdd, sector 279655648 Apr 8 23:15:05 Tower kernel: BTRFS: bdev /dev/sdd1 errs: wr 120, rd 251246352, flush 0, corrupt 0, gen 0
April 9, 201610 yr Community Expert I would say that is the cache disk because it is referencing /dev/sdd1. If it was the docker image I would expect it to reference /dev/loop0.
April 9, 201610 yr Author It is my cache disk yes. It houses my docker img. It seems is gone read only and so all dockers luck up. Question being why is it going read only. I pulled it, added it to another system and ran the WD QUICK test and it checked OK. Added to a Linux system and it reads fine and can write to it too. So it's it bad or what? Why is unRAID making it read only. It did it Thursday so I rebooted and it worked, but by the end of Friday it read only again. Sent from my Nexus 6P using Tapatalk
April 9, 201610 yr Community Expert It is my cache disk yes. It houses my docker img. It seems is gone read only and so all dockers luck up. Question being why is it going read only. I pulled it, added it to another system and ran the WD QUICK test and it checked OK. Added to a Linux system and it reads fine and can write to it too. So it's it bad or what? Why is unRAID making it read only. It did it Thursday so I rebooted and it worked, but by the end of Friday it read only again. Sent from my Nexus 6P using Tapatalk unRAID will set a disk as read-only if any sort of file system corruption is detected. You should put the array into Maintenance mode, and then click on the cache disk to run a file system check on it.
April 9, 201610 yr Author OK. I was going to just replace it actually, but it has all my docker configs so I need to get those off somehow first. Because of the permissions, it isn't as simple as mount in new system cut and paste. May mount it usb as unassigned and see if I can get it off. Or, pull new drive, add back, copy off. Then Maintenance check maybe? Sent from my Nexus 6P using Tapatalk
April 9, 201610 yr Author It is my cache disk yes. It houses my docker img. It seems is gone read only and so all dockers luck up. Question being why is it going read only. I pulled it, added it to another system and ran the WD QUICK test and it checked OK. Added to a Linux system and it reads fine and can write to it too. So it's it bad or what? Why is unRAID making it read only. It did it Thursday so I rebooted and it worked, but by the end of Friday it read only again. Sent from my Nexus 6P using Tapatalk unRAID will set a disk as read-only if any sort of file system corruption is detected. You should put the array into Maintenance mode, and then click on the cache disk to run a file system check on it. I put the disk back. how do I run said test? I see stuff for smart test, but not file system check, unless of course my eyes are playing games
April 9, 201610 yr Author It is my cache disk yes. It houses my docker img. It seems is gone read only and so all dockers luck up. Question being why is it going read only. I pulled it, added it to another system and ran the WD QUICK test and it checked OK. Added to a Linux system and it reads fine and can write to it too. So it's it bad or what? Why is unRAID making it read only. It did it Thursday so I rebooted and it worked, but by the end of Friday it read only again. Sent from my Nexus 6P using Tapatalk unRAID will set a disk as read-only if any sort of file system corruption is detected. You should put the array into Maintenance mode, and then click on the cache disk to run a file system check on it. I put the disk back. how do I run said test? I see stuff for smart test, but not file system check, unless of course my eyes are playing games seems I do not see it because cache is formatted btrfs. can this be changed?
April 10, 201610 yr Author 1 Raw read error rate 0x000b 200 200 051 Pre-fail Always Never 0 3 Spin up time 0x0007 169 165 021 Pre-fail Always Never 4550 4 Start stop count 0x0032 096 096 040 Old age Always Never 4179 5 Reallocated sector count 0x0033 199 199 140 Pre-fail Always Never 3 7 Seek error rate 0x000a 200 200 051 Old age Always Never 0 9 Power on hours 0x0032 038 038 000 Old age Always Never 45948 (5y, 2m, 28d, 12h) 10 Spin retry count 0x0012 100 100 051 Old age Always Never 0 11 Calibration retry count 0x0012 100 100 051 Old age Always Never 0 12 Power cycle count 0x0032 100 100 000 Old age Always Never 225 194 Temperature celsius 0x0022 126 096 000 Old age Always Never 21 196 Reallocated event count 0x0032 198 198 000 Old age Always Never 2 197 Current pending sector 0x0012 200 200 000 Old age Always Never 0 198 Offline uncorrectable 0x0012 200 200 000 Old age Always Never 0 199 UDMA CRC error count 0x000a 200 253 000 Old age Always Never 1 200 Multi zone error rate 0x0008 200 200 051 Old age Offline Never 0 Done
April 10, 201610 yr Author scrub status for 1b60e5b1-39f5-4a77-a870-be87c2216efe scrub started at Sat Apr 9 13:53:12 2016 and finished after 00:18:54 total bytes scrubbed: 67.45GiB with 0 errors
Archived
This topic is now archived and is closed to further replies.