jongregory75

Steps: Stop array Remove devices from cache pool Unmount Remove Partitions Format (BTRFS) Mount Assign disks to cache pool Start array Still received the same failure. I erased the cache pool itself and created a new one. Assigned cache pool disks Started array Now its running ok What would have corrupted the cache pool itself? Last night I couldn't move files, delete, nothing was working.

I ended up clearing them, formatted btrfs, mounted but when I start the array, they say Unmountable: Unsupported or no file system. Diags attached. tower-diagnostics-20240223-0704.zip

in an attempt to just free up a few GB, I can't even delete /mnt/cache/data/trashcan Syslog continues to say anything on the cache pool is "Read-only file system". When I try running chmod anywhere on the cache pool it tells me its "read-only file system" Would the fact that I have mismatched cache pool drives? One is 500GB and one is 1TB.

So it's correctly set to none like you said. I've stopped the mover. Went to data share and manually started mover. secondary storage for appdata is set to none secondary storage for data is set to array but I'm seeing file: /mnt/cache/data/media/music/Luke Combs/Luke Combs - What You See Is What You Get [2019]/15. All Over Again.mp3 create_parent: /mnt/cache/data/media/music/Luke Combs/Luke Combs - What You See Is What You Get [2019] error: Read-only file system

Oh sorry, I did set is to none. Looked at the syslog and it was grinding away trying to move appdata. I miss-understood that for trying to skip app data. I should be trying to move /mnt/cache/data/media.

Meant /mnt/user/appdata/Plex-Media-Server

Scratch that, it's trying to move Plex metadata to disk8 but telling me "Read-only file system." Feb 22 20:09:40 Tower move: file: /mnt/disk8/appdata/Plex-Media-Server/Library/Application Support/Plex Media Server/Library/Application Support/Plex Media Server/Metadata/TV Shows/3/b65ba2804fa57d28ae7019fde0b9506857aabd7.bundle/Contents/_combined/posters/tv.plex.agents.series_72a5c9fda1932c1043859891f249a38b918dc4c7 So manually "chmod -R 777 to /mnt/disk8/appdata/Plex-Media-Server" ??

Just noticed that my /mnt/user/data share has Override Mover Tuning set to Yes. Should that be no? Ran mover manually and it's not executing.

Hmmm looks like cache is just full. Wonder why mover isn't working.

Plex wasn't working. Upgraded unassigned devices and OS, rebooted and can't get docker service to start. Something tells me my cache pool somehow went to SH!T. The server wasn't even being used to my knowledge. Thoughts? Diagnostics attached. Syslog displays: Feb 22 19:03:01 Tower avahi-daemon[14887]: Service "Tower" (/services/sftp-ssh.service) successfully established. Feb 22 19:03:05 Tower kernel: loop: Write error at byte offset 307298304, length 4096. Feb 22 19:03:05 Tower kernel: I/O error, dev loop2, sector 600192 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2 Feb 22 19:03:05 Tower kernel: loop: Write error at byte offset 38862848, length 4096. Feb 22 19:03:05 Tower kernel: I/O error, dev loop2, sector 75904 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2 Feb 22 19:03:05 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 248, rd 0, flush 0, corrupt 0, gen 0 Feb 22 19:03:05 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 249, rd 0, flush 0, corrupt 0, gen 0 Feb 22 19:03:05 Tower kernel: loop: Write error at byte offset 307429376, length 4096. Feb 22 19:03:05 Tower kernel: I/O error, dev loop2, sector 600448 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2 Feb 22 19:03:05 Tower kernel: loop: Write error at byte offset 38993920, length 4096. Feb 22 19:03:05 Tower kernel: I/O error, dev loop2, sector 76160 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2 Feb 22 19:03:05 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 250, rd 0, flush 0, corrupt 0, gen 0 Feb 22 19:03:05 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 251, rd 0, flush 0, corrupt 0, gen 0 Feb 22 19:03:05 Tower kernel: loop: Write error at byte offset 308150272, length 4096. Feb 22 19:03:05 Tower kernel: I/O error, dev loop2, sector 601856 op 0x1:(WRITE) flags 0x1800 phys_seg 23 prio class 2 Feb 22 19:03:05 Tower kernel: loop: Write error at byte offset 39714816, length 4096. Feb 22 19:03:05 Tower kernel: I/O error, dev loop2, sector 77568 op 0x1:(WRITE) flags 0x1800 phys_seg 23 prio class 2 Feb 22 19:03:05 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 252, rd 0, flush 0, corrupt 0, gen 0 Feb 22 19:03:05 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 253, rd 0, flush 0, corrupt 0, gen 0 Feb 22 19:03:05 Tower kernel: loop: Write error at byte offset 308101120, length 4096. Feb 22 19:03:05 Tower kernel: I/O error, dev loop2, sector 601760 op 0x1:(WRITE) flags 0x1800 phys_seg 2 prio class 2 Feb 22 19:03:05 Tower kernel: loop: Write error at byte offset 39665664, length 4096. Feb 22 19:03:05 Tower kernel: I/O error, dev loop2, sector 77472 op 0x1:(WRITE) flags 0x1800 phys_seg 2 prio class 2 Feb 22 19:03:05 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 254, rd 0, flush 0, corrupt 0, gen 0 Feb 22 19:03:05 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 255, rd 0, flush 0, corrupt 0, gen 0 Feb 22 19:03:05 Tower kernel: loop: Write error at byte offset 307937280, length 4096. Feb 22 19:03:05 Tower kernel: I/O error, dev loop2, sector 601440 op 0x1:(WRITE) flags 0x1800 phys_seg 2 prio class 2 Feb 22 19:03:05 Tower kernel: loop: Write error at byte offset 39501824, length 4096. Feb 22 19:03:05 Tower kernel: I/O error, dev loop2, sector 77152 op 0x1:(WRITE) flags 0x1800 phys_seg 2 prio class 2 Feb 22 19:03:05 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 256, rd 0, flush 0, corrupt 0, gen 0 Feb 22 19:03:05 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 257, rd 0, flush 0, corrupt 0, gen 0 Feb 22 19:03:05 Tower kernel: BTRFS: error (device loop2) in btrfs_commit_transaction:2494: errno=-5 IO failure (Error while writing out transaction) Feb 22 19:03:05 Tower kernel: BTRFS info (device loop2: state E): forced readonly Feb 22 19:03:05 Tower kernel: BTRFS warning (device loop2: state E): Skipping commit of aborted transaction. Feb 22 19:03:05 Tower kernel: BTRFS: error (device loop2: state EA) in cleanup_transaction:1992: errno=-5 IO failure tower-diagnostics-20240222-1931.zip

I've been slowly attempting to go through ibracorps documentation to install a variety of apps. It seems as I moved to the new unraid connect, things went sideways. I'm fairly sure my initial install setup had a ton of issues so I'm starting from scratch. Nuked the docker image to start fresh. Next is network setttings. What do I need to do here? Everything was working great until I got to traefik and then I can't even connect to unraid connect properly so there are problems with my network. tower-diagnostics-20230711-2231.zip

The order of operation is a little shady at this point but...found a preclear rpt from that drive that showed a preclear failure pointing to non-zero issue. Ran format on the disk1. Copied a small file to the disk. Stopped array. Restarted array. Everything was clean. Rebooted, all is well. unRAID format was done in under 20 secs, I had attempted to run preclear which would have taken 15hrs so lesson learned there. Im guessing I didn't format the drive when I added it to the array. What effect if any will there be on the parity disk? Should I run a parity check now that things are stable?

Latest diags and screenshot above.

Fixed cache issue, mover completed w/o issue, created usb backup, turned off a cron scheduler to eliminate error in syslog, shutdown, checked all connections, booted up. Disk1 shows new issue with partition. mediamonsterv3-diagnostics-20200306-0032.zip

Noticed the cache - prefer issue, changed to yes and mover is running. Once mover is done, I'll re-run diags and re-post .zip Yes - prior to mover kicking off. Saw that. I had to redo the 3.3v pin tape on two of the drives. Started from scratch, rebuilt parity disk, did pre-clear on all disks so any of that data in the syslog is old/not applicable. Haven't seen any SMART warnings on any of the disks. No backup yet, nothing on the current system is important. Will backup once mover finishes. Files I've moved to the array are fully backed up on separate computer so nothing is lost except time. Once mover is finished, I'll reboot and rerun diagnostics.