Bigsam411

So I just had this issue. Server was up for days (I rebooted earlier this week) and was using my Windows VM. I stopped the VM and was going to go to bed but decided after a bit to get back on the computer for something. I went to turn on the VM using my phone and on the monitor I saw the Tiano Core screen but it was frozen. I tried to restart the VM and that didnt work so I selected stop then Force Stop. After a few seconds the server rebooted. When it got to the Unraid boot screen it wouldnt get passed BZroot before rebooting again. This happened several times (even when trying safe mode) before eventually booting up properly. Once booted the VM manager was turned off and of course a Parity check had started (as expected). Now I am in the VM. I am not sure if the diagnostic will show anything before the crash but here it is. Other things going on before the crash were a Home assistant VM, Several Docker containers (One downloading stuff), and at one point a remote Plex stream. Any idea what may have happened? A quick Google search led me to it maybe being the USB which would be a bummer since its new and I dont really want to swap it (its inside the case plugged into a dongle plugged into a USB header). Thanks sauron-diagnostics-20210917-2334.zip

I already tried the cables and the power connector is just one ( or maybe it was two) that goes to 5 of the drives. I think the design of the hot swap bay is the problem on my case. Or it's just something loose inside the hot swap bays. I think new case might solve that.

So I every time I run parity checks (Either the monthly one or manual ones) I get tons of disk errors on some of the disks. In my research I came to the conclusion that it could be the SATA cables that are the problem. Trying different SATA cables however did not seem to help with the problem. I came to the possible conclusion that it could be the Case I am using or possibly the SATA ports on my Board. Here are my current relevant specs: 1. AMD Ryzen 9 5950X 2. ASRock X570 Creator 3. 6x 16TB Seagate EXOS 4. Silverstone SST-CS350B case with 5 hotswap bays (I added a hotswap bay to the 5.25" slot on the front) Since the case is hot swap and the drives connect to an enclosure that then connects to the drives via SATA cables I think the case could be the problem. I am also concerned that plugging so many SATA devices to the board directly could be the problem. I was about to swap all of the components into another case I have laying around in order to confirm my theory of the case being the problem but I very quickly remembered the case only supports M-ATX boards and not full size ATX. So instead I just placed an order for this Rosewill Case and an LSI 9211-8i. I figured the new Case would give me extra Hot swap bays in case I need more storage and maybe it will solve my issue. Am I right to think the case is the problem or would the LSI likely solve the problem without the case. Or do you think it could be something else all together? Thanks sauron-diagnostics-20210801-1135.zip

So I think I just confirmed that the issue is either with the sata cable or the sata port. I hot swapped the two troublesome drives with two other ones on my hot swappable case and now a different drive is spitting out errors. Weirdly only one drive is having problems post swap as opposed to two. I wonder if I can try seating the bad one better in the drive bay to see if that solves it. If anyone else has any solutions though I would appreciate that as well. Thanks sauron-diagnostics-20210624-2118.zip

Seems like it rebooted again an hour ago. I uploaded a diagnostic this time. When I have time later I can look at the page about reboots and try some other things. Thanks sauron-diagnostics-20210624-0921.zip

Lately I have been noticing random reboots and lots of parity checks. Things were going well for a while though so I did not think much of it until today when I had a reboot while stopping the array. I clicked on the disk log information and two of the disks were spitting a bunch of warnings and errors. After a Google search I determined it could be a bad SATA cable so I swapped that out. Still having the issue. Below is some of the Disk log as well as a full attached log for reference. Any help would be appreciated. Thanks Jun 23 22:30:40 Sauron kernel: ata11: hard resetting link Jun 23 22:30:50 Sauron kernel: ata11: softreset failed (1st FIS failed) Jun 23 22:30:50 Sauron kernel: ata11: hard resetting link Jun 23 22:30:59 Sauron kernel: ata11: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 23 22:30:59 Sauron kernel: ata11.00: configured for UDMA/33 Jun 23 22:30:59 Sauron kernel: ata11: EH complete Jun 23 22:31:00 Sauron kernel: ata11.00: exception Emask 0x10 SAct 0xff00 SErr 0x90200 action 0xe frozen Jun 23 22:31:00 Sauron kernel: ata11.00: irq_stat 0x00400000, PHY RDY changed Jun 23 22:31:00 Sauron kernel: ata11: SError: { Persist PHYRdyChg 10B8B } Jun 23 22:31:00 Sauron kernel: ata11.00: failed command: READ FPDMA QUEUED Jun 23 22:31:00 Sauron kernel: ata11.00: cmd 60/40:40:98:e4:60/05:00:00:00:00/40 tag 8 ncq dma 688128 in Jun 23 22:31:00 Sauron kernel: ata11.00: status: { DRDY } Jun 23 22:31:00 Sauron kernel: ata11.00: failed command: READ FPDMA QUEUED Jun 23 22:31:00 Sauron kernel: ata11.00: cmd 60/40:48:d8:e9:60/00:00:00:00:00/40 tag 9 ncq dma 32768 in Jun 23 22:31:00 Sauron kernel: ata11.00: status: { DRDY } Jun 23 22:31:00 Sauron kernel: ata11.00: failed command: READ FPDMA QUEUED Jun 23 22:31:00 Sauron kernel: ata11.00: cmd 60/10:50:18:ea:60/05:00:00:00:00/40 tag 10 ncq dma 663552 in Jun 23 22:31:00 Sauron kernel: ata11.00: status: { DRDY } Jun 23 22:31:00 Sauron kernel: ata11.00: failed command: READ FPDMA QUEUED Jun 23 22:31:00 Sauron kernel: ata11.00: cmd 60/40:58:28:ef:60/05:00:00:00:00/40 tag 11 ncq dma 688128 in Jun 23 22:31:00 Sauron kernel: ata11.00: status: { DRDY } Jun 23 22:31:00 Sauron kernel: ata11.00: failed command: READ FPDMA QUEUED Jun 23 22:31:00 Sauron kernel: ata11.00: cmd 60/70:60:68:f4:60/00:00:00:00:00/40 tag 12 ncq dma 57344 in Jun 23 22:31:00 Sauron kernel: ata11.00: status: { DRDY } Jun 23 22:31:00 Sauron kernel: ata11.00: failed command: READ FPDMA QUEUED Jun 23 22:31:00 Sauron kernel: ata11.00: cmd 60/40:68:d8:f4:60/05:00:00:00:00/40 tag 13 ncq dma 688128 in Jun 23 22:31:00 Sauron kernel: ata11.00: status: { DRDY } Jun 23 22:31:00 Sauron kernel: ata11.00: failed command: READ FPDMA QUEUED Jun 23 22:31:00 Sauron kernel: ata11.00: cmd 60/40:70:18:fa:60/05:00:00:00:00/40 tag 14 ncq dma 688128 in Jun 23 22:31:00 Sauron kernel: ata11.00: status: { DRDY } Jun 23 22:31:00 Sauron kernel: ata11.00: failed command: READ FPDMA QUEUED Jun 23 22:31:00 Sauron kernel: ata11.00: cmd 60/40:78:58:ff:60/05:00:00:00:00/40 tag 15 ncq dma 688128 in Jun 23 22:31:00 Sauron kernel: ata11.00: status: { DRDY } Jun 23 22:31:00 Sauron kernel: ata11: hard resetting link sauron-syslog-20210624-0226.zip

Okay I will leave this up and not delete the post but after I was able to log in to the Terminal directly on the device I was browsing on my laptop for some help and then decided to connect to the Webui and it suddenly worked. I am now able to use everything again. No idea what happened. But I am no longer having this issue.

Okay so I forgot that the keyboard I was using was connected to a USB controller that I am passing through to the VM. I am able to log into the terminal using a keyboard connected to a different USB port but not the Web UI. Any Ideas would be helpful. Thanks.

Everything was working fine just earlier. I had a Windows VM booted and I was using it no problem. I left my computer for a bit and then came back and turned the monitor on and then got nothing. I tried to go into the Web ui on my phone and couldnt get in either. I even tried to ssh in from phone and that didnt work so I hard rebooted the machine and it booted into Unraid but then I was unable to even log in. No keyboard input was working even though it was working in the Bios. I then tried to boot into Gui mode and only got a blinking cursor for a while. The only thing that works when I boot into Unraid is a ping to the network IP. Nothing else is working. Any ideas on what I can do to troubleshoot? Thanks Edit. I also tried plugging the USB into my laptop to see if the drive had gone bad and it seemed fine. I was able to browse all of the directories in it. There was a log file there but that was created on Friday and everything was working then and yesterday.

Anyone have any experience with Passing through Thunderbolt 3? I am on 6.9.0 RC2 with an ASRock X570 Creator board. The actual computer is on the other side of a wall from where my desk is so I was hoping to be able to hook up a Thunderbolt dock mainly for more USB ports and an SD Card reader for my camera. I bought a CalDigit USB-C Pro Dock which supports ThunderBolt 3 and USB-C (Though at much slower speed). When I am in System Devices I see the following IOMMU groups related to Thunderbolt but only the bottom two are enabled for Passthrough. When I edit my Windows 10 VM I only get the option for the USB controller but then nothing actually passes through and I cannot use the dock. Any Ideas? IOMMU group 21:[8086:15ea] 03:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) IOMMU group 22:[8086:15ea] 04:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) IOMMU group 23:[8086:15ea] 04:01.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) IOMMU group 24:[8086:15ea] 04:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) IOMMU group 25:[8086:15ea] 04:04.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) IOMMU group 26:[8086:15eb] 05:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018] (rev 06) IOMMU group 27:[8086:15ec] 07:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] (rev 06) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Edit: I noticed in Device Manager that there is an "Unknown USB Device (Device Descriptor Request Failed). I also didnt mention that I did in fact install the Thunderbolt SW I got off of ASRocks page for the board.

Awesome thanks.

Oh so this is normal? I mean I wasnt too worried about 7 gigs out of a terabyte but was just curious. Thanks I guess.

Drive is Samsung 1tb QVO SSD. I just shut off all docker containers and ran the mover. It shows I have 7GB used out of the 1tb. When I go to browse the contents I see nothing. Any ideas on how to get that space back? Thanks sauron-diagnostics-20210217-1050.zip