Jump to content
XPEnology Community

Sata Controllers not recognized

JigglyJoe

By JigglyJoe
in Hardware Modding

 Share

Recommended Posts

sarieri Junior Member

sarieri

Posted
Posted
2 minutes ago, IG-88 said:

and the proper driver is loaded/used (ahci)

next stop dmesg and compare this with the dmesg results later when tuning switches in grub.cfg

Does "failed to assign" meant that there's no space for the ahci controller anymore so that I need to edit the "set extra_args_918" line in grub.cfg? I looked into disk mapping issues a while ago but never really understand how this actually work...

It seems to me that there are only two controllers for DSM in my case. One is the virtual controller connected to the disk with loader and other two RDM passthru NVME drives, the other controller is the passed through AHCI controller.

Link to comment
Share on other sites
IG-88 Guru Master

IG-88

Posted
Posted
3 minutes ago, sarieri said:

Does "failed to assign" meant that there's no space for the ahci controller anymore so that I need to edit the "set extra_args_918" line in grub.cfg? I looked into disk mapping issues a while ago but never really understand how this actually work...

i would google that error messages, might not be synology related

also i never had a case where disks where not visible in dmesg and anything in grub.cfg made them available, i only know that as way to rearrange already visible drives i a way (like synology does to give them proper order to match hardware slots and software slots in dsm)

 

10 minutes ago, sarieri said:

It seems to me that there are only two controllers for DSM in my case. One is the virtual controller connected to the disk with loader and other two RDM passthru NVME drives, the other controller is the passed through AHCI controller.

cant say much as you not posted your dmesg but when nmve is done by pcie passthroug then it would need a patch in dsm to make a non synology nvme hardware work

https://xpenology.com/forum/topic/13342-nvme-cache-support/page/3/?tab=comments#comment-126755

 

if its mapped as rdm then it should be visible and usable (check the forum search, that was the old way to use nvme disks before the native way worked)

Link to comment
Share on other sites
sarieri Junior Member

sarieri

Posted
Posted (edited)
14 minutes ago, IG-88 said:

i would google that error messages, might not be synology related

also i never had a case where disks where not visible in dmesg and anything in grub.cfg made them available, i only know that as way to rearrange already visible drives i a way (like synology does to give them proper order to match hardware slots and software slots in dsm)

 

cant say much as you not posted your dmesg but when nmve is done by pcie passthroug then it would need a patch in dsm to make a non synology nvme hardware work

https://xpenology.com/forum/topic/13342-nvme-cache-support/page/3/?tab=comments#comment-126755

 

if its mapped as rdm then it should be visible and usable (check the forum search, that was the old way to use nvme disks before the native way worked)

Hi,

Here is the full version dmesg...I thought that vim could pull out the full version...my bad. 

[Sun Jun 28 01:24:51 2020] pci 0000:13:00.0: Signaling PME through PCIe PME interrupt


.....

[Sun Jun 28 01:24:52 2020] ahci 0000:13:00.0: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x3f impl SATA mode
[Sun Jun 28 01:24:52 2020] ahci 0000:13:00.0: flags: 64bit ncq led clo pio slum part ems apst 
[Sun Jun 28 01:24:52 2020] scsi host4: ahci
[Sun Jun 28 01:24:52 2020] scsi host5: ahci
[Sun Jun 28 01:24:52 2020] scsi host6: ahci
[Sun Jun 28 01:24:52 2020] scsi host7: ahci
[Sun Jun 28 01:24:52 2020] scsi host8: ahci
[Sun Jun 28 01:24:52 2020] scsi host9: ahci

The only part that mentions "0000:13:00.0" was this.

dmesg

Edited by sarieri
Link to comment
Share on other sites
IG-88 Guru Master

IG-88

Posted
Posted (edited)

1st controller is vmwares own sata

one boot disk, two other

  

[Sun Jun 28 01:24:51 2020] sd 0:0:0:0: [sda] 102400 512-byte logical blocks: (52.4 MB/50.0 MiB)
...
[Sun Jun 28 01:24:52 2020] sd 1:0:0:0: [sdb] 4000797360 512-byte logical blocks: (2.05 TB/1.86 TiB)
...
[Sun Jun 28 01:24:52 2020] sd 2:0:0:0: [sdc] 12502446768 512-byte logical blocks: (6.40 TB/5.82 TiB)

 

thats the  6 port sata pass through 

[Sun Jun 28 01:24:52 2020] ahci 0000:13:00.0: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x3f impl SATA mode
[Sun Jun 28 01:24:52 2020] ahci 0000:13:00.0: flags: 64bit ncq led clo pio slum part ems apst 
[Sun Jun 28 01:24:52 2020] scsi host4: ahci
[Sun Jun 28 01:24:52 2020] scsi host5: ahci
[Sun Jun 28 01:24:52 2020] scsi host6: ahci
[Sun Jun 28 01:24:52 2020] scsi host7: ahci
[Sun Jun 28 01:24:52 2020] scsi host8: ahci
[Sun Jun 28 01:24:52 2020] scsi host9: ahci
[Sun Jun 28 01:24:52 2020] ata5: SATA max UDMA/133 abar m2048@0xfd2ff000 port 0xfd2ff100 irq 57
[Sun Jun 28 01:24:52 2020] ata6: SATA max UDMA/133 abar m2048@0xfd2ff000 port 0xfd2ff180 irq 57
[Sun Jun 28 01:24:52 2020] ata7: SATA max UDMA/133 abar m2048@0xfd2ff000 port 0xfd2ff200 irq 57
[Sun Jun 28 01:24:52 2020] ata8: SATA max UDMA/133 abar m2048@0xfd2ff000 port 0xfd2ff280 irq 57
[Sun Jun 28 01:24:52 2020] ata9: SATA max UDMA/133 abar m2048@0xfd2ff000 port 0xfd2ff300 irq 57
[Sun Jun 28 01:24:52 2020] ata10: SATA max UDMA/133 abar m2048@0xfd2ff000 port 0xfd2ff380 irq 57

 

and this are the errors to look for and resolve 

[Sun Jun 28 01:24:52 2020] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[Sun Jun 28 01:24:53 2020] clocksource: Switched to clocksource tsc
[Sun Jun 28 01:24:57 2020] ata5.00: qc timeout (cmd 0x27)
[Sun Jun 28 01:24:57 2020] ata5.00: failed to read native max address (err_mask=0x4)
[Sun Jun 28 01:24:57 2020] ata5.00: HPA support seems broken, skipping HPA handling
[Sun Jun 28 01:24:58 2020] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[Sun Jun 28 01:25:03 2020] ata5.00: qc timeout (cmd 0xec)
[Sun Jun 28 01:25:03 2020] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Sun Jun 28 01:25:03 2020] ata5: limiting SATA link speed to 1.5 Gbps
[Sun Jun 28 01:25:04 2020] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[Sun Jun 28 01:25:14 2020] ata5.00: qc timeout (cmd 0xec)
[Sun Jun 28 01:25:14 2020] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Sun Jun 28 01:25:14 2020] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
...

[Sun Jun 28 01:28:20 2020] ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Sun Jun 28 01:28:25 2020] ata10.00: qc timeout (cmd 0xec)
[Sun Jun 28 01:28:25 2020] ata10.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Sun Jun 28 01:28:25 2020] ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Sun Jun 28 01:28:35 2020] ata10.00: qc timeout (cmd 0xec)
[Sun Jun 28 01:28:35 2020] ata10.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Sun Jun 28 01:28:35 2020] ata10: limiting SATA link speed to 3.0 Gbps
[Sun Jun 28 01:28:35 2020] ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[Sun Jun 28 01:29:05 2020] ata10.00: qc timeout (cmd 0xec)
[Sun Jun 28 01:29:05 2020] ata10.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Sun Jun 28 01:29:05 2020] ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 320)

 

Edited by IG-88
Link to comment
Share on other sites
sarieri Junior Member

sarieri

Posted
Posted
2 minutes ago, IG-88 said:

1st controller is vmwares own sata

one boot disk, two other

  


[Sun Jun 28 01:24:51 2020] sd 0:0:0:0: [sda] 102400 512-byte logical blocks: (52.4 MB/50.0 MiB)
...
[Sun Jun 28 01:24:52 2020] sd 1:0:0:0: [sdb] 4000797360 512-byte logical blocks: (2.05 TB/1.86 TiB)
...
[Sun Jun 28 01:24:52 2020] sd 2:0:0:0: [sdc] 12502446768 512-byte logical blocks: (6.40 TB/5.82 TiB)

 

thats the  6 port sata pass through 


[Sun Jun 28 01:24:52 2020] ata5: SATA max UDMA/133 abar m2048@0xfd2ff000 port 0xfd2ff100 irq 57
[Sun Jun 28 01:24:52 2020] ata6: SATA max UDMA/133 abar m2048@0xfd2ff000 port 0xfd2ff180 irq 57
[Sun Jun 28 01:24:52 2020] ata7: SATA max UDMA/133 abar m2048@0xfd2ff000 port 0xfd2ff200 irq 57
[Sun Jun 28 01:24:52 2020] ata8: SATA max UDMA/133 abar m2048@0xfd2ff000 port 0xfd2ff280 irq 57
[Sun Jun 28 01:24:52 2020] ata9: SATA max UDMA/133 abar m2048@0xfd2ff000 port 0xfd2ff300 irq 57
[Sun Jun 28 01:24:52 2020] ata10: SATA max UDMA/133 abar m2048@0xfd2ff000 port 0xfd2ff380 irq 57

 

and this are the errors to look for and resolve 


[Sun Jun 28 01:24:52 2020] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[Sun Jun 28 01:24:53 2020] clocksource: Switched to clocksource tsc
[Sun Jun 28 01:24:57 2020] ata5.00: qc timeout (cmd 0x27)
[Sun Jun 28 01:24:57 2020] ata5.00: failed to read native max address (err_mask=0x4)
[Sun Jun 28 01:24:57 2020] ata5.00: HPA support seems broken, skipping HPA handling
[Sun Jun 28 01:24:58 2020] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[Sun Jun 28 01:25:03 2020] ata5.00: qc timeout (cmd 0xec)
[Sun Jun 28 01:25:03 2020] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Sun Jun 28 01:25:03 2020] ata5: limiting SATA link speed to 1.5 Gbps
[Sun Jun 28 01:25:04 2020] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[Sun Jun 28 01:25:14 2020] ata5.00: qc timeout (cmd 0xec)
[Sun Jun 28 01:25:14 2020] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Sun Jun 28 01:25:14 2020] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
...

[Sun Jun 28 01:28:20 2020] ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Sun Jun 28 01:28:25 2020] ata10.00: qc timeout (cmd 0xec)
[Sun Jun 28 01:28:25 2020] ata10.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Sun Jun 28 01:28:25 2020] ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Sun Jun 28 01:28:35 2020] ata10.00: qc timeout (cmd 0xec)
[Sun Jun 28 01:28:35 2020] ata10.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Sun Jun 28 01:28:35 2020] ata10: limiting SATA link speed to 3.0 Gbps
[Sun Jun 28 01:28:35 2020] ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[Sun Jun 28 01:29:05 2020] ata10.00: qc timeout (cmd 0xec)
[Sun Jun 28 01:29:05 2020] ata10.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Sun Jun 28 01:29:05 2020] ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 320)

 

So this has nothing to do with the configuration of set extra_args_918 in grub.cfg right?

Link to comment
Share on other sites
sarieri Junior Member

sarieri

Posted
Posted
6 minutes ago, IG-88 said:

yes, but you can also append it manually to the arguments in "set common_args_918"

Not working...Well, I did some research on google and maybe I will give it a try later. For now, KVM and UNRAID passthru the AHCI controller fine but not ESXI. Might be something wrong with reset mode(d3d0) of the controller.

Link to comment
Share on other sites
sarieri Junior Member

sarieri

Posted
Posted (edited)
19 hours ago, IG-88 said:

different kernel (3.10.105 vs 4.4.59) and there are some differences in the settings how its compiled too but i guess it the kernel version

Hi,

Sorry to bother again, but it looks there is still some problem. So I played with SataPortmap in grub.cfg in order to have all six drives that connect to the AHCI controller recognized by DSM. DSM did recognize all 6 drives, but it performs a repair on the storage pool(SHR). The Storage pool is repaired now and shows healthy, but the volume is creashed and data is read only. Do you know if there's anything I can do now or I just have to backup things and rebuild everything.

H0M4776J3NMJ8AWZ4}7I8DM.png

K~}Y3JV%B62(D}Z@W(YTU33.png

Edited by sarieri
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing
×
×
  • Create New...