Jump to content

Benson

Members
  • Content Count

    1261
  • Joined

  • Last visited

  • Days Won

    2

Benson last won the day on July 8 2019

Benson had the most liked content!

Community Reputation

96 Good

About Benson

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

1498 profile views
  1. Agree, due to AMD-Vi (IOMMU) error also point to NVMe Jan 12 06:45:34 Anton kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 Some feedback but not relate to the crash - memory speed setting ( suppose be auto ) quite slow, only 1600MT/s, you have found 8G 3200MT/s single RANK RAM module. Expect could run at 2400MT/s or 2666MT/s. - undervolt this chip. It may reduce heat during high load, but in fact, it will generate more heat in low load because the voltage were fixed.
  2. Note. Futher check those log again, in fact, the HDDs were detect in 6.8 but with error. Why it need "lower device linkrate" but no need in 6.7 ????? Jan 16 22:35:09 Tower2 kernel: ex 5001438007be0905 phy05 SATA device linkrate > min pathway connection rate, attempting to lower device linkrate Jan 16 22:35:09 Tower2 kernel: ex 5001438007be0905 phy05 SATA device set linkrate successfully Jan 3 09:38:13 Tower2 kernel: ex 5001438007be0900 phy00 SATA device linkrate > min pathway connection rate, attempting to lower device linkrate Jan 3 09:38:13 Tower2 kernel: ex 5001438007be0900 phy00 SATA device set linkrate successfully Jan 3 09:38:13 Tower2 kernel: ex 5001438007be0901 phy01 SATA device linkrate > min pathway connection rate, attempting to lower device linkrate Jan 3 09:38:13 Tower2 kernel: ex 5001438007be0901 phy01 SATA device set linkrate successfully Jan 3 09:38:13 Tower2 kernel: ex 5001438007be0902 phy02 SATA device linkrate > min pathway connection rate, attempting to lower device linkrate Jan 3 09:38:13 Tower2 kernel: ex 5001438007be0902 phy02 SATA device set linkrate successfully Jan 3 09:38:13 Tower2 kernel: ex 5001438007be0903 phy03 SATA device linkrate > min pathway connection rate, attempting to lower device linkrate Jan 3 09:38:13 Tower2 kernel: ex 5001438007be0903 phy03 SATA device set linkrate successfully Jan 3 09:38:13 Tower2 kernel: ex 5001438007be0904 phy04 SATA device linkrate > min pathway connection rate, attempting to lower device linkrate Jan 3 09:38:13 Tower2 kernel: ex 5001438007be0904 phy04 SATA device set linkrate successfully Jan 3 09:38:13 Tower2 kernel: ex 5001438007be0905 phy05 SATA device linkrate > min pathway connection rate, attempting to lower device linkrate Jan 3 09:38:13 Tower2 kernel: ex 5001438007be0905 phy05 SATA device set linkrate successfully Jan 3 09:38:13 Tower2 kernel: ex 5001438007be0906 phy06 SATA device linkrate > min pathway connection rate, attempting to lower device linkrate Jan 3 09:38:13 Tower2 kernel: ex 5001438007be0906 phy06 SATA device set linkrate successfully Jan 3 09:38:13 Tower2 kernel: ex 5001438007be0907 phy07 SATA device linkrate > min pathway connection rate, attempting to lower device linkrate Jan 3 09:38:13 Tower2 kernel: ex 5001438007be0907 phy07 SATA device set linkrate successfully Jan 3 09:38:13 Tower2 kernel: ex 5001438007be0908 phy08 SATA device linkrate > min pathway connection rate, attempting to lower device linkrate Jan 3 09:38:13 Tower2 kernel: ex 5001438007be0908 phy08 SATA device set linkrate successfully Jan 3 09:38:13 Tower2 kernel: ex 5001438007be0909 phy09 SATA device linkrate > min pathway connection rate, attempting to lower device linkrate Jan 3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87 Jan 3 09:38:13 Tower2 kernel: ata7.00: failed to IDENTIFY (I/O error, err_mask=0x11) Jan 3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87 Jan 3 09:38:13 Tower2 kernel: ata10.00: failed to IDENTIFY (I/O error, err_mask=0x11) Jan 3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87 Jan 3 09:38:13 Tower2 kernel: ata21.00: failed to IDENTIFY (I/O error, err_mask=0x11) Jan 3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87 Jan 3 09:38:13 Tower2 kernel: ata11.00: failed to IDENTIFY (I/O error, err_mask=0x11) Jan 3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87 Jan 3 09:38:13 Tower2 kernel: ata12.00: failed to IDENTIFY (I/O error, err_mask=0x11) Jan 3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87 Jan 3 09:38:13 Tower2 kernel: ata15.00: failed to IDENTIFY (I/O error, err_mask=0x11) Jan 3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87 Jan 3 09:38:13 Tower2 kernel: ata13.00: failed to IDENTIFY (I/O error, err_mask=0x11) Jan 3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87 Jan 3 09:38:13 Tower2 kernel: ata9.00: failed to IDENTIFY (I/O error, err_mask=0x11) Jan 3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87 Jan 3 09:38:13 Tower2 kernel: ata14.00: failed to IDENTIFY (I/O error, err_mask=0x11) Jan 3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87 Jan 3 09:38:13 Tower2 kernel: ata8.00: failed to IDENTIFY (I/O error, err_mask=0x11) Jan 3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87 Jan 3 09:38:13 Tower2 kernel: ata23.00: failed to IDENTIFY (I/O error, err_mask=0x11) Jan 3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87 Jan 3 09:38:13 Tower2 kernel: ata18.00: failed to IDENTIFY (I/O error, err_mask=0x11)
  3. Disk controller problem Jan 14 19:13:32 Nasgard kernel: ahci 0000:08:00.0: AHCI controller unavailable! Jan 14 19:14:05 Nasgard kernel: ahci 0000:09:00.0: AHCI controller unavailable! Jan 14 19:14:17 Nasgard kernel: ahci 0000:07:00.0: AHCI controller unavailable! Jan 14 19:14:18 Nasgard kernel: ahci 0000:0a:00.0: AHCI controller unavailable!
  4. Most mainboard can monitoring different source i.e. CPU, MB, Power module. Some BIOS also can mix different source and take multi in account. The problem may be you plug to a CPU FAN socket, so it will limited to monitor CPU only. This usually could be tune in BIOS, you can adjust slope/ramp parameter manually. Most are DIY build with hall effect current sensor to detect the current draw or pure hall effect sensor to detect HDDs motor rotate or not with suitable circuit. But you could use some market build Temp. FAN controller which have temp. sensor, i.e. 4 channel, then monitor 4 groups HDDs and stop the fan if under certain temp. But this may have problem, the temp. will raise if FAN stop or affect by surrounding too.
  5. The 45Drives enclosure really a good case, but I doubt a single power supply can fullfill the 5v power requirement for 30 HDD and System? Does cables ( data/power ) have several connect point instead a single end to end. An easy way to check this was use a multimeter ( with Min / Max recording ) to check the 5v at the most far end-point, just load all HDDs and check the min reading. Could you provide the spec. of the power supply ? If problem on disk itself ( may be ), why it can success preclear without problem > 50s hrs, so I prefer believe problem not on disk.
  6. Why in same FAN socket, mothboard have different FAN socket and have individuals control. Besides, CPU FAN was PWM, if you connect another non-PWM FAN with it, then those FAN will run in their max speed. Plugin should be the only easy choice, but I don't apply this and I doubt if HDD sleep and no temperature reading what would plugin will do. If you really like to turn off some FAN during HDD sleep, then you can make some hardware controller to detect the 12v power draw from HDD, if less then some drawing then off the FAN.
  7. If most 1G network device without problem with Meraki MS120-8LP switch then it is problem on the new NIC. But you can take more troubleshooting. Any different if ? ( no more link down ) - Only connect 1 port instead 2 port - Not apply LACP
  8. Always. You can see the main problem was the clearance between contact pin was less then 1mm. So the inslulator will be thin, fault easy happen. Arc won't be main problem, 1) if you don't hot plug, then almost no arc, and those are low voltage, 2) Molex design have more clearance between contact pin, so may be less problem. 3) Molex to multi SATA ( or anything ) fire, it is another kind of fault, due to too much device loading, the large electrical current exceed the contact pin loading, as result melting and cause problem. This just the same thing, or even worse. ( remember on the clearance, but SATA usually have better contact performance then Molex ) I never agree Molex or SATA which will more safe then which other, in fact both have their problem. I will conclude all people ( include me ) also have risk on their connector because there are no effective fault protection to avoid problem happen. What can "effective" against this ? Fuse, each power point have their fuse. This exactly like your home power distribution network. ( But this not practice ) Anyway, some rule you should take on SATA / Molex connector - Better material and build quality - Never overload it - Don't make any unnecessary mechanical force on it, i.e. cable in tension / other cables touch them due to housekeeping etc.
  9. Noise vs Cooling always headcahe because no space between HDD.
  10. From new Syslog, the second SAS2308 card also run at PCIe Gen 1 speed. In fact all device were in Gen 1, but machine support PCIe Gen 3. Does you wrongly set the limit in BIOS ? It like expander to provide a function to let you connect more device but share same bandwidth, just expander service for SAS device. How about the result on 2nd 2308 HBA ??
  11. I don't think so, but you can troubleshoot in this direction. As mention before, HBA should have PCIe switch and your mainboard also have PCIe switch, those were in cascade and may have compatible problem. From Syslog, this have a sign, LSI HBA only running in PCIe Gen 1 speed, but bandwidth still have 16Gb/s. ( Even all problem solve, throughput will ceiling at this too ) Dec 30 20:01:55 UnRAID-Backup kernel: pci 0000:08:00.0: 16.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s x8 link at 0000:00:01.0 (capable of 63.008 Gb/s with 8 GT/s x8 link) I also notice you have P420i HBA, 1 or 2 disk connect, could you unplug it and try. Which Expander you got ??
  12. Message come from offical ( only apply for SAS3 ) ?? I can't remember does I try this under UEFI. Agree.
  13. I know, I haven't speed bottleneck for 2008 and 2308 chip to connect 12 and 16 disks which have same result as above. 9206-16e have two 2308 chips, I suppose it should have a PCIe switch on HBA in order to connect two chips, there may be some compatibility issue with mother board. Or could you check relate overheat on HBA ?? But I am not sure HBA would or wont throttle because I never see that.
  14. I am not family with disk speed docker, but seems abnormal of simultaneous bandwidth only 347MB/s.
  15. Good you found that, if you got one pls try that and report back.