DSM 6.2 Loader


Recommended Posts

I can't get the DS918+ loader to detect HDDs on a 88SE9128. It shows up in lspci in slot 1:00:

root@NAS:~# lspci -s 1:00
0000:01:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9128 PCIe SATA 6 Gb/s RAID controller (rev 20)
0000:01:00.1 IDE interface: Marvell Technology Group Ltd. 88SE912x IDE Controller (rev 20)
0001:01:00.0 Non-VGA unclassified device: Marvell Technology Group Ltd. Device 9215 (rev ff)

It also clearly tries to load it during boot but fails with COMRESET errors repeating for a couple minutes.

Spoiler

2018-10-02T19:52:21+02:00 NAS kernel: [    3.906947] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 330)
2018-10-02T19:52:21+02:00 NAS kernel: [    3.906969] DMAR: DRHD: handling fault status reg 3
2018-10-02T19:52:21+02:00 NAS kernel: [    3.907230] DMAR: DMAR:[DMA Read] Request device [01:00.1] fault addr fffe0000
2018-10-02T19:52:21+02:00 NAS kernel: [    3.907230] DMAR:[fault reason 02] Present bit in context entry is clear
2018-10-02T19:52:21+02:00 NAS kernel: [    8.906970] ata5.00: qc timeout (cmd 0xec)
2018-10-02T19:52:21+02:00 NAS kernel: [    8.908961] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x4)
2018-10-02T19:52:21+02:00 NAS kernel: [   14.265024] ata5: link is slow to respond, please be patient (ready=0)
2018-10-02T19:52:21+02:00 NAS kernel: [   18.957081] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [   18.957334] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [   24.313143] ata5: link is slow to respond, please be patient (ready=0)
2018-10-02T19:52:21+02:00 NAS kernel: [   29.005199] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [   29.005451] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [   34.361263] ata5: link is slow to respond, please be patient (ready=0)
2018-10-02T19:52:21+02:00 NAS kernel: [   64.043619] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [   64.043870] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [   64.044147] ata5: limiting SATA link speed to 1.5 Gbps
2018-10-02T19:52:21+02:00 NAS kernel: [   69.093678] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [   69.093927] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [   69.094204] ata5: reset failed, giving up
2018-10-02T19:52:21+02:00 NAS kernel: [   69.094417] ata5: get error flags 0x2
2018-10-02T19:52:21+02:00 NAS kernel: [   69.095685] ata5: get error flags 0x2
2018-10-02T19:52:21+02:00 NAS kernel: [   69.097680] ata5: do detect tries 1
2018-10-02T19:52:21+02:00 NAS kernel: [   69.097890] ata5: device plugged sstatus 0x123
2018-10-02T19:52:21+02:00 NAS kernel: [   69.097894] ata5: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xf t1
2018-10-02T19:52:21+02:00 NAS kernel: [   69.098235] ata5: irq_stat 0x00000000, PHY RDY changed
2018-10-02T19:52:21+02:00 NAS kernel: [   69.098509] ata5: hard resetting link
2018-10-02T19:52:21+02:00 NAS kernel: [   74.871748] ata5: link is slow to respond, please be patient (ready=0)
2018-10-02T19:52:21+02:00 NAS kernel: [   79.104797] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [   79.105047] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [   79.105324] ata5: hard resetting link
2018-10-02T19:52:21+02:00 NAS kernel: [   84.878866] ata5: link is slow to respond, please be patient (ready=0)
2018-10-02T19:52:21+02:00 NAS kernel: [   89.111916] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [   89.112166] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [   89.112442] ata5: hard resetting link
2018-10-02T19:52:21+02:00 NAS kernel: [   94.885985] ata5: link is slow to respond, please be patient (ready=0)
2018-10-02T19:52:21+02:00 NAS kernel: [  124.160335] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [  124.160586] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [  124.160863] ata5: limiting SATA link speed to 1.5 Gbps
2018-10-02T19:52:21+02:00 NAS kernel: [  124.160864] ata5: hard resetting link
2018-10-02T19:52:21+02:00 NAS kernel: [  129.169395] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [  129.169645] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [  129.169921] ata5: reset failed, giving up
2018-10-02T19:52:21+02:00 NAS kernel: [  129.170134] ata5: get error flags 0x2
2018-10-02T19:52:21+02:00 NAS kernel: [  129.171395] ata5: do deep tries 1
2018-10-02T19:52:21+02:00 NAS kernel: [  129.171592] ata5: not support deep sleep, do one more detect try
2018-10-02T19:52:21+02:00 NAS kernel: [  129.171909] ata5: device plugged sstatus 0x123
2018-10-02T19:52:21+02:00 NAS kernel: [  129.171913] ata5: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xf t1
2018-10-02T19:52:21+02:00 NAS kernel: [  129.172254] ata5: irq_stat 0x00000000, PHY RDY changed
2018-10-02T19:52:21+02:00 NAS kernel: [  129.172528] ata5: hard resetting link
2018-10-02T19:52:21+02:00 NAS kernel: [  134.946464] ata5: link is slow to respond, please be patient (ready=0)
2018-10-02T19:52:21+02:00 NAS kernel: [  139.179514] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [  139.179765] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [  139.180041] ata5: hard resetting link
2018-10-02T19:52:21+02:00 NAS kernel: [  144.953583] ata5: link is slow to respond, please be patient (ready=0)
2018-10-02T19:52:21+02:00 NAS kernel: [  149.186634] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [  149.186884] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [  149.187159] ata5: hard resetting link
2018-10-02T19:52:21+02:00 NAS kernel: [  154.960703] ata5: link is slow to respond, please be patient (ready=0)
2018-10-02T19:52:21+02:00 NAS kernel: [  184.235052] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [  184.235303] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [  184.235579] ata5: limiting SATA link speed to 1.5 Gbps
2018-10-02T19:52:21+02:00 NAS kernel: [  184.235580] ata5: hard resetting link
2018-10-02T19:52:21+02:00 NAS kernel: [  189.244112] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [  189.244362] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [  189.244639] ata5: reset failed, giving up
2018-10-02T19:52:21+02:00 NAS kernel: [  189.244852] ata5: get error flags 0x2
2018-10-02T19:52:21+02:00 NAS kernel: [  189.246112] ata5: ==== port retry failed ====

Relevant grub config:

set common_args_918='syno_hdd_powerup_seq=1 HddHotplug=1 syno_hw_version=DS918+ vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet syno_hdd_detect=0 syno_port_thaw=1'

set sata_args='sata_uid=1 sata_pcislot=1:00 synoboot_satadom=1 DiskIdxMap=0005 SataPortMap=44'

The disk is detected with DS3615xs. Custom extra.lzma makes no difference, the driver loads just fine with the stock one. I will investigate further since I did somehow manage to get the installer to detect a fresh disk with 918+ but I'm still trying to replicate it.

Link to post
Share on other sites
On 10/2/2018 at 8:15 PM, AndreyATGB said:

I can't get the DS918+ loader to detect HDDs on a 88SE9128. It shows up in lspci in slot 1:00:


root@NAS:~# lspci -s 1:00
0000:01:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9128 PCIe SATA 6 Gb/s RAID controller (rev 20)
0000:01:00.1 IDE interface: Marvell Technology Group Ltd. 88SE912x IDE Controller (rev 20)
0001:01:00.0 Non-VGA unclassified device: Marvell Technology Group Ltd. Device 9215 (rev ff)

It also clearly tries to load it during boot but fails with COMRESET errors repeating for a couple minutes.

  Log (Hide contents)

2018-10-02T19:52:21+02:00 NAS kernel: [    3.906947] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 330)
2018-10-02T19:52:21+02:00 NAS kernel: [    3.906969] DMAR: DRHD: handling fault status reg 3
2018-10-02T19:52:21+02:00 NAS kernel: [    3.907230] DMAR: DMAR:[DMA Read] Request device [01:00.1] fault addr fffe0000
2018-10-02T19:52:21+02:00 NAS kernel: [    3.907230] DMAR:[fault reason 02] Present bit in context entry is clear
2018-10-02T19:52:21+02:00 NAS kernel: [    8.906970] ata5.00: qc timeout (cmd 0xec)
2018-10-02T19:52:21+02:00 NAS kernel: [    8.908961] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x4)
2018-10-02T19:52:21+02:00 NAS kernel: [   14.265024] ata5: link is slow to respond, please be patient (ready=0)
2018-10-02T19:52:21+02:00 NAS kernel: [   18.957081] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [   18.957334] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [   24.313143] ata5: link is slow to respond, please be patient (ready=0)
2018-10-02T19:52:21+02:00 NAS kernel: [   29.005199] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [   29.005451] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [   34.361263] ata5: link is slow to respond, please be patient (ready=0)
2018-10-02T19:52:21+02:00 NAS kernel: [   64.043619] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [   64.043870] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [   64.044147] ata5: limiting SATA link speed to 1.5 Gbps
2018-10-02T19:52:21+02:00 NAS kernel: [   69.093678] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [   69.093927] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [   69.094204] ata5: reset failed, giving up
2018-10-02T19:52:21+02:00 NAS kernel: [   69.094417] ata5: get error flags 0x2
2018-10-02T19:52:21+02:00 NAS kernel: [   69.095685] ata5: get error flags 0x2
2018-10-02T19:52:21+02:00 NAS kernel: [   69.097680] ata5: do detect tries 1
2018-10-02T19:52:21+02:00 NAS kernel: [   69.097890] ata5: device plugged sstatus 0x123
2018-10-02T19:52:21+02:00 NAS kernel: [   69.097894] ata5: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xf t1
2018-10-02T19:52:21+02:00 NAS kernel: [   69.098235] ata5: irq_stat 0x00000000, PHY RDY changed
2018-10-02T19:52:21+02:00 NAS kernel: [   69.098509] ata5: hard resetting link
2018-10-02T19:52:21+02:00 NAS kernel: [   74.871748] ata5: link is slow to respond, please be patient (ready=0)
2018-10-02T19:52:21+02:00 NAS kernel: [   79.104797] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [   79.105047] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [   79.105324] ata5: hard resetting link
2018-10-02T19:52:21+02:00 NAS kernel: [   84.878866] ata5: link is slow to respond, please be patient (ready=0)
2018-10-02T19:52:21+02:00 NAS kernel: [   89.111916] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [   89.112166] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [   89.112442] ata5: hard resetting link
2018-10-02T19:52:21+02:00 NAS kernel: [   94.885985] ata5: link is slow to respond, please be patient (ready=0)
2018-10-02T19:52:21+02:00 NAS kernel: [  124.160335] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [  124.160586] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [  124.160863] ata5: limiting SATA link speed to 1.5 Gbps
2018-10-02T19:52:21+02:00 NAS kernel: [  124.160864] ata5: hard resetting link
2018-10-02T19:52:21+02:00 NAS kernel: [  129.169395] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [  129.169645] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [  129.169921] ata5: reset failed, giving up
2018-10-02T19:52:21+02:00 NAS kernel: [  129.170134] ata5: get error flags 0x2
2018-10-02T19:52:21+02:00 NAS kernel: [  129.171395] ata5: do deep tries 1
2018-10-02T19:52:21+02:00 NAS kernel: [  129.171592] ata5: not support deep sleep, do one more detect try
2018-10-02T19:52:21+02:00 NAS kernel: [  129.171909] ata5: device plugged sstatus 0x123
2018-10-02T19:52:21+02:00 NAS kernel: [  129.171913] ata5: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xf t1
2018-10-02T19:52:21+02:00 NAS kernel: [  129.172254] ata5: irq_stat 0x00000000, PHY RDY changed
2018-10-02T19:52:21+02:00 NAS kernel: [  129.172528] ata5: hard resetting link
2018-10-02T19:52:21+02:00 NAS kernel: [  134.946464] ata5: link is slow to respond, please be patient (ready=0)
2018-10-02T19:52:21+02:00 NAS kernel: [  139.179514] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [  139.179765] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [  139.180041] ata5: hard resetting link
2018-10-02T19:52:21+02:00 NAS kernel: [  144.953583] ata5: link is slow to respond, please be patient (ready=0)
2018-10-02T19:52:21+02:00 NAS kernel: [  149.186634] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [  149.186884] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [  149.187159] ata5: hard resetting link
2018-10-02T19:52:21+02:00 NAS kernel: [  154.960703] ata5: link is slow to respond, please be patient (ready=0)
2018-10-02T19:52:21+02:00 NAS kernel: [  184.235052] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [  184.235303] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [  184.235579] ata5: limiting SATA link speed to 1.5 Gbps
2018-10-02T19:52:21+02:00 NAS kernel: [  184.235580] ata5: hard resetting link
2018-10-02T19:52:21+02:00 NAS kernel: [  189.244112] ata5: COMRESET failed (errno=-16)
2018-10-02T19:52:21+02:00 NAS kernel: [  189.244362] ata5: COMRESET fail, set COMRESET fail flag
2018-10-02T19:52:21+02:00 NAS kernel: [  189.244639] ata5: reset failed, giving up
2018-10-02T19:52:21+02:00 NAS kernel: [  189.244852] ata5: get error flags 0x2
2018-10-02T19:52:21+02:00 NAS kernel: [  189.246112] ata5: ==== port retry failed ====

Relevant grub config:


set common_args_918='syno_hdd_powerup_seq=1 HddHotplug=1 syno_hw_version=DS918+ vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet syno_hdd_detect=0 syno_port_thaw=1'

set sata_args='sata_uid=1 sata_pcislot=1:00 synoboot_satadom=1 DiskIdxMap=0005 SataPortMap=44'

The disk is detected with DS3615xs. Custom extra.lzma makes no difference, the driver loads just fine with the stock one. I will investigate further since I did somehow manage to get the installer to detect a fresh disk with 918+ but I'm still trying to replicate it.

you dont mention the brand of the add-on card/controller, but check that raid is disabled ( set IT or JBOD mode) and the ide ports are too. Not an expert but I think the drivers/modules in the 3615 image are different to the 918, maybe the 918 version behaves differently. Also, try setting the sataportmap to default.

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

Silly question maybe? 

 

Is there any issue with updating 6.2?

Are we only doing the important updates? 

Which 6.2 do we start with and stop with? 

personally I am sticking with 6.1 at the moment, imho 6.2 is still late beta, as this thread shows. I'm testing it myself, but wont be upgrading my live systems yet

Link to post
Share on other sites
19 hours ago, sbv3000 said:

you dont mention the brand of the add-on card/controller, but check that raid is disabled ( set IT or JBOD mode) and the ide ports are too. Not an expert but I think the drivers/modules in the 3615 image are different to the 918, maybe the 918 version behaves differently. Also, try setting the sataportmap to default.

I don’t remember the brand, I think it’s IOcrest or something. I finally managed to enter its BIOS but there’s nothing to configure besides RAID (which was disabled anyway). It only shows the one sata disk I have installed, it’s marked as AHCI Mode. It doesn’t show the empty slots or any way to disable the IDE port. It’s probably some weird interaction with the DS918+ loader considering that it is being detected but for some reason just doesn’t work.

With the DS3615 loader the disk showed exactly as it would if I had it plugged in directly the motherboard. I’ll just switch to DS3615 when I actually need to use the extra ports. It could be that the IDE port is the problem with the newer kernel that DS918+ uses, I don’t care enough about hardware acceleration to get another card right now. 

Link to post
Share on other sites

Upgraded my HP Microserver G8 from 6.1.5 to 6.2 but know I'm not able to login anymore to the Web GUI - it stucks at "Loading".

 

When I logon via SSH and type in "synobootseq --set-boot-done" and "synobootseq --is-ready" the login process works but really weird is, that few seconds later the internet connection is totally lost so I cant dig deeper into the problem.

 

Any ideas to get back the web gui?

Link to post
Share on other sites

Thanks Jun!

 

Thecus N7510: Intel Atom D2701, 4GB, RAID6 (7x WD 3TB Red), 2x Intel 1GB LAN, Fans working with lm-sensors, LCD and LEDs not working.

 

1.03b installer DS 6.2-23739 (DS3615xs): SUCCESSFUL

UPGRADE DS6.2-23739 -->  DS6.2-23739 Update 2: SUCCESS

 

Edited by Bogey
Link to post
Share on other sites
1 hour ago, CrazyCreator said:

I think DSM 6.2 (last version) is not running actually with the Loader 1.03b

 

I've uploaded DSM_DS3615xs_23739.pat on migration from 6.1 to 6.2.

Nearly everything is fine except the Web GUI, I'm able to reach my files and connect via ssh.

Link to post
Share on other sites
2 hours ago, socra said:

Since we all know that 6.2.1 is currently not working with the 1.0.3b loader:
https://xpenology.com/forum/announcement/17-dsm-621-23824-warning/

Is this something that is "fixable" or has Synology delivered a serious blow to the xpenology project by modifying some kernel options?
 

It does actually work. It depends on your hardware. It seems Realtek NICs don’t work for example.

  • Thanks 1
Link to post
Share on other sites

Hello, I have the problem that after updating my server is no longer achievable. Unfortunately, I saw the message too late and updated it beforehand. Now the server is down. I use HP Microserver Gen8 Loader: 1.03b - ds3617_6.2 Can someone help me how to get it all going now? or undo the update so that everything runs again?

Link to post
Share on other sites

Hi

 

Posted this in the general questions of post installation but perhaps it is better here:

 

I've got the latest boot image and DSM running on my Supermicro X8DTL-iF setup.  I'm trying to trim my power consumption and have decided to gut my R710's of their memory to support the all in one approach.  I had 32GB of DDR3 RDIMMs installed in a 2 x 16GB config, with a single spare memory slot, this worked well and had no issues.  I took another matching 16GB stick and put it in the spare slot but upon rebooting, DSM is still only showing 32GB of Ram which is confirmed using TOP in the CLI.  Does the 3615xs image max out at 32GB like the actual proper unit; I wouldn't have thought so but I've never tried to take it further.

 

Anyone got any thoughts?

 

Thanks,

 

Chris

Link to post
Share on other sites
9 hours ago, phpcode said:

Hello, I have the problem that after updating my server is no longer achievable. Unfortunately, I saw the message too late and updated it beforehand. Now the server is down. I use HP Microserver Gen8 Loader: 1.03b - ds3617_6.2 Can someone help me how to get it all going now? or undo the update so that everything runs again?

 

I dunno, maybe start all over again with installing the previous pat file.

 

Format your drives and start from scratch (you will lose the data, of course should always have a backup).  Don't update to this latest firmware, to get your box going again.

Edited by rgarjr
Link to post
Share on other sites

I see there are successful 6.2.1 updates in the  updates reporting thread but unfortunately not many post their hardware configuration and its not required to fill that info out so it doesn't help the community much. Is there a list of what the "officially supported" kernel hardware is? So far it looks like Intel chipset NICs "all?"

Edited by Black6spdZ
Link to post
Share on other sites

I was using this on my old laptop. After Latest update unable to reach the machine!
Hardware XPS M1530

Original Network card damaged on a lightning!
Now using PCIE Express card.

6GB RAM, 250GB Samsung Evo SSD, Intel Core2 Duo T9300 @ 2.50GHz
EC1000S Gigabit Ethernet Network Adapter Card (Chipset IDRealtek - RTL8111DL)
I reinstalled it with older version on DSM and now working fine.


But i cannot update to latest version :( Someone said Synology removed Realtek support from Kernel.

I cannot run FreeNAS (it required 8GB RAM)
Any other alternative? Yes i can run this old version for ever! But.. 

Link to post
Share on other sites
29 minutes ago, Vishnu said:

I was using this on my old laptop. After Latest update unable to reach the machine!
Hardware XPS M1530

Original Network card damaged on a lightning!
Now using PCIE Express card.

6GB RAM, 250GB Samsung Evo SSD, Intel Core2 Duo T9300 @ 2.50GHz
EC1000S Gigabit Ethernet Network Adapter Card (Chipset IDRealtek - RTL8111DL)
I reinstalled it with older version on DSM and now working fine.


But i cannot update to latest version :( Someone said Synology removed Realtek support from Kernel.

I cannot run FreeNAS (it required 8GB RAM)
Any other alternative? Yes i can run this old version for ever! But.. 

 

6.2 isn't very old at all, I wouldn't worry much.. I'm sure it's being hashed out as we type this.

  • Thanks 1
Link to post
Share on other sites
On 10/7/2018 at 4:30 PM, Bogey said:

Thanks Jun!

 

Thecus N7510: Intel Atom D2701, 4GB, RAID6 (7x WD 3TB Red), 2x Intel 1GB LAN, Fans working with lm-sensors, LCD and LEDs not working.

 

1.03b installer DS 6.2-23739 (DS3615xs): SUCCESSFUL

UPGRADE DS6.2-23739 -->  DS6.2-23739 Update 2: SUCCESS

 

Upgrade to 6.2.1 went like a charm :)

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.