Borys

Hi all. I've read few posts here, searched the Internat and watched Spaceinvader One's video. I don't know what could I do else. I start the VM and my external monitor connected to the GPU with HDMI is showing no input. Please help tower-diagnostics-20240130-2348.zip

Sorry for the stupid question. I am fighting with the black screen. How do you "roll back the driver to the windows basic display driver"?

I'm tagging along for the iommu question 😊 As for the ports. This ASRock X670E PG Lightning has 4xSATA but also 4xM.2.

I would like to know the iommu groups as well. I'm looking at ASRock X670E PG Lightning. Thanks

Yeah 😔 Thank you

Hi all, I've ben having issues with my Unraid setup for years. Constant errors pushing my disks into emulation. I was fed up with it and decided to start from a scratch. I've created a new config precleared 3 16TB drives: 2 for parity and 1 (for now) as data drive. The data drive precleared without any issues but the moment the array starter the first parity-sync I got errors! I've started the SMART extended self-test and it "Completed: read failure" (attached report). The only problem is that this drive has 26 hours on it and 16TB written (=preclear) ... I literally took drive I've never used (cold swap), precleared it and put into the array. This is some post-warehouse drive. Could the SMART be cleared? Is it possible the drive was mishandled in transit? Or am I simply unlucky? Thank you ST16000NM001G-2KK103_ZL2BD0A0-20240102-2203.txt

My minimal free space threshold is sufficient and is double of what I would drop into a share in a single time. However, high-water policy on the first child (folder) of the share so it increases over time. This is something I proactively deal with by manually moving children off that drive before I hit that min free space threshold. I was hoping for some automatic way of dealing with it 🤔

I have my shares set to High-Water method for allocation and it works fine. What happens when a file added to a folder already on a drive pushes that folder's size over the minimum free space threshold? Will that folder be automatically moved off the drive? If not is there a way to make that happen?

OK, will do next time. (Simplifying the journey and removing all the swearing). I changed a cable and the disk died (it was a funny looking old cable). I changed the cable again but the disk was dead. I changed a disk and everything works fine. The dead disk was successfully recovered afterwards, I think. I will test it properly (preclear) later. Also, the original cable was part of 4-split HBA cable and that particular one was flaky first few times I attached it. A disk connected with it was not working. Lesson learned, if something works funny even for a short period of time just don't trust it.

Hi all, My regular data-parity check found 2044 errors (how do I fond what kinds) and marked the disk as disabled and content emulated. I have removed the disk from the array and run the preclear process without any issues with spot on speed. However, after adding the disk back to the array and starting the data-rebuild process the disk has issues. At the beginning everything was fine but then the disk started making low, short and vibrating noise in regular intervals and the speed dropped to 0. Any ideas? The logs show something like this: Feb 5 22:29:35 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED Feb 5 22:29:35 Tower kernel: ata4.00: cmd 60/00:58:e8:49:cd/04:00:5c:00:00/40 tag 11 ncq dma 524288 in Feb 5 22:29:35 Tower kernel: res 40/00:48:a8:44:cd/00:00:5c:00:00/40 Emask 0x50 (ATA bus error) Feb 5 22:29:35 Tower kernel: ata4.00: status: { DRDY } Feb 5 22:29:35 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED Feb 5 22:29:35 Tower kernel: ata4.00: cmd 60/40:60:e8:4d:cd/01:00:5c:00:00/40 tag 12 ncq dma 163840 in Feb 5 22:29:35 Tower kernel: res 40/00:48:a8:44:cd/00:00:5c:00:00/40 Emask 0x50 (ATA bus error) Feb 5 22:29:35 Tower kernel: ata4.00: status: { DRDY } Feb 5 22:29:35 Tower kernel: ata4: hard resetting link Feb 5 22:29:41 Tower kernel: ata4: link is slow to respond, please be patient (ready=0) Feb 5 22:29:45 Tower kernel: ata4: COMRESET failed (errno=-16) Feb 5 22:29:45 Tower kernel: ata4: hard resetting link Feb 5 22:29:51 Tower kernel: ata4: link is slow to respond, please be patient (ready=0) Feb 5 22:29:53 Tower kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Feb 5 22:29:53 Tower kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT3._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Feb 5 22:29:53 Tower kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT3._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Feb 5 22:29:53 Tower kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT3._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Feb 5 22:29:53 Tower kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT3._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Feb 5 22:29:53 Tower kernel: ata4.00: configured for UDMA/100 Feb 5 22:29:53 Tower kernel: ata4: EH complete Feb 5 22:29:53 Tower kernel: ata4.00: exception Emask 0x50 SAct 0x7e00003f SErr 0x4890800 action 0xe frozen Feb 5 22:29:53 Tower kernel: ata4.00: irq_stat 0x0d400040, interface fatal error, connection status changed Feb 5 22:29:53 Tower kernel: ata4: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch } Feb 5 22:29:53 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED