Tydell

Members
  • Posts

    19
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Tydell's Achievements

Newbie

Newbie (1/14)

3

Reputation

  1. Nope, no issues....works out of the box. Bought a QNAP QSW-308-1C that works perfectly with it.
  2. The whole system has one nvidia gpu that's passed through to a vm and then the igpu that isn't passed through, per se, but is set up to be used in the plex docker container. The only thing I wish I had now was an ipmi port. That would make this whole build just about perfect. A couple other notes: some of the PCIE slots on this motherboard share lanes with the sata controller, so if you use some of the PCIE ports, it'll disable some of your onboard sata. Of note though, I used a SAS expander in my last PCIE slot that only pulls power from the PCIE slot - it doesn't use any actual data. That particular port did not disable the corresponding sata ports. If I think of any other gotchas, i'll post them here.
  3. Yep, I was able to use the igpu to transcode 4k content - it does the job just fine! I'm also currently passing a GPU I had laying around through to a VM for ethereum mining and it works great as well. I used the ACS Override setting to break up my IOMMU groups so all the devices have their own IOMMU group. I believe I had to do that in order to get the GPU to pass through to the VM. Overall, very happy with the build.
  4. It would appear that you, sir, are correct! Copying everything over now. Thanks again for all your help! Time for a 2nd parity drive, methinks.
  5. Oops, thanks for that! That worked! Still doesn't mount though Jul 5 08:59:29 Unraid kernel: XFS (sdc1): Corruption warning: Metadata has LSN (1:22491) ahead of current LSN (1:2). Please unmount and run xfs_repair (>= v4.3) to resolve. Jul 5 08:59:29 Unraid kernel: XFS (sdc1): log mount/recovery failed: error -22 Jul 5 08:59:29 Unraid kernel: XFS (sdc1): log mount failed Jul 5 08:59:29 Unraid unassigned.devices: Mount of '/dev/sdc1' failed: 'mount: /mnt/disks/Hitachi_HDS723030ALA640_MK0311YHG033ZA: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error. ' Jul 5 08:59:29 Unraid kernel: XFS (sdc1): Corruption warning: Metadata has LSN (1:22491) ahead of current LSN (1:2). Please unmount and run xfs_repair (>= v4.3) to resolve. Jul 5 08:59:29 Unraid kernel: XFS (sdc1): log mount/recovery failed: error -22 Jul 5 08:59:29 Unraid kernel: XFS (sdc1): log mount failed Jul 5 08:59:29 Unraid unassigned.devices: Mount of '/dev/sdc1' failed: 'mount: /mnt/disks/Hitachi_HDS723030ALA640_MK0311YHG033ZA: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error. ' These errors are usually a bad SATA cable, please post a SMART report for that disk. Attached. Lots of UDMA_CRC_Error_Count. Hitachi_HDS723030ALA640_MK0311YHG033ZA-20210705-0900.txt
  6. @JorgeB & @trurl - Thank you both for your help! My folder is back and I'll be going through now to see if there are any missing files. Lost+Found only has about 600KB of total stuff in it, and no important files that I recognize or can really see the contents of in notepad.
  7. I might have evidence now - It won't mount in unassigned devices - says it has a dup UUID. I haven't done what it suggests yet (running xfs_repair with the -L flag) I running xfs_repair -nv on it is not going well.: xfs_repair -nv /dev/sdc Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... ......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... The system log file also threw some errors during the check: Jul 5 08:30:37 Unraid kernel: ata4.00: exception Emask 0x10 SAct 0x180000 SErr 0x280100 action 0x6 frozen Jul 5 08:30:37 Unraid kernel: ata4.00: irq_stat 0x08000000, interface fatal error Jul 5 08:30:37 Unraid kernel: ata4: SError: { UnrecovData 10B8B BadCRC } Jul 5 08:30:37 Unraid kernel: ata4.00: failed command: READ FPDMA QUEUED Jul 5 08:30:37 Unraid kernel: ata4.00: cmd 60/3f:98:00:30:03/05:00:00:00:00/40 tag 19 ncq dma 687616 in Jul 5 08:30:37 Unraid kernel: res 50/00:c1:3f:35:03/00:02:00:00:00/40 Emask 0x10 (ATA bus error) Jul 5 08:30:37 Unraid kernel: ata4.00: status: { DRDY } Jul 5 08:30:37 Unraid kernel: ata4.00: failed command: READ FPDMA QUEUED Jul 5 08:30:37 Unraid kernel: ata4.00: cmd 60/c1:a0:3f:35:03/02:00:00:00:00/40 tag 20 ncq dma 360960 in Jul 5 08:30:37 Unraid kernel: res 50/00:c1:3f:35:03/00:02:00:00:00/40 Emask 0x10 (ATA bus error) Jul 5 08:30:37 Unraid kernel: ata4.00: status: { DRDY } Jul 5 08:30:37 Unraid kernel: ata4: hard resetting link Jul 5 08:30:37 Unraid kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 5 08:30:37 Unraid kernel: ata4.00: configured for UDMA/133 Jul 5 08:30:37 Unraid kernel: ata4: EH complete Jul 5 08:30:39 Unraid kernel: ata4.00: exception Emask 0x10 SAct 0x80800000 SErr 0x280100 action 0x6 frozen Jul 5 08:30:39 Unraid kernel: ata4.00: irq_stat 0x08000000, interface fatal error Jul 5 08:30:39 Unraid kernel: ata4: SError: { UnrecovData 10B8B BadCRC } Jul 5 08:30:39 Unraid kernel: ata4.00: failed command: READ FPDMA QUEUED Jul 5 08:30:39 Unraid kernel: ata4.00: cmd 60/3f:b8:00:00:0e/05:00:00:00:00/40 tag 23 ncq dma 687616 in Jul 5 08:30:39 Unraid kernel: res 50/00:c1:3f:05:0e/00:02:00:00:00/40 Emask 0x10 (ATA bus error) Jul 5 08:30:39 Unraid kernel: ata4.00: status: { DRDY } Jul 5 08:30:39 Unraid kernel: ata4.00: failed command: READ FPDMA QUEUED Jul 5 08:30:39 Unraid kernel: ata4.00: cmd 60/c1:f8:3f:05:0e/02:00:00:00:00/40 tag 31 ncq dma 360960 in Jul 5 08:30:39 Unraid kernel: res 50/00:c1:3f:05:0e/00:02:00:00:00/40 Emask 0x10 (ATA bus error) Jul 5 08:30:39 Unraid kernel: ata4.00: status: { DRDY } Jul 5 08:30:39 Unraid kernel: ata4: hard resetting link Jul 5 08:30:40 Unraid kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 5 08:30:40 Unraid kernel: ata4.00: configured for UDMA/133 Jul 5 08:30:40 Unraid kernel: ata4: EH complete Jul 5 08:31:50 Unraid kernel: ata4.00: exception Emask 0x10 SAct 0xc00 SErr 0x280100 action 0x6 frozen Jul 5 08:31:50 Unraid kernel: ata4.00: irq_stat 0x08000000, interface fatal error Jul 5 08:31:50 Unraid kernel: ata4: SError: { UnrecovData 10B8B BadCRC } Jul 5 08:31:50 Unraid kernel: ata4.00: failed command: READ FPDMA QUEUED Jul 5 08:31:50 Unraid kernel: ata4.00: cmd 60/3f:50:00:58:4c/05:00:01:00:00/40 tag 10 ncq dma 687616 in Jul 5 08:31:50 Unraid kernel: res 50/00:c1:3f:5d:4c/00:02:01:00:00/40 Emask 0x10 (ATA bus error) Jul 5 08:31:50 Unraid kernel: ata4.00: status: { DRDY } Jul 5 08:31:50 Unraid kernel: ata4.00: failed command: READ FPDMA QUEUED Jul 5 08:31:50 Unraid kernel: ata4.00: cmd 60/c1:58:3f:5d:4c/02:00:01:00:00/40 tag 11 ncq dma 360960 in Jul 5 08:31:50 Unraid kernel: res 50/00:c1:3f:5d:4c/00:02:01:00:00/40 Emask 0x10 (ATA bus error) Jul 5 08:31:50 Unraid kernel: ata4.00: status: { DRDY } Jul 5 08:31:50 Unraid kernel: ata4: hard resetting link Jul 5 08:31:51 Unraid kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 5 08:31:51 Unraid kernel: ata4.00: configured for UDMA/133 Jul 5 08:31:51 Unraid kernel: ata4: EH complete I think she's dead!
  8. I have no evidence yet - I'll definitely be investigating. I do still have the old drive, although it's unseated slightly from its hot swap bay. It's weird - when the rebuild of that first disk was happening, the error count on that drive shot through the roof. I noticed a bit later on that the drive was actually showing up in both the array AND unassigned devices at the same time. I didn't do anything at that time other than let the rebuild finish. I then unseated it when I replaced it in the array. Also xfs_repair appars to have done the trick! I'll be going through and seeing if I can find any corrupted files, but it had me run the repair twice and now the folder is back, so thank you for that! Now to investigate the "failed" drive...
  9. So there are movies in the media share on a bunch of other disks that are completely fine, but if i navigate to \\unraid\media\movies, that folder in the share appears empty, but browsing the individual disks, the files are there. the other folders under the media share appear to be unaffected - just the Movies folder appears affected. I'll certainly look @ ddrescue though, much appreciated!
  10. So yesterday, I was ready to swap in a spare drive to replace one that was starting to throw SMART errors. I'd already moved all files off of it, so there was no real risk of data loss - or so I thought. After I replaced it, during the 10 hour rebuild, another drive started throwing hundreds of thousands of errors during the rebuild. This drive contained a few dozen movies in my media share. Not really knowing what else to do, I let the rebuild complete, which it did overnight. I then replaced the newly failed drive as well and then let that rebuild complete. Now, it would appear that my Movies folder under my media share has become corrupt somehow. The files still exist spread throughout my drives - including the newly replaced drive, though I'd be shocked if there wasn't significant corruption in those files, which are quite easily replaceable. My logs are now full of "Unmount and run xfs_repair" and "Metadata corruption detected at xfs_buf....." messages which eventually completely fill the log file until it stops filling up anymore. Seems like at this point, I don't have many options other than to just let it sit there and do its thing. Anything else I can do? Potentially create a new share and use Krusader or Unbalance to move the missing files to the new share? I appreciate any insights! diagnostics-20210704-2126.zip
  11. I'm not familiar with the boxes you're talking about. Are we talking something like a pi running one of those distros? or is this a different device? I wasn't aware that the cpu on the pi could handle something like that.
  12. I mean, I'd call myself an unraid novice, sure, but I'm certainly not a novice to this sort of hardware - just not used to applying it for personal use. I've been in this space professionally for something like 15 years now. I did end up up going away from a smaller case and skipped ahead a couple levels and picked up a supermicro 846 4u chassis (24 hot swap bays) with a full sized atx motherboard (w480 creator) with the w-1290p. RAM is ECC - I figured this may be a "an ounce of prevention is worth a pound of cure" sort of situation. I was originally looking for a Rosewill 4u chassis, but those are hard to come by, so I did the next logical thing and just got a supermicro chassis with the sas/sata backplane already in there. It would have cost more to outfit the rosewill chassis with a few hot swap cages than it cost for the supermicro chassis. And plex 4k transcoding unfortunately requires quite the beefy CPU, so here we are. Would it have been more prudent to start with a simpler, less beefy setup? Probably, but I wouldn't have been able to test my primary use case.