dzyuba86

I ran a non correcting check as you suggested and it came up with 0 errors. Also my telegram bot now says my health passes instead of fails. SO I'm going to assume this is resolved and can be flagged as solved. Thanks.

Should I be worried about this? For clarity and back story. I had a drive fail so I replaced it. A week later another drive failed so I replaced that one as well (These are my old 3TB drives I've been replacing). This month when it ran it's monthly parity check it took a very long time and found this many errors.. Just wondering if there is any cause for alarm or leave it be?

So I'm looking at adding VM capability to my unraid server to double down as a part time gaming rig for light to medium gaming. I currently have: Asus TUF gaming X570 PLUS motherboard Ryzen 5950X cpu 16GB ram (will add more Nvidia p2200 quadro GPU. Can I add a RTX card and use that for the passthrough for VM's and keep the quaddro for Plex transcoding only? Since the motherboard supports dual GPU's. I'm planning to add a 2.5" ssd for VM use only, the M.2 drives I have are for cache and downloads. Thanks in advance

Been seeing these more often than usual and not sure why they are popping up. plexnas-diagnostics-20230220-0952.zip

Last night I was doing some docker updates and going through sonarr to manually find missing episodes for sone older shows. This morning I woke up to a powered down server. I have auto power on set in bios after a power loss. And no settings to power off for anything. Nor did I initiate a shut down sequence. I attached the diag log and hope someone can find why it self powered down as I still haven't learned my way around these logs so I'm not even sure where to look for the cause of this issue in them. Thank you plexnas-diagnostics-20221217-0959.zip

4 hours in now. No errors found yet. It's on pass#4 now. I doubt it'll find anything now. At this point I think my only option is to reformat the drive. lose the data and have radarr/sonarr re-acquire what I lose on that drive. I really have no other idea what I can do now. Also thinking that the 8TB drive that was in that slot is still good. SO I'll use it to replace disk 6 which is showing old age pre-fail errors.

This is disk 6 repair output Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... done

Disk 6 claims to have 158 errors on the "Main" dashboard. Disk 7 is green light now but still saying unmountable no file system present.

Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata sb_icount 64, counted 32 sb_ifree 61, counted 29 sb_fdblocks 1952984849, counted 1952984853 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 4 - agno = 5 - agno = 6 - agno = 3 - agno = 2 - agno = 7 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... SB summary counter sanity check failed Metadata corruption detected at 0x47a15b, xfs_sb block 0x0/0x200 libxfs_bwrite: write verifier failed on xfs_sb bno 0x0/0x1 SB summary counter sanity check failed Metadata corruption detected at 0x47a15b, xfs_sb block 0x0/0x200 libxfs_bwrite: write verifier failed on xfs_sb bno 0x0/0x1 xfs_repair: Releasing dirty buffer to free list! xfs_repair: Refusing to write a corrupt buffer to the data device! xfs_repair: Lost a write to the data device! fatal error -- File system metadata writeout failed, err=117. Re-run xfs_repair.

Rebuild finished. Here's the diag log. Doing the check now. plexnas-diagnostics-20221204-0954.zip

I've done a check with -nv parameter several times now. Not sure what else to do to make it stop showing as an unmountable disk.

I currently have brand new 10TB Seagate ironwolfs in disk 1 and 7 and it's running a rebuild. Disk 7 is still showing unmountable: unknown or no file system message though. Seems like my disk 7 is really messed up.

Claims data rebuild was complete but disk 7 still showing same error on dashboard. I pulled a diagnostic log. Going to shut down and re-balance the power load on the wires to see if it'll help. And I can put the new 10TB drive in. Looks like the 3TB drive has too many reallocated sectors so it's in a pre-fail stage. I'll use the RMA drive I'll get in a few weeks to swap that one out. plexnas-diagnostics-20221202-1842.zip

Smart test for Disk 6. plexnas-smart-20221202-1537.zip

I'll check in a few hours once parity check finishes. I check my dashboard 5+ times a week but don't have email alerts set up. Might need to set something up at this point. Also picked up 2 new drives to replace the RMA 10TB drive and the 8TB that's having issues.

Adding 2 more drives I needed to add a new splitter. I'm probably overloading the port on the power supply. When I get home I'll add another modular plug and split the power load between 2 and see if that helps. I believe currently 12 drives are on one mod plug.

Sata splitter. I'm thinking to maybe go to the computer shop and see if they have better modular plugs for my power supply. No, no smart errors on dashboard which is super odd. Unless the error corrected itself?

I got a error popup for an error and when I clicked on it l, it went away and I forgot which disk. So I can't answer that for sure.

Yes. I'm using three 1 to 4 power splitter.

Here's the log. Rebuild failed half way. plexnas-diagnostics-20221202-0748.zip

It's currently running a re-build on the 8TB. The 10 is shot and I'm sending it out for a RMA. I'll pick one up at the local tech shop to rebuild since it'll take 1-2 weeks to get the warranty replacement. One of my 3TB drives is throwing pre-fail errors so I'll swap it with a 10. If rebuild fails I'll pull a diagnostic log and post. All I did was deselect the disk from the slot then reassign it and it started the rebuild. Not sure if the smart test reset something on the drive or my deselect, spin up and select to rebuild did the trick.

I downloaded and ran seagate diagnostics tools. The 8TB drive passes the smart test and my laptop can see the drive no problem. Then 10TB drive comes up as uninitialized right away, fails to pass any smart test and I get a failed CRC error when I try to initialize the disc. Will check with warranty support tomorrow about a replacement. I have 1 more year of warranty on it. Still need to figure out what to do about the 8TB and why it isn't working.

Would it make sense to pull the drive out, format through my sata enclosure with my laptop and put back in to rebuild or no? The 2 drives having problems are the 2nd newest drives in my array

Tried doing a rebuild and it failed 1 minute in. Guessing my disk is shot?

Now disk 7 reading as unassigned device. plexnas-diagnostics-20221130-1330.zip