MathieuBC Posted January 7, 2020 Share Posted January 7, 2020 Currently in the process of making my first unraid server. Motherboard is ASRock AM1H-ITX and using SATA card https://www.amazon.ca/-/fr/gp/product/B07T66ZXMT/ref=ppx_yo_dt_b_asin_title_o04_s01?ie=UTF8&th=1 My SATA is using ASM1061 chipset which should be supported by unraid. The disk connected to the motherboard are all detected fine, the disks connected to the SATA card are not detected by UNRAID. They are detected during boot but can see errors in UNRAID log which I am unable to "translate". Anybody can take a look at my log ? Thank you ! https://mega.nz/?fbclid=IwAR1-YrqA3WGihdAvV_ImBVhMd6E8bO76MZoQoqyWpUB-cBzGz9ybWe9AZPU#!1x9hmKhC!T_skrk_326qtfH-nNhnwRs0esJEHHV6eYXRDv8hZzoM tower-syslog-20200107-0214.zip Quote Link to comment
trurl Posted January 7, 2020 Share Posted January 7, 2020 Go to Tools - Diagnostics and attach the complete Diagnostics zip file to your NEXT post. Diagnostics includes syslog and many other useful things. Diagnostics are always preferred instead of only syslog. Quote Link to comment
MathieuBC Posted January 7, 2020 Author Share Posted January 7, 2020 Here is complete diagnostic. Thank you yoda-diagnostics-20200106-2207.zip Quote Link to comment
JorgeB Posted January 7, 2020 Share Posted January 7, 2020 4 hours ago, MathieuBC said: My SATA is using ASM1061 chipset which should be supported by unraid. Asmedia is fine, SATA port multipliers are not (or not usually), and that's what's causing your problems: Jan 6 19:04:44 Yoda kernel: ata3.00: failed to read SCR 1 (Emask=0x40) Jan 6 19:04:44 Yoda kernel: ata3.01: failed to read SCR 1 (Emask=0x40) Jan 6 19:04:44 Yoda kernel: ata3.02: failed to read SCR 1 (Emask=0x40) Jan 6 19:04:44 Yoda kernel: ata3.01: exception Emask 0x100 SAct 0xd000000 SErr 0x0 action 0x6 frozen Jan 6 19:04:44 Yoda kernel: ata3.01: failed command: READ FPDMA QUEUED Jan 6 19:04:44 Yoda kernel: ata3.01: cmd 60/30:c0:48:00:00/00:00:00:00:00/40 tag 24 ncq dma 24576 in Jan 6 19:04:44 Yoda kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 6 19:04:44 Yoda kernel: ata3.01: status: { DRDY } Jan 6 19:04:44 Yoda kernel: ata3.01: failed command: READ FPDMA QUEUED Jan 6 19:04:44 Yoda kernel: ata3.01: cmd 60/78:d0:88:00:00/00:00:00:00:00/40 tag 26 ncq dma 61440 in Jan 6 19:04:44 Yoda kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 6 19:04:44 Yoda kernel: ata3.01: status: { DRDY } Jan 6 19:04:44 Yoda kernel: ata3.01: failed command: READ FPDMA QUEUED Jan 6 19:04:44 Yoda kernel: ata3.01: cmd 60/f8:d8:08:01:00/00:00:00:00:00/40 tag 27 ncq dma 126976 in Jan 6 19:04:44 Yoda kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 6 19:04:44 Yoda kernel: ata3.01: status: { DRDY } Jan 6 19:04:44 Yoda kernel: ata3.15: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 6 19:04:44 Yoda kernel: ata3.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Jan 6 19:04:44 Yoda kernel: ata3.01: hard resetting link Jan 6 19:04:44 Yoda kernel: ata3.01: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Jan 6 19:04:44 Yoda kernel: ata3.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Jan 6 19:04:44 Yoda kernel: ata3.00: configured for UDMA/133 Jan 6 19:04:44 Yoda kernel: ata3.01: configured for UDMA/133 Jan 6 19:04:44 Yoda kernel: ata3.02: configured for UDMA/133 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.