Unraid gui issues

[aleda]

here is lastest log i was upgrading the chassis for my server after rebooting cpu pinned to 100% restarted again now no gui, i can still access the shares via ip which is another issue used to be able to browse by \\tower but that stopped working and all my of data is very slow accessing. also tried formatting usb and same thing. when i do powerdown command from cli it takes 10minutes to shut down

tower-diagnostics-20200521-1324.zip

[trurl]

You're having problems connecting on multiple disks. Check all connections, both ends, power and SATA, including any power splitters. Reseat controller card if that applies.

[aleda]

I got it back up in the gui, it sems semi stable i see the cpu usage peg 100% on several cores randomly then it goes away. causes my vm and docker to reboot.

[trurl]

Did you check connections as I suggested?

[aleda]

Yes they were all seated fine as far as i can tell 

[aleda]

here is a newer diag log if that helps

tower-diagnostics-20200521-1808.zip

[aleda]

Currently running DiskSpeed on them to see if any issues happen

[JorgeB]

Onboard controller is set to IDE, change it to AHCI for best performance and reliability.

[ljm42]

@johnnie.black how can you tell IDE vs AHCI? Is this something that FCP should warn about?

[JorgeB]

15 hours ago, ljm42 said:

how can you tell IDE vs AHCI?

There are several ways, depends on what diag file I open first, e.g., you can see it in lsscsi.txt

 

Quote

[1:0:0:0]    disk    ATA      ST4000NM0033-9ZM GA0A  /dev/sdb   /dev/sg1
  state=running queue_depth=1 scsi_level=6 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/1:0:0:0  [/sys/devices/pci0000:00/0000:00:1f.2/ata1/host1/target1:0:0/1:0:0:0]
[1:0:1:0]    disk    ATA      WD4000FYYX       D1K4  /dev/sdc   /dev/sg2
  state=running queue_depth=1 scsi_level=6 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/1:0:1:0  [/sys/devices/pci0000:00/0000:00:1f.2/ata1/host1/target1:0:1/1:0:1:0]
[2:0:0:0]    disk    ATA      SanDisk SD6SB1M2 600   /dev/sdd   /dev/sg3
  state=running queue_depth=1 scsi_level=6 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/2:0:0:0  [/sys/devices/pci0000:00/0000:00:1f.2/ata2/host2/target2:0:0/2:0:0:0]
[2:0:1:0]    disk    ATA      ST4000DM005-2DP1 0001  /dev/sde   /dev/sg4
  state=running queue_depth=1 scsi_level=6 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/2:0:1:0  [/sys/devices/pci0000:00/0000:00:1f.2/ata2/host2/target2:0:1/2:0:1:0]
[3:0:0:0]    disk    ATA      ST4000DM005-2DP1 0001  /dev/sdf   /dev/sg5
  state=running queue_depth=1 scsi_level=6 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/3:0:0:0  [/sys/devices/pci0000:00/0000:00:1f.5/ata3/host3/target3:0:0/3:0:0:0]
[4:0:0:0]    disk    ATA      ST4000NM0033-9ZM GA0A  /dev/sdg   /dev/sg6
  state=running queue_depth=1 scsi_level=6 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/4:0:0:0  [/sys/devices/pci0000:00/0000:00:1f.5/ata4/host4/target4:0:0/4:0:0:0]

Note more than one device with same ATA#, that only happens in IDE mode (and with some SATA port multipliers), also Intel controller in AHCI is just one device, usually 1f:2, in in IDE mode there are two devices, 1f:2 and 1f:5

 

You can also see it in lspci.txt

Quote

00:1f.2 IDE interface [0101]: Intel Corporation 8 Series/C220 Series Chipset Family 4-port SATA Controller 1 [IDE mode] [8086:8c00] (rev 05)
    Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset Family 4-port SATA Controller 1 [IDE mode] [1458:b005]
    Kernel driver in use: ata_piix
    Kernel modules: ata_piix
...
00:1f.5 IDE interface [0101]: Intel Corporation 8 Series/C220 Series Chipset Family 2-port SATA Controller 2 [IDE mode] [8086:8c08] (rev 05)
    Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset Family 2-port SATA Controller 2 [IDE mode] [1458:b002]
    Kernel driver in use: ata_piix
    Kernel modules: ata_piix

Here you just need to look ate the driver in use, ata_piix for IDE, ACHI for AHCI, there's also de "IDE mode" on the controller name but this might not always be a reliable way to tell, especially on non Intel controllers, same on the syslog, you see the IDE driver being loaded:

May 21 14:54:28 Tower kernel: ata_piix 0000:00:1f.2: version 2.13
May 21 14:54:28 Tower kernel: ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
May 21 14:54:28 Tower kernel: scsi host1: ata_piix
May 21 14:54:28 Tower kernel: scsi host2: ata_piix

and the dual ATA# ATA1.00 + ATA1.01 and ATA2.00 + ATA2.01

May 21 14:54:28 Tower kernel: ata2.00: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 21 14:54:28 Tower kernel: ata2.01: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 21 14:54:28 Tower kernel: ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
May 21 14:54:28 Tower kernel: ata1.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
May 21 14:54:28 Tower kernel: ata2.00: ATA-8: SanDisk SD6SB1M256G1022I, 134439400836, X230600, max UDMA/133
May 21 14:54:28 Tower kernel: ata2.00: 500118192 sectors, multi 1: LBA48 NCQ (depth 0/32)
May 21 14:54:28 Tower kernel: ata1.00: ATA-9: ST4000NM0033-9ZM170,             Z1Z3ESJS,     GA0A, max UDMA/133
May 21 14:54:28 Tower kernel: ata1.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 0/32)
May 21 14:54:28 Tower kernel: ata2.01: ATA-10: ST4000DM005-2DP166,             ZDH3HBM4, 0001, max UDMA/133
May 21 14:54:28 Tower kernel: ata2.01: 7814037168 sectors, multi 16: LBA48 NCQ (depth 0/32)
May 21 14:54:28 Tower kernel: ata1.01: ATA-8: WD4000FYYX,         WCC13LZR5569, 00.0D1K4, max UDMA/133
May 21 14:54:28 Tower kernel: ata1.01: 7814037168 sectors, multi 16: LBA48 NCQ (depth 0/32)
May 21 14:54:28 Tower kernel: ata1.00: configured for UDMA/133
May 21 14:54:28 Tower kernel: ata2.00: configured for UDMA/133
May 21 14:54:28 Tower kernel: ata2.01: configured for UDMA/133
May 21 14:54:28 Tower kernel: ata1.01: configured for UDMA/133

 

 

15 hours ago, ljm42 said:

Is this something that FCP should warn about?

It would be, best bet would be to warn if the ata_piix driver is loaded, though it might give some false positives since some boards/controllers might have an IDE mode for some add-on controller and not be in use, some older JMB controllers come to mind.

 

[JorgeB]

9 minutes ago, johnnie.black said:

best bet would be to warn if the ata_piix driver is loaded

Also pata_atiixp since it's used for some AMD controllers.

[ljm42]

Thanks @johnnie.black so if this command returns anything then a controller is in IDE mode and should be changed to AHCI mode if possible:

lspci -v | grep "ata_piix"

Is there a wiki page or somthing that FCP could direct users to? 

 

Tagging @Squid to see if he wants to add this check to FCP

[JorgeB]

10 hours ago, ljm42 said:

lspci -v | grep "ata_piix"

If doing it then also look for the AMD IDE driver "pata_atiixp", since that one can be even more problematic, sometimes disks can't even be used in the array when it's in use.