Driver extension jun 1.03b/1.04b for DSM6.2.3 for 918+ / 3615xs / 3617xs


Recommended Posts

I am tring to install this drivers because i recently get a r8125. Smart and hybernation works fine for me. I am on 6.2.3u3 on a baremetal.

 

I had a glitch, as insturcted, I have put 4 files to usb stick and removed old driver folders. When i tried to boot into os, it failed, I was not able to ping the system with old eth. I have tried standard and syno packages. No luck.

 

When i return back to original files, OS booted up successfully.

 

What i am doing wrong?

 

Thanks

Link to post
Share on other sites
53 minutes ago, Vitaly said:

extra3617_v0.11.2_test for 6.2.3 tg3 driver version is 3.132 and bonding two hp i330 ethernet adapters doesn't work correctly.

extra3617_v0.5_test for 6.2.2 tg3 driver version is 3.137k everything is OK

thanks, its now on my todo list, the older one will be the one from kernel 3.10.105 i guess

 

Link to post
Share on other sites

Hi @IG-88 sorry for probably stupid question but is it so this AHCI driver for Marvell 88SE9125 is part of 3615/17 loader only?

I am bit stuck with J5040 and Marvell 88SE9125 when I run 918+ I cannot utilize additional 2 disks except onboard controller properly and I don't know where to else to look in this forum.

 

Funny is that it seems recognize somehow in drives numbers because it skipped 3. and 4. as you see:

 

image.thumb.png.01db578b485e6b0c1b5ef491d5c912f8.png

 

I will appreciate any help here, since the same controller worked with FREENAS / TRUENAS native OS but I want to use 5 drives in one LUN and have 6. drive for backup purpose what is not supported by ZFS (only in pairs which wont be fitting my usecase)

 

Best Regards!

Gryllz

 

 

 

Edited by Gryllz
Link to post
Share on other sites
35 minutes ago, Gryllz said:

I am bit stuck with J5040 and Marvell 88SE9125 when I run 918+ I cannot utilize additional 2 disks except onboard controller properly and I don't know where to else to look in this forum.

if its Asrock J5040-ITX the its would be normal, as CPU/sock have 2 sata ports and asrock adds 2 port asm1061 do a added controller would be 5/6

you can check /var/log/dmesg (or just type dmesg on commandline) to see what controller os using what port (ata01, ata02, ...)

with 3/4 unused it looks more like the asm1061 is not working propperly

the 88se9125 should be working as ahci

https://ata.wiki.kernel.org/index.php/SATA_hardware_features

 

on some system were the chipset has more asata ports the is used on the board it can be ssen too (4 ports onboard but added controller start with 7)

as long as you come near the maximum (12 for 3615/17 and 16 for 918+) its just a cosmetic problem

 

Link to post
Share on other sites
11 hours ago, IG-88 said:

if its Asrock J5040-ITX the its would be normal, as CPU/sock have 2 sata ports and asrock adds 2 port asm1061 do a added controller would be 5/6

you can check /var/log/dmesg (or just type dmesg on commandline) to see what controller os using what port (ata01, ata02, ...)

with 3/4 unused it looks more like the asm1061 is not working propperly

the 88se9125 should be working as ahci

https://ata.wiki.kernel.org/index.php/SATA_hardware_features

 

on some system were the chipset has more asata ports the is used on the board it can be ssen too (4 ports onboard but added controller start with 7)

as long as you come near the maximum (12 for 3615/17 and 16 for 918+) its just a cosmetic problem

 

Yes I do have Asrock J5040-ITX.

I found these in report, it seems affected is ata3 and 4 because of the errors in the report:

I am not sure how to troubleshoot this. :( I am still Nob here.

 

[    2.296609] ata3: SATA max UDMA/133 abar m2048@0xa1210000 port 0xa1210100 irq                                                                                                                                               123
[    2.296623] ata4: SATA max UDMA/133 abar m2048@0xa1210000 port 0xa1210180 irq                                                                                                                                               123
[    2.301968] DMAR: DRHD: handling fault status reg 2
[    2.302300] DMAR: DMAR:[DMA Write] Request device [01:00.1] fault addr fffe00                                                                                                                                              00
               DMAR:[fault reason 02] Present bit in context entry is clear
[    2.354380]  sdb: sdb1 sdb2 sdb5
[    2.355203] sd 1:0:0:0: [sdb] Attached SCSI disk
[    2.600704] DMAR: DRHD: handling fault status reg 2
[    2.601078] DMAR: DMAR:[DMA Read] Request device [01:00.1] fault addr fffe000                                                                                                                                              0
               DMAR:[fault reason 02] Present bit in context entry is clear
[    2.750883] clocksource: Switched to clocksource tsc
[   12.294652] ata3: softreset failed (1st FIS failed)
[   12.300762] DMAR: DRHD: handling fault status reg 2
[   12.301139] DMAR: DMAR:[DMA Write] Request device [01:00.1] fault addr fffe00                                                                                                                                              00
               DMAR:[fault reason 02] Present bit in context entry is clear
[   12.599602] DMAR: DRHD: handling fault status reg 2
[   12.599981] DMAR: DMAR:[DMA Read] Request device [01:00.1] fault addr fffe000                                                                                                                                              0
               DMAR:[fault reason 02] Present bit in context entry is clear
[   22.293616] ata3: softreset failed (1st FIS failed)
[   22.299522] DMAR: DRHD: handling fault status reg 2
[   22.299897] DMAR: DMAR:[DMA Write] Request device [01:00.1] fault addr fffe00                                                                                                                                              00
               DMAR:[fault reason 02] Present bit in context entry is clear
[   22.598564] DMAR: DRHD: handling fault status reg 2
[   22.598929] DMAR: DMAR:[DMA Read] Request device [01:00.1] fault addr fffe000                                                                                                                                              0
               DMAR:[fault reason 02] Present bit in context entry is clear
[   57.287482] ata3: softreset failed (1st FIS failed)
[   57.287859] ata3: limiting SATA link speed to 3.0 Gbps
[   57.297589] DMAR: DRHD: handling fault status reg 2
[   57.297958] DMAR: DMAR:[DMA Write] Request device [01:00.1] fault addr fffe00                                                                                                                                              00
               DMAR:[fault reason 02] Present bit in context entry is clear
[   57.592433] DMAR: DRHD: handling fault status reg 2
[   57.592807] DMAR: DMAR:[DMA Read] Request device [01:00.1] fault addr fffe000                                                                                                                                              0
               DMAR:[fault reason 02] Present bit in context entry is clear
[   62.287468] ata3: softreset failed (1st FIS failed)
[   62.287837] ata3: reset failed, giving up
[   62.592411] ata4: SATA link down (SStatus 0 SControl 330)
[   62.592418] ata4: No present pin info for SATA link down event
[   62.593065] ahci 0000:04:00.0: SSS flag set, parallel bus scan disabled
[   62.593112] ahci 0000:04:00.0: AHCI 0001.0200 32 slots 2 ports 6 Gbps 0x3 imp  

Link to post
Share on other sites
3 hours ago, Gryllz said:

Yes I do have Asrock J5040-ITX.

I found these in report, it seems affected is ata3 and 4 because of the errors in the report:

I am not sure how to troubleshoot this

from the board specs the 3&4 would be asm1061, no general trouble with that one

to be sure you would need to back track the device [01:00.1] in /var/log/dmesg to its pci vendor and device id to see if its asm1061 or 9215

maybe some kernel parameter in grub.cfg can help (like iommu=pt) but 1st try would be to disable VT-d in bios

 

  • Thanks 1
Link to post
Share on other sites
2 hours ago, IG-88 said:

from the board specs the 3&4 would be asm1061, no general trouble with that one

to be sure you would need to back track the device [01:00.1] in /var/log/dmesg to its pci vendor and device id to see if its asm1061 or 9215

maybe some kernel parameter in grub.cfg can help (like iommu=pt) but 1st try would be to disable VT-d in bios

 

YEAH!

disable VT-d in bios did a trick!

Thank you very much @IG-88 you are hero of my day :)

 

I have only remaining issue that disk is diffent size and brand and for some reason I cannot add it from Action button add disk to already existing 4 disk pool, is that by design or can I hack this somehow? at least is visible under the disk list now and as available and I can create new pool from it ...

Edited by Gryllz
Link to post
Share on other sites
41 minutes ago, Gryllz said:

I have only remaining issue that disk is diffent size and brand and for some reason I cannot add it from Action button add disk to already existing 4 disk pool, is that by design or can I hack this somehow? at least is visible under the disk list now and as available and I can create new pool from it ...

 

you can use the KB of synology for things like this as you use dsm as any other synology user

https://www.synology.com/en-global/knowledgebase/DSM/help/DSM/StorageManager/storage_pool_expand_add_disk

...
Drive requirements:

Please make sure the drives that you intend to add to your Synology NAS meet the following requirements:

RAID or SHR configuration must be created by drives of the same type. Using drives of different types will affect system reliability and performance. Mixed drive types as shown below are not supported for RAID or SHR configuration:
SATA drives and SAS drives
4K native drives and non-4K native drives

For SHR: The capacity of the drive you intend to add must be equal to or larger than the largest drive in the storage pool, or equal to any of the drives in the storage pool.
Example: If an SHR storage pool is composed of three drives (2 TB, 1.5 TB, and 1 TB), we recommend that the newly-added drive should be at least 2 TB for a better capacity usage. You can consider adding 1.5 TB and 1 TB drives, but please note that some capacity of the 2 TB drive will remain unused.

For RAID 5, RAID 6, or RAID F1: The capacity of the drive you intend to add must be equal to or larger than the smallest drive in the storage pool.
Example: If a RAID 5, RAID 6, or RAID F1 storage pool is composed of three drives (2 TB, 1.5 TB, and 1 TB), then the capacity of the new drive must be at least 1 TB.
...

 

  • Like 1
Link to post
Share on other sites
8 minutes ago, IG-88 said:

 

you can use the KB of synology for things like this as you use dsm as any other synology user

https://www.synology.com/en-global/knowledgebase/DSM/help/DSM/StorageManager/storage_pool_expand_add_disk


...
Drive requirements:

Please make sure the drives that you intend to add to your Synology NAS meet the following requirements:

RAID or SHR configuration must be created by drives of the same type. Using drives of different types will affect system reliability and performance. Mixed drive types as shown below are not supported for RAID or SHR configuration:
SATA drives and SAS drives
4K native drives and non-4K native drives

For SHR: The capacity of the drive you intend to add must be equal to or larger than the largest drive in the storage pool, or equal to any of the drives in the storage pool.
Example: If an SHR storage pool is composed of three drives (2 TB, 1.5 TB, and 1 TB), we recommend that the newly-added drive should be at least 2 TB for a better capacity usage. You can consider adding 1.5 TB and 1 TB drives, but please note that some capacity of the 2 TB drive will remain unused.

For RAID 5, RAID 6, or RAID F1: The capacity of the drive you intend to add must be equal to or larger than the smallest drive in the storage pool.
Example: If a RAID 5, RAID 6, or RAID F1 storage pool is composed of three drives (2 TB, 1.5 TB, and 1 TB), then the capacity of the new drive must be at least 1 TB.
...

 

ok, thank you for enlighting me, I will take it from there.

Link to post
Share on other sites

Hey would you like to fix and provide a driver extension pack for this? I tried editing /etc/rc.modules in extra{,2}.lzma but in 7-Zip this is a read only archive so I can't do it myself easily. You have the source to reproduce the pack. I think the kernel version is not matching. I want to use virtio so that I can squeeze most of the performance as much as possible so that it can go production. I'm running DSM off of my Proxmox NAS box running atop of ZFS right now and I think DSM and Proxmox can complement each other well :) I have the commands to load virtio in my log.txt, you can take a look. There is some symbols indeed not found in the kernel and maybe I think I need to change the kernel too or swap to DS361x

log.txt

Link to post
Share on other sites

I am trying to to install xpenology on intel NUC NUC8i3BEH (Intel® Core™ i3-8109U, Intel® Ethernet Connection I219-V)
I have tried :

  • v1.04b DS918+ 
  • v1.04b DS918+  with:  extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.3 v0.13.3
  • v1.04b DS918+  with:  extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.3 v0.12.1

I always get  find.synology.com.
But I am not able to connect to it using SynologyAssitant
I also don't see any new entry in the DHCP server.

Can anyone help me ?
I think the driver for this device is e1000e, but it's not working.
 

Link to post
Share on other sites
3 hours ago, Steve Fan said:

Hey would you like to fix and provide a driver extension pack for this? I tried editing /etc/rc.modules in extra{,2}.lzma but in 7-Zip this is a read only archive so I can't do it myself easily.

7-zip is ok for having a look (unpack)

for repacking it there is a proper way everyone can use on any linux (live/recue linux from usb or in a VM), the unpacking and repacking is part of the description for having new drivers, for repacking just skip the parts about making the kernel drivers

https://xpenology.com/forum/topic/7187-how-to-build-and-inject-missing-drivers-in-jun-loader-102a/

 

i'm already on it in case of kvm/proxmox and 9p

you log does not really help as it does not show what symbols are missing, you would also need to check dmesg and messages in /var/log/

i guess i know at least one missing module (aufs.ko) but there might be more, so if you could provide more details about what the modules are missing

also the sequence of loading the modules need to be right order insmod just try's to load a module and if you dont do it in the right order you will get unknown symbol even if you have the right module, in theory "modprobe" would look for dependencies of modules and automatically load them is present but that not helping for rc.modules for that i need to know exactly waht modules are needed and if possible the order (dependencies of modules can be checked. in theory there should be a entry in the module for a dependency

atm i have this but i dont know if its right and if something is missing (i also have a note on my todo that "virtio_input.ko" is missing)

virtio
virtio_ring
virtio_pci
virtio_mmio
virtio_net
virtio_blk
virtio_scsi
9pnet
9pnet_virtio
9p

 

i want that to be present in the next version or at least a have special version for this but atm i struggle with whats needed and in what order it needs to be loaded

 

 

1 hour ago, petersnows said:

I am trying to to install xpenology on intel NUC NUC8i3BEH (Intel® Core™ i3-8109U, Intel® Ethernet Connection I219-V)
...
I think the driver for this device is e1000e, but it's not working.

 

can you boot a live/rescue linux and see what lspci has about that device (vendor and device id including sub id's if present)

 

Link to post
Share on other sites
Quote

can you boot a live/rescue linux and see what lspci has about that device (vendor and device id including sub id's if present)


I was able to get SynologyAssistant to work, connecting an USB-Ethernet card.
Just by connecting it, without changing anything else.  I can now see both network cards (the usb one and the intelNUC one).

Do you know why ?


synologyAssistant-pub.thumb.JPG.f9e0cd3b08db73090c77b0e826c5d58f.JPG


I then installed the DSM like usual.
No I notice that the CPU in controlPanel (J3455) is not the one on the machine. ( i3-8109U CPU)
Does this impacts the performance ?
SynologyCPU-pub.thumb.jpg.94d3ac76d0a06e87e92e255d73162f25.jpg
 

 

Here you have the lscpi   (of the NUC8i3BEH  after installed the DSM)
I removed the usb-ethernet device, after installed the DSM

 

admin@syno:/proc/net$ lspci -q
0000:00:00.0 Host bridge: Intel Corporation Device 3ecc (rev 08)
0000:00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-U GT3e [Iris Plus Graphics 655] (rev 01)
0000:00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
0000:00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30)
0000:00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30)
0000:00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30)
0000:00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30)
0000:00:17.0 SATA controller: Intel Corporation Cannon Point-LP SATA Controller [AHCI Mode] (rev 30)
0000:00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0)
0000:00:1d.6 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #15 (rev f0)
0000:00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30)
0000:00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30)
0000:00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30)
0000:00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 30)
0000:00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (6) I219-V (rev 30)
0000:02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01)
0001:00:12.0 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SATA AHCI Controller (rev ff)
0001:00:13.0 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #1 (rev ff)
0001:00:14.0 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #1 (rev ff)
0001:00:15.0 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series USB xHCI (rev ff)
0001:00:16.0 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series I2C Controller #1 (rev ff)
0001:00:18.0 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 (rev ff)
0001:00:19.2 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SPI Controller #3 (rev ff)
0001:00:1f.1 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SMBus Controller (rev ff)
0001:01:00.0 Non-VGA unclassified device: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller (rev ff)
0001:02:00.0 Non-VGA unclassified device: Intel Corporation I211 Gigabit Network Connection (rev ff)
0001:03:00.0 Non-VGA unclassified device: Intel Corporation I211 Gigabit Network Connection (rev ff)
pcilib: Cannot write to /var/services/homes/admin/.pciids-cache: No such file or directory
admin@syno:/proc/net$ lspci
0000:00:00.0 Class 0600: Device 8086:3ecc (rev 08)
0000:00:02.0 Class 0300: Device 8086:3ea5 (rev 01)
0000:00:08.0 Class 0880: Device 8086:1911
0000:00:12.0 Class 1180: Device 8086:9df9 (rev 30)
0000:00:14.0 Class 0c03: Device 8086:9ded (rev 30)
0000:00:14.2 Class 0500: Device 8086:9def (rev 30)
0000:00:16.0 Class 0780: Device 8086:9de0 (rev 30)
0000:00:17.0 Class 0106: Device 8086:9dd3 (rev 30)
0000:00:1d.0 Class 0604: Device 8086:9db0 (rev f0)
0000:00:1d.6 Class 0604: Device 8086:9db6 (rev f0)
0000:00:1f.0 Class 0601: Device 8086:9d84 (rev 30)
0000:00:1f.3 Class 0403: Device 8086:9dc8 (rev 30)
0000:00:1f.4 Class 0c05: Device 8086:9da3 (rev 30)
0000:00:1f.5 Class 0c80: Device 8086:9da4 (rev 30)
0000:00:1f.6 Class 0200: Device 8086:15be (rev 30)
0000:02:00.0 Class ff00: Device 10ec:522a (rev 01)
0001:00:12.0 Class 0000: Device 8086:5ae3 (rev ff)
0001:00:13.0 Class 0000: Device 8086:5ad8 (rev ff)
0001:00:14.0 Class 0000: Device 8086:5ad6 (rev ff)
0001:00:15.0 Class 0000: Device 8086:5aa8 (rev ff)
0001:00:16.0 Class 0000: Device 8086:5aac (rev ff)
0001:00:18.0 Class 0000: Device 8086:5abc (rev ff)
0001:00:19.2 Class 0000: Device 8086:5ac6 (rev ff)
0001:00:1f.1 Class 0000: Device 8086:5ad4 (rev ff)
0001:01:00.0 Class 0000: Device 1b4b:9215 (rev ff)
0001:02:00.0 Class 0000: Device 8086:1539 (rev ff)
0001:03:00.0 Class 0000: Device 8086:1539 (rev ff)
admin@syno:/proc/net$

 

 



 

Link to post
Share on other sites
3 hours ago, petersnows said:

I then installed the DSM like usual.
No I notice that the CPU in controlPanel (J3455) is not the one on the machine. ( i3-8109U CPU)
Does this impacts the performance ?

remeber the faq?

https://xpenology.com/forum/topic/9392-general-faq/?do=findComment&comment=82391

if you need it to shown the real cpu then you can use this

https://xpenology.com/forum/topic/13030-dsm-5x6x-cpu-name-cores-infomation-change-tool/

 

3 hours ago, petersnows said:

Here you have the lscpi   (of the NUC8i3BEH  after installed the DSM)
I removed the usb-ethernet device, after installed the DSM

not important anymore if the driver in the extra/extra2 is working

 

3 hours ago, petersnows said:

Do you know why ?

there are lots of possibility's, wrong/old extra.lzma used, rj-45 connector not plugged in properly,. cable problems

you would need to repeat your steps and might find out you cant reproduce it

most simple test just take any empty usb, put the loader on it (dont bother about usb vid/pid, as long as you dont start installing is does not matter if its wrong), add the newer extra/extra2, disconnect your drive(s) and working usb, connect your test usb boot and try to find it in network with synology assistant

 

Edited by IG-88
Link to post
Share on other sites
13 hours ago, IG-88 said:

7-zip is ok for having a look (unpack)

for repacking it there is a proper way everyone can use on any linux (live/recue linux from usb or in a VM), the unpacking and repacking is part of the description for having new drivers, for repacking just skip the parts about making the kernel drivers

https://xpenology.com/forum/topic/7187-how-to-build-and-inject-missing-drivers-in-jun-loader-102a/

 

i'm already on it in case of kvm/proxmox and 9p

you log does not really help as it does not show what symbols are missing, you would also need to check dmesg and messages in /var/log/

i guess i know at least one missing module (aufs.ko) but there might be more, so if you could provide more details about what the modules are missing

also the sequence of loading the modules need to be right order insmod just try's to load a module and if you dont do it in the right order you will get unknown symbol even if you have the right module, in theory "modprobe" would look for dependencies of modules and automatically load them is present but that not helping for rc.modules for that i need to know exactly waht modules are needed and if possible the order (dependencies of modules can be checked. in theory there should be a entry in the module for a dependency

atm i have this but i dont know if its right and if something is missing (i also have a note on my todo that "virtio_input.ko" is missing)





virtio
virtio_ring
virtio_pci
virtio_mmio
virtio_net
virtio_blk
virtio_scsi
9pnet
9pnet_virtio
9p

 

i want that to be present in the next version or at least a have special version for this but atm i struggle with whats needed and in what order it needs to be loaded

 

 

 

can you boot a live/rescue linux and see what lspci has about that device (vendor and device id including sub id's if present)

 

Yes I followed the order of loading module and now it somehow works, at least the virtio net driver does, meanwhile balloon and the rest doesn't:

Quote

[Sun Feb 21 14:27:36 2021] virtio_balloon: Unknown symbol balloon_page_dequeue (err 0)
[Sun Feb 21 14:27:36 2021] virtio_balloon: Unknown symbol balloon_page_enqueue (err 0)
[Sun Feb 21 14:27:43 2021] virtio_console: Unknown symbol hvc_remove (err 0)
[Sun Feb 21 14:27:43 2021] virtio_console: Unknown symbol hvc_kick (err 0)
[Sun Feb 21 14:27:43 2021] virtio_console: Unknown symbol hvc_alloc (err 0)
[Sun Feb 21 14:27:43 2021] virtio_console: Unknown symbol hvc_poll (err 0)
[Sun Feb 21 14:27:43 2021] virtio_console: Unknown symbol hvc_instantiate (err 0)
[Sun Feb 21 14:27:43 2021] virtio_console: Unknown symbol __hvc_resize (err 0)

 

Also interestingly I checked lsmod to see the deps:

Quote

9pnet_virtio            6815  0
9pnet                  39704  2 9p,9pnet_virtio
virtio_blk              8736  0
virtio_net             20523  0
virtio_mmio             5270  0
virtio_pci             14135  0
virtio_scsi            10558  0
virtio_ring             6787  6 virtio_blk,virtio_net,virtio_pci,9pnet_virtio,virtio_mmio,virtio_scsi
virtio                  5337  6 virtio_blk,virtio_net,virtio_pci,9pnet_virtio,virtio_mmio,virtio_scsi

 

But I don't know why it is not built-in since Linux kernel should have had included these out of the box. I also don't see why Synology will cherry pick these modules since it is not really impacting any performance, plus by the inclusion of virtio they can utilize the VM station more efficiently thus bringing in more value to the customers. Silly choice for Synology.

 

Also it seems like there is a problem with virtio scsi? I have attached an excerpt of the log from dmesg and you can check it out.

Quote

[Sun Feb 21 14:26:15 2021] blk_update_request: I/O error, dev vda, sector 0
[Sun Feb 21 14:26:15 2021] Buffer I/O error on dev vda, logical block 0, async page read
[Sun Feb 21 14:26:15 2021] blk_update_request: I/O error, dev vda, sector 0
[Sun Feb 21 14:26:15 2021] Buffer I/O error on dev vda, logical block 0, async page read
[Sun Feb 21 14:26:15 2021] blk_update_request: I/O error, dev vda, sector 0
[Sun Feb 21 14:26:15 2021] Buffer I/O error on dev vda, logical block 0, async page read
[Sun Feb 21 14:26:15 2021]  vda: unable to read partition table
[Sun Feb 21 14:26:15 2021] blk_update_request: I/O error, dev vda, sector in range 268431360 + 0-2(12)
[Sun Feb 21 14:26:15 2021] blk_update_request: I/O error, dev vda, sector 268435328
[Sun Feb 21 14:26:15 2021] Buffer I/O error on dev vda, logical block in range 33550336 + 0-2(12) , async page read
[Sun Feb 21 14:26:31 2021] blk_update_request: I/O error, dev vda, sector in range 0 + 0-2(12)
[Sun Feb 21 14:26:31 2021] blk_update_request: I/O error, dev vda, sector 0
[Sun Feb 21 14:26:31 2021] Buffer I/O error on dev vda, logical block in range 0 + 0-2(12) , async page read
[Sun Feb 21 14:26:43 2021] blk_update_request: I/O error, dev vda, sector 0
[Sun Feb 21 14:26:43 2021] blk_update_request: I/O error, dev vda, sector 0
[Sun Feb 21 14:26:43 2021] Buffer I/O error on dev vda, logical block 0, async page read
[Sun Feb 21 14:26:46 2021] blk_update_request: I/O error, dev vda, sector 0
[Sun Feb 21 14:26:46 2021] blk_update_request: I/O error, dev vda, sector 0
[Sun Feb 21 14:26:46 2021] Buffer I/O error on dev vda, logical block 0, async page read

 

Edited by Steve Fan
Link to post
Share on other sites
3 hours ago, Steve Fan said:

But I don't know why it is not built-in since Linux kernel should have had included these out of the box. I

that depnds on the kernel config you use for compiling a normal linux might try to be universal as possible a appliance like dsm is made to fit a purpose

being a appliance with lots a custom kernel mods impacts other functions, so they tend to only activate whats needed and its also limiting customers going wild with uncertified hardware or extending in a way its not intended (like deliberately removing multiplexer support in ~2013/2014)

also they broke sata_*.kon and pata_*.ko modules with modifications and as they dont need them they did no care about the broken code in the kernel, if WE need it we will have to fix it ourself (why should they care for hacker and freeloader?)

 

3 hours ago, Steve Fan said:

I also don't see why Synology will cherry pick these modules since it is not really impacting any performance, plus by the inclusion of virtio they can utilize the VM station more efficiently thus bringing in more value to the customers. Silly choice for Synology.

there is virtual dsm for that purpose and they include all thats needed for virtio there and if needed all the necessary kernel options are that in this

as of the appliance model its not intended to visualize a 3615/3617 or 918+ so it does nor need this stuff (same for hyper-v extensions in the kernel)

 

 

3 hours ago, Steve Fan said:

Also it seems like there is a problem with virtio scsi? I have attached an excerpt of the log from dmesg and you can check it out.

Quote

[Sun Feb 21 14:26:15 2021] blk_update_request: I/O error, dev vda, sector 0
[Sun Feb 21 14:26:15 2021] Buffer I/O error on dev vda, logical block 0, async page read
[Sun Feb 21 14:26:15 2021] blk_update_request: I/O error, dev vda, sector 0
[Sun Feb 21 14:26:15 2021] Buffer I/O error on dev vda, logical block 0, async page read
[Sun Feb 21 14:26:15 2021] blk_update_request: I/O error, dev vda, sector 0
[Sun Feb 21 14:26:15 2021] Buffer I/O error on dev vda, logical block 0, async page read
[Sun Feb 21 14:26:15 2021]  vda: unable to read partition table
[Sun Feb 21 14:26:15 2021] blk_update_request: I/O error, dev vda, sector in range 268431360 + 0-2(12)
[Sun Feb 21 14:26:15 2021] blk_update_request: I/O error, dev vda, sector 268435328
[Sun Feb 21 14:26:15 2021] Buffer I/O error on dev vda, logical block in range 33550336 + 0-2(12) , async page read
[Sun Feb 21 14:26:31 2021] blk_update_request: I/O error, dev vda, sector in range 0 + 0-2(12)
[Sun Feb 21 14:26:31 2021] blk_update_request: I/O error, dev vda, sector 0
[Sun Feb 21 14:26:31 2021] Buffer I/O error on dev vda, logical block in range 0 + 0-2(12) , async page read
[Sun Feb 21 14:26:43 2021] blk_update_request: I/O error, dev vda, sector 0
[Sun Feb 21 14:26:43 2021] blk_update_request: I/O error, dev vda, sector 0
[Sun Feb 21 14:26:43 2021] Buffer I/O error on dev vda, logical block 0, async page read
[Sun Feb 21 14:26:46 2021] blk_update_request: I/O error, dev vda, sector 0
[Sun Feb 21 14:26:46 2021] blk_update_request: I/O error, dev vda, sector 0
[Sun Feb 21 14:26:46 2021] Buffer I/O error on dev vda, logical block 0, async page read

 

 

no idea where that is comming from, i cant do any kernel source mod's as i'm not a coder (just a monkey with a keyboard when it comes to this)

Link to post
Share on other sites
Quote

there are lots of possibility's, wrong/old extra.lzma used, rj-45 connector not plugged in properly,. cable problems

you would need to repeat your steps and might find out you cant reproduce it

most simple test just take any empty usb, put the loader on it (dont bother about usb vid/pid, as long as you dont start installing is does not matter if its wrong), add the newer extra/extra2, disconnect your drive(s) and working usb, connect your test usb boot and try to find it in network with synology assistant


Thanks IG-88 

I have tested before installing the DSM.
I created a usb pen with: v1.04b DS918+  with:  extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.3 v0.12.1 

  1. plug the usb pen and booted
    find.synology.com appears but I am not able to connect to it using SynologyAssitant
  2. plug the usb pen and booted
    find.synology.com appears but I am not able to connect to it using SynologyAssitant
    plug an "usb-Ethernet device"
    find.synology.com appears and I am able to connect using SynologyAssitant 
    I don't even use the "usb-Ethernet device" to connect to it

I repeated the above 2 steps 3 times, I would get the same result over and over.
Connecting the "usb-Ethernet device" would make the "Ethernet Connection I219-V" to work and ask for an IP.
 

Quote

s, wrong/old extra.lzma used, rj-45 connector not plugged in properly,. cable problems


I always used the same usb pen. The RJ45 was well connected, I could see the lights on the switch and on the  "Ethernet Connection I219-V".

One question, what is the  usb vid/pid for ? When it's used ?
After I install the the DSM, what does the synoboot (usb pen) do ?
Does it changes and teaks the DSM installation everytime it boots ?

If I want to duplicate the USB pen to replace the existing one.
I just need to:

  • recreate it like I did with the first one
  • grub.cfg (vid/pid, depending on the usb pen brand, mac, serial)
  • use the rd.gz, zImage of the latest installed pat file 

Or there is any other file that I need to be aware ?

Edited by petersnows
Link to post
Share on other sites
19 minutes ago, petersnows said:

I created a usb pen with: v1.04b DS918+  with:  extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.3 v0.12.1 

  1. plug the usb pen and booted
    find.synology.com appears but I am not able to connect to it using SynologyAssitant
  2. plug the usb pen and booted
    find.synology.com appears but I am not able to connect to it using SynologyAssitant
    plug an "usb-Ethernet device"
    find.synology.com appears and I am able to connect using SynologyAssitant 
    I don't even use the "usb-Ethernet device" to connect to it

 

thats interesting, the presence of a usb adapter should not make a difference

also with my systems (having 3 diffrent hardware types and about 6 ot 7 different nic types)  i never had the problem that a driver present would not work

atm i would not have a logical explanation why a usb nic would make a difference or why a working nic driver only is working if a 2nd one is present

 

23 minutes ago, petersnows said:

One question, what is the  usb vid/pid for ? When it's used ?

original synology units use a specific unique id of f400/f400, in some way the loader needs to spoof that and i guess its a comparison spoof where the f400/f400 gets replaced with the values we put in grub.cfg and if the code compares what it should be (our grub values now) it comes out with a true and continues

its checked when installing the *.pat file to disk and later after install its also checked in the start/boot process (along other things aka protections)

 

29 minutes ago, petersnows said:

After I install the the DSM, what does the synoboot (usb pen) do ?

beside spoofing some things making the dsm think its still running on a original hardware it just provides the dsm original kernel for being able to start reading the system from disk (raid1 over all disks), after boot its unmounted and the only occasion where its used with dsm running is when making a update, in that process the new kernel (if there is any) needs to be copied to usb before booting the new updated version

so its no problem removing the usb while dsm is running but you will need it on every boot as its the boot loader (just a few megabyte are processed so no need for some huge or extra fast usb flash drives)

 

34 minutes ago, petersnows said:

Does it changes and teaks the DSM installation everytime it boots ?

yes thats too, at least it looks for it and try's to change things if needed, there is also a patch mechanism involved that, if it hits a already patched file, it will not patch, but after installing a update there are files back to default and will  be patched on 1st boot with a new dsm new version (among other things restoring the 16 drives we have with 918+, syno's default is just 4) - there are lots of things that can go wrong after udpates of dsm, but in most cases it does not and synology obviously does not care much, they could easily throw in some changes to specifically hinder the loader to do the patching (but we a could also adapt the patching of the files if needed so it would be a dead race, usually synology "rises the bar" with new main versions like 6.1, 6.2 or 7.0)

 

also it compares the added kernel module files on boot and if they are different they will be copied again from loader to disk (so even if you replace one of the modules manually on disk - in the update directory where the loader keeps its modules -then it will be replaced with the one from the loader because its different

(there is also a pre boot kernel that is loaded before synologys original kernel, my guess it emulates hardware devices present on the original hardware so when dsm checks for there presence they come back as existing, one of the reasons why a loader is specific for a certain dsm hardware model)

 

if you want to have a closer look just open extra.lzma with 7zip and look for the files in etc, there is jun.patch, that is tried to apply on booting

(918+ has a extra2.lzma containing a 2nd different patch, witch one is loaded seems to be decided in the pro boot kernel, so its up to guessing when extra2 is used, my guess is when its a fresh install and on normal boots its extra)

the pre boot kernel is bzImage on the 1st partition on the loader, with the proper tools that one can be decomposed too but you will end with code you would need to reverse engineer so thats for some more hardcore coder, i was not able to find out he logic about extra/extra2 that way so its based on trying a little with modding rc.modules in both extra's to see what is used on what occasion, thats what my guess is based on

  • Thanks 1
Link to post
Share on other sites
1 hour ago, petersnows said:

just need to:

  • recreate it like I did with the first one
  • grub.cfg (vid/pid, depending on the usb pen brand, mac, serial)

if its the same system keep mac, usb vid/pid needs to mach the usb device used

mac is only needed for WOL and convenience  (some protection, like in survailance station, check the match on sn and mac to it might be important to keep a sn and mach together if they are from a original system or "valid" generated)

if adding or removing nic's it need to be looked for as the order of nic's may change, so the mac's 1,2,3, ... might not fit the hardware anymore

also still some special in 918+, only 2 nic's are default, so when adding a 2 port nic one port will be outside when installing a update

in my system its the onboard nic gets 3rd and the maintenance nic (onboard 1G) is not working anymore and also the eth0 eth1 in dsm will not be working anymore as before, can get messy to regain access over network if you worked with 9k mtu, vlan, or teaming

serial console can help here but most people dont have/use this, a good amount of logic and knowledge can help too  to get things back to normal but best would still be a extended patch to also patch the number of nic's at boot like the number of drives (as i'm back to 918+ for my main nas i got the nic fun after the cross upgrade from 3617 so i#m kind of motivated to have this patched as its annoying to care about this after updates)

 

1 hour ago, petersnows said:
  • use the rd.gz, zImage of the latest installed pat file 

 

yes but if you dont and boot up the system will not start and when you use synology assistant then it will offer you to fix this (usually reading the kernel from system disk and write it to the loader, only takes seconds)

its more important to know/remember that there is a kernel mismatch when redoing the loader

 

1 hour ago, petersnows said:

Or there is any other file that I need to be aware ?

 

no only grub.cfg, extra(extra2 if its 918+) if you changed them from the original loader and the kernel files of dsm on the 2nd partiton

beside the usb vid/pid, number and mac of nic's there can be other changes to the grub.cfg that need to be documented, like adding kernel parameters to handle special adjustments like disable NCQ for the kernel (seen WD drives having problems with NCQ last week with newer jmb585 on 3617 ahci driver)

when doing changes like this later on they might not end in the "documentation"

same goes for bios settings, might be important for CSM/legacy mode on uefi bios or disabling vt-d for a asm1061 controller, if a cmos battery dies it can be a lot of fun getting the system up again ("why is thin happening i did not change a single thing in two yaer's")

  • Thanks 1
Link to post
Share on other sites

6.2.3_ 918 system USB not recognized

My English is not good, the following are all used translation tools

Mini PC configuration:

cpu i7 4650u

ram 8G

USB boot can be found, but it will appear during installation (error 13). It is normal to install with hard disk, but it does not recognize any USB.

After many tests, it is found that the USB is not recognized, resulting in installation errors.

But install 3617_ 6.1.7, but everything is normal, so I don't think it's a hardware or BIOS setting problem.

Excuse me, what should I do in this situation? Because I like the hardware decoding of 918 very much.

Asking for help

Link to post
Share on other sites

 

9 hours ago, lhscjn said:

6.2.3_ 918 system USB not recognized

My English is not good, the following are all used translation tools

Mini PC configuration:

cpu i7 4650u

ram 8G

USB boot can be found, but it will appear during installation (error 13).

 

the following from your dmesg shows the kernel parameters comming from grub.cfg of the loader and the usb vid/pid is still the default of the loader

[    0.000000] Linux version 4.4.59+ (root@build3) (gcc version 4.9.3 20150311 (prerelease) (crosstool-NG 1.20.0) ) #25426 SMP PREEMPT Tue May 12 04:54:55 CST 2020
[    0.000000] Command line: syno_hdd_powerup_seq=1 HddHotplug=0 syno_hw_version=DS918+ vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet syno_hdd_detect=0 syno_port_thaw=1 root=/dev/md0 sn=1780PDN388713 mac1=0011327B2C73 mac2=0011327B2C74 netif_num=2 vid=0x1908 pid=0x0226
[    0.000000] KERNEL supported cpus:

 

thats from the loaders grub.cfg

set extra_initrd="extra.lzma"
set info="info.txt"

set vid=0x1908
set pid=0x0226
set sn=1780PDN123456
set mac1=001132123456
set rootdev=/dev/md0
set netif_num=1

 

its most often seen error and its explicitly mentioned in the tutorial with the error number 13

 

9 hours ago, lhscjn said:

but it does not recognize any USB.

After many tests, it is found that the USB is not recognized, resulting in installation errors.

yes thats normal,  installing dsm to usb drives is not supported, by default usb drives are only supported as external single drive (no raid)

 

9 hours ago, lhscjn said:

what should I do in this situation?

cenge vid/pid of 1.04b loader, seems you did it right with loader 1.02b if you installed 6.1.7, so redo the 1.04b loader and check twice

Link to post
Share on other sites
4 hours ago, IG-88 said:

 

 

the following from your dmesg shows the kernel parameters comming from grub.cfg of the loader and the usb vid/pid is still the default of the loader


[    0.000000] Linux version 4.4.59+ (root@build3) (gcc version 4.9.3 20150311 (prerelease) (crosstool-NG 1.20.0) ) #25426 SMP PREEMPT Tue May 12 04:54:55 CST 2020
[    0.000000] Command line: syno_hdd_powerup_seq=1 HddHotplug=0 syno_hw_version=DS918+ vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet syno_hdd_detect=0 syno_port_thaw=1 root=/dev/md0 sn=1780PDN388713 mac1=0011327B2C73 mac2=0011327B2C74 netif_num=2 vid=0x1908 pid=0x0226
[    0.000000] KERNEL supported cpus:

 

thats from the loaders grub.cfg


set extra_initrd="extra.lzma"
set info="info.txt"

set vid=0x1908
set pid=0x0226
set sn=1780PDN123456
set mac1=001132123456
set rootdev=/dev/md0
set netif_num=1

 

its most often seen error and its explicitly mentioned in the tutorial with the error number 13

 

yes thats normal,  installing dsm to usb drives is not supported, by default usb drives are only supported as external single drive (no raid)

 

cenge vid/pid of 1.04b loader, seems you did it right with loader 1.02b if you installed 6.1.7, so redo the 1.04b loader and check twice

grub.cfg The parameter in is the default value, because I just do the boot test, because the hard disk does not need to modify the vid and PID, right.

Now I boot through the hard disk, can install the system normally, but no matter how I set it up synoinfo.conf , USB will not appear, this is the problem I want to solve most.

Because my 6T hard disk box can't be mounted.

Now my PC only USB abnormal, other work and hard solution video are very good.

If it can recognize USB hard disk properly, it will be perfect.

Link to post
Share on other sites
17 hours ago, lhscjn said:

st, because the hard disk does not need to modify the vid and PID, right.

no, the vid7pid is not needed for just finding the system in network, if you start installing to disk you will see error 13 that way because of the vid/pid mismatch

 

17 hours ago, lhscjn said:

but no matter how I set it up synoinfo.conf , USB will not appear, this is the problem I want to solve most.

most people i have seen using usb drives as internal drives had problems as it might not be stable (drives often dropping out of raid - hope you have a backup and know hot to manually recover a mdadm and lvm2) and you will loose the tweaked config when updating dsm (usually bigger version with 200-300MB *.pat file where the whole system disk is replaced, including the synoinfo.conf), i've seen both cases

 

using usb as internal is not for 1st time users as its not easy to handle and will easily break

 

you usually configure a overlap of internal drives and usb drives, like leaving usb on its default values and at the same time configuring max disks and internalportcfg to 24 drives, that way usb and internal overlap and you would see the usb drives within the 24 drive range

 

Link to post
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.