Energen Posted August 22, 2019 Share Posted August 22, 2019 I've been experiencing a number of problems within the last week or so, that all seemingly started out of nowhere.,,, last version upgrade maybe? I've had the GUI/server essentially crash for some unknown reason which was fine after a reboot, but I rebooted again last night to try and resolve some issues and ended up in a boot loop because the USB drive was not detected, or something. Got that resolved after a hard reset. I had a number of warnings about a drive or two with read errors yet all drives pass all checks. Currently my biggest problem is that some shares are read only even though read only was never set on any shares, and again started out of nowhere. I ran Docker Safe New Perms to go through everything and reset any permissions but I still have read only shares. I have a number of "some or all files are unprotected" on the Shares list because of these read only issues. The Mover gets jammed up in the log "UNRAID move: move: create_parent: /mnt/disk8/appdata error: Read-only file system" Fix Common Problems is currently giving me these two errors: Unable to write to cache Drive mounted read-only or completely full. Unable to write to Docker Image Docker Image either full or corrupted. What the hell is going on here? Last week when I was having read errors I put the array into maintenance mode and scanned all the drives, no errors reported, array restarted fine and didn't have any problems (known anyways) until now. My system log has a bunch of bad looking stuff in it .. is this all included in the diagnostics zip if it would help to figure anything out? Aug 21 23:20:07 UNRAID dhcpcd[1795]: br0: failed to renew DHCP, rebinding Aug 21 23:30:45 UNRAID kernel: BTRFS error (device sdl1): parent transid verify failed on 857849856 wanted 13396518 found 13393366 Aug 21 23:30:45 UNRAID kernel: BTRFS: error (device sdl1) in btrfs_run_delayed_refs:2935: errno=-5 IO failure Aug 21 23:30:45 UNRAID kernel: BTRFS info (device sdl1): forced readonly Aug 21 23:30:45 UNRAID kernel: print_req_error: I/O error, dev loop2, sector 0 Aug 21 23:30:45 UNRAID kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 1, rd 0, flush 1, corrupt 0, gen 0 Aug 21 23:30:45 UNRAID kernel: BTRFS warning (device loop2): chunk 13631488 missing 1 devices, max tolerance is 0 for writeable mount Aug 21 23:30:45 UNRAID kernel: BTRFS: error (device loop2) in write_all_supers:3716: errno=-5 IO failure (errors while submitting device barriers.) Aug 21 23:30:45 UNRAID kernel: BTRFS info (device loop2): forced readonly Aug 21 23:30:45 UNRAID kernel: BTRFS: error (device loop2) in btrfs_sync_log:3168: errno=-5 IO failure Aug 21 23:30:45 UNRAID kernel: loop: Write error at byte offset 17977344, length 4096. Aug 21 23:30:45 UNRAID kernel: print_req_error: I/O error, dev loop2, sector 35112 Aug 21 23:30:45 UNRAID kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 2, rd 0, flush 1, corrupt 0, gen 0 Aug 21 23:30:45 UNRAID kernel: BTRFS error (device loop2): pending csums is 12288 Aug 21 23:30:45 UNRAID kernel: BTRFS error (device sdl1): pending csums is 4096 Aug 21 23:30:47 UNRAID kernel: BTRFS warning (device sdl1): csum failed root 5 ino 4631484 off 131072 csum 0x1079e3d3 expected csum 0x73901347 mirror 1 Aug 21 23:30:47 UNRAID kernel: BTRFS warning (device sdl1): csum failed root 5 ino 4631484 off 262144 csum 0xafa74aad expected csum 0xfa3d3f16 mirror 1 So one thing at a time, how do I fix the read only issues? Thanks. Quote Link to comment
JorgeB Posted August 22, 2019 Share Posted August 22, 2019 10 minutes ago, Energen said: is this all included in the diagnostics zip if it would help to figure anything out? Yes. Quote Link to comment
Energen Posted August 22, 2019 Author Share Posted August 22, 2019 (edited) Figured so, here's the diags. Edited August 22, 2019 by Energen Quote Link to comment
JorgeB Posted August 22, 2019 Share Posted August 22, 2019 Cache filesystem is corrupt, can't see why because the problem happened before this reboot, but there are some write errors, backup any data there and re-format it, docker image will also need to be recreated. Quote Link to comment
Energen Posted August 22, 2019 Author Share Posted August 22, 2019 What about the read only shares though? The cache is trying to write to the shares, yet I can't find anywhere that they could be set to read only, or any reason why they would have been set to read only. Appdata is read only also, somehow. Those are my two biggest problems. Quote Link to comment
JorgeB Posted August 22, 2019 Share Posted August 22, 2019 First fix the cache problem, corruption on one filesystem can affect the same shares on other filesystems, if still issues after that post new diags. Quote Link to comment
Energen Posted August 22, 2019 Author Share Posted August 22, 2019 Ok will try that first. Thanks for the help. I'll try to move any files off the cache drive and remove it from the array and go from there. Quote Link to comment
Energen Posted August 23, 2019 Author Share Posted August 23, 2019 So I haven't had any more issues since removing this cache drive.... it seems it was the root of all problems! Lost my VMs since I couldn't move over the files but there was nothing essential there, and dockers reinstalled with no major issues. My cache drive was a 7-8 month old Mushkin SSD.... I guess it didn't work out too well. I'll eventually look to replace that. Thanks for the help. Quote Link to comment
JorgeB Posted August 24, 2019 Share Posted August 24, 2019 The SSD itself should be fine, though can't say for sure what caused the write errors without the logs from when it happened. Quote Link to comment
Energen Posted August 25, 2019 Author Share Posted August 25, 2019 For whatever it's worth, the SMART attributes said the drive failed .. "SMART overall-health:Failed" and when I tried to preclear the drive for removal it failed preclear/erase also... I've already opened up a warranty claim to RMA it just to be safe, but I won't use the replacement for anything critical. Quote Link to comment
JorgeB Posted August 26, 2019 Share Posted August 26, 2019 On 8/25/2019 at 2:11 AM, Energen said: For whatever it's worth, the SMART attributes said the drive failed .. "SMART overall-health:Failed" In that case it should be replaced. 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.