Cubitus

Hi soulcola, Thanks for your answer. What is strange is that the same configuration works perfectly with Jun's loader and DSM6.2.3 : my disks are respectively identified as 3 (SSD), 4 & 6 (linux RAID). I will postpone the upgrade as I cannot add any PCI card to my configuration, maybe this will be corrected later .

Hi, Another unsuccessful try today My mother board gets 4 SATA ports but the chipset allows 6. The 2 1st ones are not connectable (maybe port 1 = M2 interface ?) and the disks can be connected as SATA 3 / 4 / 5 / 6 the DMESG command shows following when activating the SATA ports [ 0.944500] ata1: DUMMY [ 0.944787] ata2: SATA max UDMA/133 abar m2048@0xdf14b000 port 0xdf14b180 irq 122 [ 0.945462] ata3: SATA max UDMA/133 abar m2048@0xdf14b000 port 0xdf14b200 irq 122 [ 0.946193] ata4: SATA max UDMA/133 abar m2048@0xdf14b000 port 0xdf14b280 irq 122 [ 0.946994] ata5: SATA max UDMA/133 abar m2048@0xdf14b000 port 0xdf14b300 irq 122 [ 0.947625] ata6: SATA max UDMA/133 abar m2048@0xdf14b000 port 0xdf14b380 irq 122 [ 0.948338] ata1: send port disabled event [ 0.948780] ata1: Disk is present for send port disabled event [ 1.253683] ata2: SATA link down (SStatus 4 SControl 300) [ 1.254147] ata2: No present pin info for SATA link down event [ 1.560675] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) .... (SATA 3 is the only disk connected to the mother board and rest of activation is OK) Synology tool gives an error on disk (1) -> corresponding to the dummy one. Could it be the reason why it cannot go further ? How to overpass this ? (the system is working fine with DSM 6.2.1 / Jun's loader) Thanks for helping

I have made another try without the DSM 6.2.3 disks, only an empty SSD : no more success below is what's written in /var/log/messages when I try to activate the system from SynologyAssistant Any idea of what's causing this ? Jan 1 00:02:25 getty[5586]: tcgetattr: Input/output error^M Jan 1 00:02:35 getty[5587]: tcgetattr: Input/output error^M Jan 25 15:00:02 getty[5627]: tcgetattr: Input/output error^M Jan 25 15:00:12 getty[5631]: tcgetattr: Input/output error^M Jan 25 15:00:19 synoupgrade: synoupgrade.c:267 Failed to get root partition version Jan 25 15:00:19 synoupgrade: synoupgrade.c:267 Failed to get root partition version Jan 25 15:00:19 synoupgrade: autocleanup/mount.c:19 run '/usr/bin/mount /dev/md0 /_disk' Jan 25 15:00:19 synoupgrade: autocleanup/mount.c:30 mount's exit status is non-zero, 255 Jan 25 15:00:19 synoupgrade: autocleanup/mount.c:72 mount point creation failed, so skip unmounting Jan 25 15:00:19 synoupgrade: autocleanup/directory.c:38 remove directory /_disk, result is 0 Jan 25 15:00:19 synoupgrade: synoupgrade.c:245 unable to get dsm version from disk device Jan 25 15:00:19 synoupgrade: synoupgrade.c:308 unable to append query string of disk dsm version Jan 25 15:00:19 synoupgrade: synoupgrade.c:267 Failed to get root partition version Jan 25 15:00:20 synoupgrade: partition_check_layout.c:173 sdc: dont contain partition [1] Jan 25 15:00:20 synoupgrade: partition_check_layout.c:173 sdc: dont contain partition [2] Jan 25 15:00:20 synoupgrade: ninstaller.c:678 Dev: sdc, DiskPath: /dev/sdc, Partition version: [not syno partition] Jan 25 15:00:20 synoupgrade: ninstaller.c:1146 SYSTEM_NOT_INSTALLED: Raid but md0 or md1 not exist Jan 25 15:00:20 synoupgrade: ninstaller.c:1214 SYSTEM_NOT_INSTALLED: Not SynoParitition and Not Recoverable Jan 25 15:00:20 synoupgrade: ninstaller.c:1114(FillUpgradeVolumeInfo): gszUpgradeVolDev = /dev/md0 Jan 25 15:00:20 synoupgrade: ninstaller.c:1115(FillUpgradeVolumeInfo): gszUpgradeVolMnt = /tmpData Jan 25 15:00:20 synoupgrade: ninstaller.c:1223 gblSupportRaid: 1, gSysStatus: 3, gblCreateDataVol: 0, gblSystemRecoverable: 0 Jan 25 15:00:22 getty[5716]: tcgetattr: Input/output error^M

@adamadam Do you mean I boot the system onto 'Hirens' and use it to remove partitions from the disks ? But that will delete my current system whereas I want to upgrade it, unless you refer to other disks ?

Hi again, Some more log from 'messages.log' : seems there is an error with md0 & md1 file systems. So what shall be done ? Jan 25 09:47:30 synoupgrade: autocleanup/mount.c:19 run '/usr/bin/mount /dev/md0 /_disk' Jan 25 09:47:30 kernel: [ 2401.714377] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:30 kernel: [ 2401.715176] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:30 synoupgrade: autocleanup/mount.c:27 mount's exit status is zero Jan 25 09:47:30 synoupgrade: get_disk_dsm_version.c:99 try reading disk dsm's version at file '/_disk//etc.defaults/VERSION' of key 'buildnumber' Jan 25 09:47:30 synoupgrade: autocleanup/mount.c:44 run '/usr/bin/umount -l /_disk' Jan 25 09:47:30 kernel: [ 2401.753718] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) Jan 25 09:47:30 synoupgrade: autocleanup/mount.c:54 umount's exit status is zero Jan 25 09:47:30 synoupgrade: autocleanup/directory.c:38 remove directory /_disk, result is 0 Jan 25 09:47:31 synoupgrade: ninstaller.c:683 Dev: sdc, DiskPath: /dev/sdc, Partition version: 8 Jan 25 09:47:31 synoupgrade: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot Jan 25 09:47:31 kernel: [ 2402.570349] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:31 kernel: [ 2402.571156] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:31 kernel: [ 2402.628869] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) Jan 25 09:47:31 synoupgrade: ninstaller.c:152 umount partition /tmpRoot Jan 25 09:47:31 synoupgrade: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot Jan 25 09:47:31 kernel: [ 2402.945713] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:31 kernel: [ 2402.946507] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:31 kernel: [ 2402.955562] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) Jan 25 09:47:31 synoupgrade: ninstaller.c:152 umount partition /tmpRoot Jan 25 09:47:31 synoupgrade: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot Jan 25 09:47:31 kernel: [ 2402.967834] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:31 kernel: [ 2402.968587] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (2c0) Jan 25 09:47:31 kernel: [ 2402.977562] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) Jan 25 09:47:31 synoupgrade: ninstaller.c:494 fail to get admin port from /tmpRoot/etc/synoinfo.conf... try another way Jan 25 09:47:31 synoupgrade: ninstaller.c:847 unique not match Jan 25 09:47:31 synoupgrade: ninstaller.c:1207 SYSTEM_NORMAL, [Recoverable=0] Jan 25 09:47:31 synoupgrade: ninstaller.c:152 umount partition /tmpRoot Jan 25 09:47:31 synoupgrade: ninstaller.c:1114(FillUpgradeVolumeInfo): gszUpgradeVolDev = /dev/md0 Jan 25 09:47:31 synoupgrade: ninstaller.c:1115(FillUpgradeVolumeInfo): gszUpgradeVolMnt = /tmpData Jan 25 09:47:31 synoupgrade: ninstaller.c:1223 gblSupportRaid: 1, gSysStatus: 1, gblCreateDataVol: 0, gblSystemRecoverable: 0

Hi everybody This morning I tried again upgrading my DSM (DS918 + Jun loader + DSM6.2.3 upd2) to DSM7.0.1 As it was not working yesterday with DS918+ conf I restarted from scratch with DS3615xs model. But results is the same : the system boots on the usb dongle and states disks errors when trying to upgrade. Below are the trace I could made accessing the system via telnet. If anyone could help ! New USB key balena etcher tinycore img from pocopico github Prepare the user_config : sudo ./rploader.sh update now sudo ./rploader.sh identifyusb now sudo ./rploader.sh satamap now SataPortMap=6 DiskIdxMap=00 sudo ./rploader.sh serialgen DS3615xs now sudo ./rploader.sh ext bromolow-7.0.1-42218 add https://raw.githubuser (don't know if strictly necessary ?) sudo ./rploader.sh build bromolow-7.0.1-42218 -- BOOT on the new key with existing disks -- http://192.168.1.13:5000/webman/start_telnet.cgi (on web browser) {"success": true} -- START a putty session -- DiskStation login: root Synology strongly advises you not to run commands as the root user, who has the highest privileges on the system. Doing so may cause major damages to the system. Please note that if you choose to proceed, all consequences are at your own risk. -- CHECK for disks -- DiskStation> fdisk -l Disk /dev/sde: 932 GB, 1000204886016 bytes, 1953525168 sectors 121601 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sde1 0,32,33 310,37,47 2048 4982527 4980480 2431M fd Linux raid autodetect /dev/sde2 310,37,48 571,58,63 4982528 9176831 4194304 2048M fd Linux raid autodetect /dev/sde3 587,111,37 1023,254,63 9437184 1953292287 1943855104 926G fd Linux raid autodetect Disk /dev/sdf: 932 GB, 1000204886016 bytes, 1953525168 sectors 121601 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sdf1 0,32,33 310,37,47 2048 4982527 4980480 2431M fd Linux raid autodetect /dev/sdf2 310,37,48 571,58,63 4982528 9176831 4194304 2048M fd Linux raid autodetect /dev/sdf3 587,111,37 1023,254,63 9437184 1953292287 1943855104 926G fd Linux raid autodetect Disk /dev/sdc: 233 GB, 250059350016 bytes, 488397168 sectors 30401 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sdc1 0,32,33 310,37,47 2048 4982527 4980480 2431M fd Linux raid autodetect /dev/sdc2 310,37,48 571,58,63 4982528 9176831 4194304 2048M fd Linux raid autodetect /dev/sdc3 587,111,37 1023,254,63 9437184 488192351 478755168 228G fd Linux raid autodetect Disk /dev/synoboot: 15 GB, 15833497600 bytes, 30924800 sectors 15100 cylinders, 64 heads, 32 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/synoboot1 * 0,32,33 6,62,56 2048 100351 98304 48.0M 83 Linux /dev/synoboot2 6,62,57 15,205,62 100352 253951 153600 75.0M 83 Linux /dev/synoboot3 15,205,63 130,138,8 253952 2097151 1843200 900M 83 Linux Disk /dev/md0: 2431 MB, 2549940224 bytes, 4980352 sectors 622544 cylinders, 2 heads, 4 sectors/track Units: sectors of 1 * 512 = 512 bytes Disk /dev/md0 doesn't contain a valid partition table Disk /dev/md1: 2047 MB, 2147418112 bytes, 4194176 sectors 524272 cylinders, 2 heads, 4 sectors/track Units: sectors of 1 * 512 = 512 bytes Disk /dev/md1 doesn't contain a valid partition table -- HERE IS THE CONTENT OF LOG FILE -- DiskStat DiskStation> cat linuxrc.syno.log START /linuxrc.syno.impl Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module ehci-hcd ... [ OK ] :: Loading module ehci-pci ... [ OK ] :: Loading module uhci-hcd ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Loading kmod #0 "e1000e.ko" for pocopico.e1000e (args: ) Loading kmod #0 "mpt2sas.ko" for pocopico.mpt2sas (args: ) Checking if kmods for thethorgroup.virtio should run using check-virtio.sh script Checking for VirtIO *No* VirtIO hypervisor detected NOT loading kmods for thethorgroup.virtio :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-e1000e.sh" for pocopico.e1000e->on_boot Loading module e1000e -> Module e1000e loaded succesfully Ran "check-e1000e.sh" for pocopico.e1000e->on_boot - exit=0 Running "check-mpt2sas.sh" for pocopico.mpt2sas->on_boot Loading module mpt2sas -> Module mpt2sas loaded succesfully Ran "check-mpt2sas.sh" for pocopico.mpt2sas->on_boot - exit=0 Running "boot-wait.sh" for thethorgroup.boot-wait->on_boot Still waiting for boot device (waited 1 of 30 seconds) Still waiting for boot device (waited 2 of 30 seconds) Still waiting for boot device (waited 3 of 30 seconds) Still waiting for boot device (waited 4 of 30 seconds) Confirmed a valid-looking /dev/synoboot device Ran "boot-wait.sh" for thethorgroup.boot-wait->on_boot - exit=0 :: Executing "on_boot" custom scripts ... [ OK ] Extensions processed Insert net driver(Mindspeed only)... Starting /usr/syno/bin/synocfgen... /usr/syno/bin/synocfgen returns 0 All disk ready or timeout execeed Assemble args: -u fc4d7be4:b0512f9f:3017a5a8:c86610be /dev/sdc1 /dev/sde1 /dev/sdf1 mdadm: /dev/md0 has been started with 3 drives (out of 16). Partition Version=8 /sbin/e2fsck exists, checking /dev/md0... e2fsck 1.44.1 (24-Mar-2018) /sbin/e2fsck -yvf returns 0 Mounting /dev/md0 /tmpRoot ------------upgrade Begin upgrade procedure Mount data partition: /dev/md0 -> /tmpData No upgrade file exists End upgrade procedure ============upgrade ------------bootup-smallupdate Try bootup smallupdate Total: 22 packages {"action":"stop","id":"MariaDB10","status":"skip"} {"action":"stop","id":"FileStation","status":"begin"} {"action":"stop","id":"FileStation","status":"end"} {"action":"stop","id":"SynologyMoments","status":"begin"} {"action":"stop","id":"SynologyDrive","status":"begin"} {"action":"stop","id":"SynoFinder","status":"begin"} {"action":"stop","id":"SynoFinder","status":"end"} {"action":"stop","id":"Virtualization","status":"begin"} {"action":"stop","id":"ReplicationService","status":"begin"} {"action":"stop","id":"ReplicationService","status":"end"} {"action":"stop","id":"SynologyApplicationService","status":"begin"} {"action":"stop","id":"Docker","status":"begin"} {"action":"stop","id":"phpMyAdmin","status":"begin"} {"action":"stop","id":"PHP7.3","status":"begin"} {"action":"stop","id":"MediaServer","status":"begin"} {"action":"stop","id":"Node.js_v12","status":"begin"} {"action":"stop","id":"syncthing.net","status":"begin"} {"action":"stop","id":"MariaDB","status":"begin"} {"action":"stop","id":"DownloadStation","status":"begin"} {"action":"stop","id":"VideoStation","status":"begin"} {"action":"stop","id":"AudioStation","status":"begin"} {"action":"stop","id":"OAuthService","status":"begin"} {"action":"stop","id":"OAuthService","status":"end"} {"action":"stop","id":"LogCenter","status":"begin"} {"action":"stop","id":"HyperBackup","status":"begin"} {"action":"stop","id":"WebStation","status":"begin"} Failed to stop all packages 150 BOOTUP_UPGRADE_SMALLUPDATE No new update to download Fail to bootup smallupdate Failed to synoupgrade --bootup-smallupdate [255] Exit on error [6] bootup-smallupdate failed... Tue Jan 25 09:07:31 UTC 2022 /dev/md0 /tmpRoot ext4 rw,relatime,journal_checksum,data=ordered 0 0 none /sys/kernel/debug debugfs rw,relatime 0 0ion>

@soulcola No solution so far. That's becoming boring....

Dear all, I have tried out the RedPill loader along with this tinycore environement and I am getting stuck just after rebooting : The Synology assistant detects disks error and stops the SATA controllers : My initial machine is DS918+ / DSM6.2.3 update 3 with jun's loader I am trying to upgrade to DSM7.0.1 I think I have done correctly the user_config operations (sataportmap = 6 / diskidxmap = 00 and I am using the previous mac address and serial) But rploader.sh sends a warning during the build : ------------------------------------------------------------------------------------------------ It looks that you will need the following modules : Found SATA Controller : pciid 8086d0000a282 Required Extension : No matching extension Which corresponds to the SATA / AHCI controller ; effectively there are none declared in the "modules.alias.json" file corresponding to 8086 / A282. I suspect I should put an entry here, but which one ? The HW is a ASROCK B365 M mothe'rboard with intel core i3. Many thanks for your help and congrats to pocopico for this nice job. Cubitus.

@BearCat Thank you for your advices ; I took loader version 1.02b which is working fine with the 3615xs config in 6.1-15047. I have another question : is there any root account on Synology servers ? I have been asked for 'admin' acount and password but nothing for root itself.

Hi , Thank you all for this realy interesting NAS system. I am looking for installing xpenology on an old PC that is now dedicated to file server but the version I tried : loader 1.04b / DS918+ is not working at all : the PC is not found neither by the assistant nor through find.synology.com. The PC is an old Packard Bell Imedia from 2009 with 6GB RAM, Pentium QuadCore 2.3GHz, 2 SATA ports (3GB) and an additional 2 SATA PCIE board able to do RAID 0 or RAID 1. It is working Linux (Debian 5) without problem. The loader seems to work correctly : there is the boot message for further action on find.synology.com but that's all : no way to have the PC found. I have modified the grub.cfg file to match the PID/VID of my USB stick I have also tried several different SN Now I wonder if I took the right loader version ? Could anybody instruct me on how to go further ? Many rhanks in advance; C.