IG-88 Posted June 17, 2020 Share #26 Posted June 17, 2020 Just now, nightbird said: how can i run "lspci -k" command? via SSH? yes, login with your admin account you use on the web gui and then elevate your rights to have root acces with "sudo -i" Quote Link to comment Share on other sites More sharing options...
nightbird Posted June 17, 2020 Share #27 Posted June 17, 2020 (edited) 25 minutes ago, IG-88 said: yes, login with your admin account you use on the web gui and then elevate your rights to have root acces with "sudo -i" So with "lspci -k" command i get this: 0000:00:00.0 Class 0600: Device 8086:2e30 (rev 03) Subsystem: Device 1458:5000 0000:00:01.0 Class 0604: Device 8086:2e31 (rev 03) Kernel driver in use: pcieport 0000:00:02.0 Class 0300: Device 8086:2e32 (rev 03) Subsystem: Device 1458:d000 0000:00:1c.0 Class 0604: Device 8086:27d0 (rev 01) Kernel driver in use: pcieport 0000:00:1d.0 Class 0c03: Device 8086:27c8 (rev 01) Subsystem: Device 1458:5004 Kernel driver in use: uhci_hcd 0000:00:1d.1 Class 0c03: Device 8086:27c9 (rev 01) Subsystem: Device 1458:5004 Kernel driver in use: uhci_hcd 0000:00:1d.2 Class 0c03: Device 8086:27ca (rev 01) Subsystem: Device 1458:5004 Kernel driver in use: uhci_hcd 0000:00:1d.3 Class 0c03: Device 8086:27cb (rev 01) Subsystem: Device 1458:5004 Kernel driver in use: uhci_hcd 0000:00:1d.7 Class 0c03: Device 8086:27cc (rev 01) Subsystem: Device 1458:5006 Kernel driver in use: ehci-pci 0000:00:1e.0 Class 0604: Device 8086:244e (rev e1) 0000:00:1f.0 Class 0601: Device 8086:27b8 (rev 01) Subsystem: Device 1458:5001 Kernel driver in use: lpc_ich 0000:00:1f.1 Class 0101: Device 8086:27df (rev 01) Subsystem: Device 1458:b001 Kernel driver in use: ata_piix 0000:00:1f.2 Class 0101: Device 8086:27c0 (rev 01) Subsystem: Device 1458:b002 Kernel driver in use: ata_piix 0000:00:1f.3 Class 0c05: Device 8086:27da (rev 01) Subsystem: Device 1458:5001 0000:01:00.0 Class 0200: Device 8086:105e (rev 06) Subsystem: Device 103c:7044 Kernel driver in use: e1000e 0000:01:00.1 Class 0200: Device 8086:105e (rev 06) Subsystem: Device 103c:7044 Kernel driver in use: e1000e 0000:02:00.0 Class 0106: Device 1b4b:9215 (rev 11) Subsystem: Device 1b4b:9215 Kernel driver in use: ahci 0001:07:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:08:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:09:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:0a:00.0 Class 0000: Device 1b4b:9235 (rev ff) What kind of info can you get from this? Tnx for your help! Edited June 17, 2020 by nightbird Quote Link to comment Share on other sites More sharing options...
IG-88 Posted June 17, 2020 Share #28 Posted June 17, 2020 (edited) 32 minutes ago, nightbird said: 0000:02:00.0 Class 0106: Device 1b4b:9215 (rev 11) Subsystem: Device 1b4b:9215 Kernel driver in use: ahci the controller is there and the ahci driver is used for it - looks like as it should be did you connect a a new disk? does it show up in the web gui in storage manager under hdd/ssd? if so and its not showing up we will need /var/log/dmesg as next (you can trigger that to list in the console by typing "dmesg" and can use the log function in putty to capture that (or use winscp to get the file directly?) side note: your onboard sata seems not to be in ahci mode but the will only be a problem if you update to dsm 6.2, if you have plans to do so look for switches in bios to change to exclusive sata/ahci mode, everything with IDE in the name is bad in this matter) Edited June 17, 2020 by IG-88 Quote Link to comment Share on other sites More sharing options...
saretar Posted August 11, 2020 Share #29 Posted August 11, 2020 (edited) Hi, I have similar problem - sata card works in bios (i can see connected disks), but completely unseen in web gui in synology. Computer: i5-4570, msi h97 gaming 3, 8gb ram, 4x4tb wd red (and pro), one sata ssd, emulex 10gbe card in main pcie slot. xpenology 1.02b, 3515xs, DSM 6.1.7-15284 Update 3. sata card with 2 ports Marvell 88SE9215, one connected disk hgst 3tb (was in shr-1 before, connected to native sata port in motherboard) Below is lspci and attached file with dmesg and this, i cannot decipher ~# lspci -k 0000:00:00.0 Class 0600: Device 8086:0c00 (rev 06) Subsystem: Device 1462:7918 0000:00:01.0 Class 0604: Device 8086:0c01 (rev 06) Kernel driver in use: pcieport 0000:00:02.0 Class 0300: Device 8086:0412 (rev 06) Subsystem: Device 1462:7918 0000:00:03.0 Class 0403: Device 8086:0c0c (rev 06) Subsystem: Device 1462:7918 0000:00:14.0 Class 0c03: Device 8086:8cb1 Subsystem: Device 1462:7918 Kernel driver in use: xhci_hcd 0000:00:16.0 Class 0780: Device 8086:8cba Subsystem: Device 1462:7918 0000:00:1a.0 Class 0c03: Device 8086:8cad Subsystem: Device 1462:7918 Kernel driver in use: ehci-pci 0000:00:1c.0 Class 0604: Device 8086:8c90 (rev d0) Kernel driver in use: pcieport 0000:00:1c.2 Class 0604: Device 8086:8c94 (rev d0) Kernel driver in use: pcieport 0000:00:1c.3 Class 0604: Device 8086:244e (rev d0) 0000:00:1c.6 Class 0604: Device 8086:8c9c (rev d0) Kernel driver in use: pcieport 0000:00:1d.0 Class 0c03: Device 8086:8ca6 Subsystem: Device 1462:7918 Kernel driver in use: ehci-pci 0000:00:1f.0 Class 0601: Device 8086:8cc6 Subsystem: Device 1462:7918 0000:00:1f.2 Class 0106: Device 8086:8c82 Subsystem: Device 1462:7918 Kernel driver in use: ahci 0000:00:1f.3 Class 0c05: Device 8086:8ca2 Subsystem: Device 1462:7918 0000:01:00.0 Class 0200: Device 19a2:0710 (rev 03) Subsystem: Device 10df:e72a Kernel driver in use: be2net 0000:01:00.1 Class 0200: Device 19a2:0710 (rev 03) Subsystem: Device 10df:e72a Kernel driver in use: be2net 0000:03:00.0 Class 0200: Device 1969:e091 (rev 13) Subsystem: Device 1462:7918 Kernel driver in use: alx 0000:04:00.0 Class 0604: Device 1b21:1080 (rev 03) 0000:06:00.0 Class 0106: Device 1b4b:9125 (rev 11) Subsystem: Device 1b4b:9125 Kernel driver in use: ahci 0001:07:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:08:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:09:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:0a:00.0 Class 0000: Device 1b4b:9235 (rev ff) dmesg.txt Edited August 11, 2020 by saretar Quote Link to comment Share on other sites More sharing options...
IG-88 Posted August 11, 2020 Share #30 Posted August 11, 2020 (edited) 10 hours ago, saretar said: 0000:06:00.0 Class 0106: Device 1b4b:9125 (rev 11) Subsystem: Device 1b4b:9125 Kernel driver in use: ahci thats your 2 port controller Quote 0001:07:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:08:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:09:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:0a:00.0 Class 0000: Device 1b4b:9235 (rev ff) just emulated dummys to make it look like original synology system the controller seem to be there and get's resources [ 1.863880] ahci 0000:06:00.0: irq 44 for MSI/MSI-X [ 1.863924] ahci 0000:06:00.0: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode [ 1.863927] ahci 0000:06:00.0: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs [ 1.863932] ahci 0000:06:00.0: port 0 can do FBS, forcing FBSCP [ 1.863950] ahci 0000:06:00.0: port 1 can do FBS, forcing FBSCP [ 1.864153] ata6: send port disabled event [ 1.866660] scsi6 : ahci [ 1.867706] scsi7 : ahci [ 1.868612] ata7: SATA max UDMA/133 abar m2048@0xefa10000 port 0xefa10100 irq 44 [ 1.868616] ata8: SATA max UDMA/133 abar m2048@0xefa10000 port 0xefa10180 irq 44 if looking further for ata7 [ 11.866360] ata7: softreset failed (1st FIS failed) [ 11.891683] dmar: DRHD: handling fault status reg 2 [ 11.891883] dmar: DMAR:[DMA Write] Request device [06:00.1] fault addr 2204e0000 DMAR:[fault reason 02] Present bit in context entry is clear [ 12.171278] dmar: DRHD: handling fault status reg 2 [ 12.171477] dmar: DMAR:[DMA Read] Request device [06:00.1] fault addr 2204e0000 DMAR:[fault reason 02] Present bit in context entry is clear [ 21.864412] ata7: softreset failed (1st FIS failed) [ 21.889772] dmar: DRHD: handling fault status reg 2 [ 21.889971] dmar: DMAR:[DMA Write] Request device [06:00.1] fault addr 2204e0000 DMAR:[fault reason 02] Present bit in context entry is clear [ 22.169330] dmar: DRHD: handling fault status reg 2 [ 22.169528] dmar: DMAR:[DMA Read] Request device [06:00.1] fault addr 2204e0000 DMAR:[fault reason 02] Present bit in context entry is clear [ 56.855097] ata7: softreset failed (1st FIS failed) [ 56.855299] ata7: limiting SATA link speed to 3.0 Gbps [ 56.880468] dmar: DRHD: handling fault status reg 2 [ 56.880667] dmar: DMAR:[DMA Write] Request device [06:00.1] fault addr 2204e0000 DMAR:[fault reason 02] Present bit in context entry is clear [ 57.160015] dmar: DRHD: handling fault status reg 2 [ 57.160214] dmar: DMAR:[DMA Read] Request device [06:00.1] fault addr 2204e0000 DMAR:[fault reason 02] Present bit in context entry is clear [ 61.854622] ata7: softreset failed (1st FIS failed) [ 61.854822] ata7: reset failed, giving up does not look good, failed and "giving up" , cause seems to be a kernel driver problem (that we cant fix) when using google to find the error "dmar: DRHD: handling fault status reg 2" ... https://bugzilla.kernel.org/show_bug.cgi?id=202723 there are suggestions about adding kernel options (in grub.cfg) related to iommu, if you want to try maybe you can try 1.04b / 918+, it has newer kernel and afaik the apollolake units from synology use a marvel controller for more ports so this build of kernel and config might be better suited also possible it might be fixed in dsm 6.2.x for 3615, but loader 1.03b cant use uefi, you would have to use csm/legacy mode, that seems to be a problem for a lot of people, so maybe try 1.04b first as it supports uefi and csm/legacy also possible are alternative controller (chips) like asm products or jmb585 (i use jmb585 myself as it supports pcie 3.0 with its two pcie lanes - but i did not test with dsm 6.1 and loader 1.02b) Edited August 11, 2020 by IG-88 Quote Link to comment Share on other sites More sharing options...
saretar Posted August 12, 2020 Share #31 Posted August 12, 2020 14 hours ago, IG-88 said: does not look good, failed and "giving up" , cause seems to be a kernel driver problem (that we cant fix) when using google to find the error "dmar: DRHD: handling fault status reg 2" ... https://bugzilla.kernel.org/show_bug.cgi?id=202723 there are suggestions about adding kernel options (in grub.cfg) related to iommu, if you want to try maybe you can try 1.04b / 918+, it has newer kernel and afaik the apollolake units from synology use a marvel controller for more ports so this build of kernel and config might be better suited also possible it might be fixed in dsm 6.2.x for 3615, but loader 1.03b cant use uefi, you would have to use csm/legacy mode, that seems to be a problem for a lot of people, so maybe try 1.04b first as it supports uefi and csm/legacy also possible are alternative controller (chips) like asm products or jmb585 (i use jmb585 myself as it supports pcie 3.0 with its two pcie lanes - but i did not test with dsm 6.1 and loader 1.02b) Hi, Thanks a lot for checking out. I'm not 100% certain to try 1.04 and 918+, as i read it has many other problems, e.g. does my emulex card will work? Is it stable enough? Right now my 3515xs with 1.02b works great, missing this cheapo sata pcie card. Maybe i will just buy LSI sas-sata. I've seen for 40$ with cables allready HP H220, they should work as i read through forum. Quote Link to comment Share on other sites More sharing options...
IG-88 Posted August 12, 2020 Share #32 Posted August 12, 2020 10 hours ago, saretar said: Maybe i will just buy LSI sas-sata. I've seen for 40$ with cables allready HP H220, they should work as i read through forum. that should work reliable too with 3615/17 and the lsi sas works also with less then its 8 pcie lanes, even with one (checked it with a pcie 1x to 16x adapter and a 9211-8i) Quote Link to comment Share on other sites More sharing options...
neoooooo Posted January 8, 2022 Share #33 Posted January 8, 2022 i have pci to 2 sata port expansion card. some chinese from wish. and it work about 30min - 1h than "volume crashed" 1.04 on 918+ dsm 6.2.3 update 3. will expansion card with marvell chip work better ? Quote Link to comment Share on other sites More sharing options...
IG-88 Posted January 9, 2022 Share #34 Posted January 9, 2022 (edited) 16 hours ago, neoooooo said: i have pci to 2 sata port expansion card. some chinese from wish. and it work about 30min - 1h than "volume crashed" 1.04 on 918+ dsm 6.2.3 update 3. would be good if you check what card/chip you have and write that along with your problem from your description it sounds more like a heat or quality issue heat problems can also arise from missing airflow in the housing or heatsink not properly mounted or missing thermal paste Quote will expansion card with marvell chip work better ? maybe every card not from wish might fix your problem? 88se92xx based cards would be possible but also asm1062 is not that bad - both suffer from the same age problem, they only support pcie 2.0 specs newer chips like jmb585/582 or asm1166/1164/1162 are better for "newer" systems supporting pcie 3.0 (1000Mbyte/s over 500 MByte/s per lane) also opening a new thread for a new problem is the normal way, the tread started 2017, lots of things are different now Edited January 9, 2022 by IG-88 Quote Link to comment Share on other sites More sharing options...
neoooooo Posted January 9, 2022 Share #35 Posted January 9, 2022 Card is from ssu-tech.com china. I ordered delock with marvell chip now. i hipe it will work. Quote Link to comment Share on other sites More sharing options...
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.