Recommended Posts

34 minutes ago, youngc29 said:

after this it dropped off and was not able to see it again. I really thought I had it fixed :( I also looked at the VERSION file in etc and etc.defaults. I'm at a total loss now if anyone has any hints or clues that would be great?

 

i edited a little with a comment what could happen if you had a 6.2.1/6.2.2 dsm before, is that case the often used extended special made (for 6.2.2) extra/extra2 will often prevent the system from loader drivers, it would also need extra/extra2 for 6.2.3 in that case

in general its best to have a serial cable (null-modem-cable) to monitor the console with putty in serial mode, you would see drivers loading or crashing and even if network drivers failed you would be able to login local on the console after boot and check with "dmesg"

 

if the version files in /etc and /etc.defaults are showing 6.2.3 it should be ok (i guess the one in /etc would be overwritten on next boot so the one in /etc.defaults is the important one), if both VERSION files are 6.2.3 then look for the extra.lzma on the loader and replace it with either jun#s original or my newer one made for 6.2.3

 

Link to post
Share on other sites

Gen8 does not have a db9 serial port for use with a null modem cable. It only has the rj45 ilo port.

 

@IG-88I used VSP from ILO and get the following:

 

Intro:                                                                          This mod is brought to you by Jun <haijun.dev@gmail.com>. You can contact me to discuss technical details, but general installation questions should go through the xpenology forum or other communities.                                                                                                                       Happy hacking.                                                                  S

                                                                                 creen will stop updating shortly, please open http://find.synology.com to      continue.                                                                       patching file etc/rc
Hunk #1 succeeded at 184 (offset 13 lines).
patching file etc/synoinfo.conf
Hunk #1 FAILED at 291.
1 out of 1 hunk FAILED -- saving rejects to file etc/synoinfo.conf.rej
patching file linuxrc.syno
Hunk #1 FAILED at 39.
Hunk #2 succeeded at 131 (offset 32 lines).
Hunk #3 succeeded at 694 (offset 179 lines).
1 out of 3 hunks FAILED -- saving rejects to file linuxrc.syno.rej              patching file usr/sbin/init.post                                                cat: can't open '/etc/synoinfo_override.conf': No such file or directory        START /linuxrc.syno                                                             Insert basic USB modules...                                                     :: Loading module usb-common ... [  OK  ]                                       :: Loading module usbcore ... [  OK  ]                                          :: Loading module ehci-hcd ... [  OK  ]                                         :: Loading module ehci-pci[    3.745237] BUG: unable to handle kernel NULL pointer dereference at 00000000000000b8                                              [    3.783249] IP: [<ffffffff8129756a>] pci_bus_read_config_word+0x4a/0x90      [    3.815680] PGD 27aef5067 PUD 27b371067 PMD 0                                [    3.838573] Oops: 0000 [#1] SMP                                              [    3.854523] Modules linked in: ehci_pci(F+) ehci_hcd(F) usbcore usb_common en(OF)
[    3.890028] CPU: 3 PID: 3736 Comm: insmod Tainted: GF          O 3.10.105 #25426
[    3.925651] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019
[    3.959639] task: ffff88027aedf040 ti: ffff88027b244000 task.ti: ffff88027b244000
[    3.995501] RIP: 0010:[<ffffffff8129756a>]  [<ffffffff8129756a>] pci_bus_read_config_word+0x4a/0x90
[    4.039591] RSP: 0018:ffff88027b247b80  EFLAGS: 00010046
[    4.064597] RAX: 0000000000000246 RBX: 0000000000000006 RCX: 0000000000000064
[    4.099404] RDX: 0000000000006464 RSI: 00000000330d103c RDI: ffffffff81ab4140
[    4.133302] RBP: 0000000000000000 R08: 000000000000000a R09: 000000000000fffb
[    4.167613] R10: 0000000000000000 R11: 00000000000002e1 R12: 00000000330d103c
[    4.202178] R13: ffff88027b247bbe R14: 0000000000000246 R15: ffffffffa0060c80
[    4.236488] FS:  00007f9e3448f700(0000) GS:ffff88028bac0000(0000) knlGS:0000000000000000
[    4.275673] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    4.303283] CR2: 00000000000000b8 CR3: 0000000279fc4000 CR4: 00000000001607e0
[    4.337430] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[    4.371714] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[    4.405979] Stack:
[    4.415628]  000000007b247bd8 0000000000000000 000000000000000a ffff88027deab808
[    4.451157]  0000000000000000 ffff88027deab898 ffffffff8129c856 0000000000000001
[    4.487077]  ffff88027deab808 ffffffff8129c89b ffff880279cef000 ffff880279cef800
[    4.523252] Call Trace:
[    4.534959]  [<ffffffff8129c856>] ? __pci_bus_find_cap_start+0x16/0x40
[    4.566443]  [<ffffffff8129c89b>] ? pci_find_capability+0x1b/0x50
[    4.595790]  [<ffffffffa00601bd>] ? ehci_pci_setup+0x9d/0x580 [ehci_pci]
[    4.627943]  [<ffffffffa0014305>] ? usb_add_hcd+0x1f5/0x770 [usbcore]
[    4.658878]  [<ffffffffa0023b63>] ? usb_hcd_pci_probe+0x393/0x490 [usbcore]
[    4.692103]  [<ffffffff812a0640>] ? pci_device_probe+0x60/0xa0
[    4.720755]  [<ffffffff8130cb1e>] ? driver_probe_device+0x7e/0x3e0
[    4.750460]  [<ffffffff8130cf3b>] ? __driver_attach+0x7b/0x80
[    4.778021]  [<ffffffff8130cec0>] ? __device_attach+0x40/0x40
[    4.805523]  [<ffffffff8130ab73>] ? bus_for_each_dev+0x53/0x90
[    4.833888]  [<ffffffff8130c198>] ? bus_add_driver+0x1c8/0x280
[    4.861765]  [<ffffffff8130d528>] ? driver_register+0x68/0x150
[    4.889359]  [<ffffffffa0062000>] ? 0xffffffffa0061fff
[    4.915413]  [<ffffffff8100038a>] ? do_one_initcall+0xca/0x180
[    4.943621]  [<ffffffff8108b69c>] ? load_module+0x1d0c/0x2360
[    4.971932]  [<ffffffff81290c70>] ? ddebug_proc_write+0xe0/0xe0
[    5.001392]  [<ffffffff8108bd84>] ? SYSC_init_module+0x94/0xf0
[    5.031832]  [<ffffffff814cedc4>] ? system_call_fastpath+0x22/0x27
[    5.061407] Code: 83 c4 08 5b 5d 41 5c 41 5d 41 5e c3 0f 1f 44 00 00 48 89 fd 48 c7 c7 40 41 ab 81 49 89 cd 89 d3 41 89 f4 e8 69 68 23 00 49 89 c6 <48> 8b 85 b8 00 00 00 4c 8d 44 24 04 89 da 44 89 e6 48 89 ef b9
[    5.152530] RIP  [<ffffffff8129756a>] pci_bus_read_config_word+0x4a/0x90
[    5.185578]  RSP <ffff88027b247b80>
[    5.202448] CR2: 00000000000000b8
[    5.218521] ---[ end trace f5d94b74adcccbe2 ]---
 ... [FAILED]
:: Loading module ohci-hcd[    5.243965] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
 ... [  OK  ]
:: Loading module uhci-hcd[    5.276755] uhci_hcd: USB Universal Host Controller Interface driver
[   29.198406] Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 1

Edited by youngc29
Link to post
Share on other sites

Sorry to spam again, I reflashed USB and got the below from serial (although im unable to login :)

 

 

    Use the ^ and v keys to select which entry is highlighted.
      Press enter to boot the selected OS, `e' to edit the commands
      before booting or `c' for a command-line.
patching file etc/rc
Hunk #1 succeeded at 182 (offset 11 lines).
patching file etc/synoinfo.conf
Hunk #1 FAILED at 291.
1 out of 1 hunk FAILED -- saving rejects to file etc/synoinfo.conf.rej
patching file linuxrc.syno
Hunk #1 succeeded at 40 with fuzz 2 (offset 1 line).
Hunk #2 succeeded at 141 (offset 6 lines).
Hunk #3 succeeded at 579 (offset 28 lines).
patching file usr/sbin/init.post
cat: can't open '/etc/synoinfo_override.conf': No such file or directory
START /linuxrc.syno
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 ohci-hcd ... [  OK  ]
:: Loading module uhci-hcd ... [  OK  ]
:: Loading module xhci-hcd ... [  OK  ]
:: Loading module usb-storage ... [  OK  ]
:: Loading module BusLogic ... [  OK  ]
:: Loading module megaraid_mm ... [  OK  ]
:: Loading module megaraid_mbox ... [  OK  ]
:: Loading module megaraid ... [  OK  ]
:: Loading module megaraid_sas ... [  OK  ]
:: Loading module mpt2sas ... [  OK  ]
:: Loading module sx8 ... [  OK  ]
:: Loading module aacraid ... [  OK  ]
:: Loading module aic94xx ... [  OK  ]
:: Loading module 3w-9xxx ... [  OK  ]
:: Loading module 3w-sas ... [  OK  ]
:: Loading module 3w-xxxx ... [  OK  ]
:: Loading module mvumi ... [  OK  ]
:: Loading module mvsas ... [  OK  ]
:: Loading module arcmsr ... [  OK  ]
:: Loading module isci ... [  OK  ]
:: Loading module hpsa ... [  OK  ]
:: Loading module nvme ... [  OK  ]
Insert net driver(Mindspeed only)...
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocfgen returns 0
All disk ready or timeout execeed
[    3.929112] md: invalid raid superblock magic on sda3
[    4.018695] md: invalid raid superblock magic on sdb3
[    4.102574] md: invalid raid superblock magic on sdc3
[    4.187790] md: invalid raid superblock magic on sdd3
Partition Version=8
 /sbin/e2fsck exists, checking /dev/md0...
/sbin/e2fsck -pvf returns 0
Mounting /dev/md0 /tmpRoot
------------upgrade
Begin upgrade procedure
No upgrade file exists
End upgrade procedure
============upgrade
Exit on error [7] Version number not match...
[    6.640695] sd 7:0:0:0: [sdu] No Caching mode page found
[    6.666653] sd 7:0:0:0: [sdu] Assuming drive cache: write through
[    6.700385] sd 7:0:0:0: [sdu] No Caching mode page found
[    6.726169] sd 7:0:0:0: [sdu] Assuming drive cache: write through
[    6.761081] sd 7:0:0:0: [sdu] No Caching mode page found
[    6.787334] sd 7:0:0:0: [sdu] Assuming drive cache: write through
Thr Apr  8 03:01:37 UTC 2021
/dev/md0 /tmpRoot ext4 rw,relatime,journal_checksum,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
none /dev devtmpfs rw,relatime,size=5086216k,nr_inodes=1271554,mode=755 0 0
proc /proc proc rw,relatime 0 0
linuxrc.syno failed on 7
starting pid 4831, tty '': '/etc/rc'
:: Starting /etc/rc
:: Mounting procfs ... [  OK  ]
:: Mounting tmpfs ... [  OK  ]
:: Mounting devtmpfs ... [  OK  ]
:: Mounting devpts ... [  OK  ]
:: Mounting sysfs ... [  OK  ]
rc: Use all internal disk as swap.
/etc/rc: line 117: /usr/syno/bin/synodiskpathparse: not found
/etc/rc: line 117: awk: not found
rc: Failed to parse partition sda2
:: Loading module sg ... [  OK  ]
:: Loading module crc-ccitt ... [  OK  ]
:: Loading module crc-itu-t ... [  OK  ]
:: Loading module mdio ... [  OK  ]
:: Loading module fat ... [  OK  ]
:: Loading module vfat ... [  OK  ]
:: Loading module ip_tunnel ... [  OK  ]
:: Loading module vxlan ... [  OK  ]
:: Loading module dca ... [  OK  ]
:: Loading module e1000e ... [  OK  ]
:: Loading module i2c-algo-bit ... [  OK  ]
:: Loading module igb ... [  OK  ]
:: Loading module be2net ... [  OK  ]
:: Loading module ixgbe ... [  OK  ]
:: Loading module r8168 ... [  OK  ]
:: Loading module libcrc32c ... [  OK  ]
:: Loading module mii ... [  OK  ]
:: Loading module libphy ... [  OK  ]
:: Loading module atl1 ... [  OK  ]
:: Loading module atl1e ... [  OK  ]
:: Loading module atl1c ... [  OK  ]
:: Loading module alx ... [  OK  ]
:: Loading module uio ... [  OK  ]
:: Loading module ipg ... [  OK  ]
:: Loading module jme ... [  OK  ]
:: Loading module skge ... [  OK  ]
:: Loading module sky2 ... [  OK  ]
:: Loading module ptp_pch ... [  OK  ]
:: Loading module pch_gbe ... [  OK  ]
:: Loading module qla3xxx ... [  OK  ]
:: Loading module qlcnic ... [  OK  ]
:: Loading module qlge ... [  OK  ]
:: Loading module netxen_nic ... [  OK  ]
:: Loading module sfc ... [  OK  ]
:: Loading module e1000 ... [  OK  ]
:: Loading module pcnet32 ... [  OK  ]
:: Loading module vmxnet3 ... [  OK  ]
:: Loading module bnx2 ... [  OK  ]
:: Loading module bnx2x ... [  OK  ]
:: Loading module igbvf ... [  OK  ]
:: Loading module ixgbevf ... [  OK  ]
:: Loading module r8101 ... [  OK  ]
:: Loading module r8125 ... [  OK  ]
:: Loading module r8169 ... [  OK  ]
:: Loading module tg3 ... [  OK  ]
:: Loading module usbnet ... [  OK  ]
:: Loading module ax88179_178a ... [  OK  ]
:: Loading module button ... [  OK  ]
:: Loading module evdev ... [  OK  ]
:: Loading module atl2 ... [  OK  ]
:: Loading module e100 ... [  OK  ]
:: Loading module ixgb ... [  OK  ]
:: Loading module forcedeth ... [  OK  ]
:: Loading module tn40xx[    8.158153] tn40xx: Tehuti Network Driver, 0.3.6.17.2
[    8.183348] tn40xx: Supported phys : MV88X3120 MV88X3310 MV88E2010 QT2025 TLK10232 AQR105 MUSTANG
 ... [  OK  ]
:: Loading module cxgb ... [  OK  ]
:: Loading module cxgb3 ... [  OK  ]
:: Loading module cxgb4 ... [  OK  ]
:: Loading module atlantic ... [  OK  ]
:: Loading module bna ... [  OK  ]
:: Loading module vxge ... [  OK  ]
:: Loading module aqc111 ... [  OK  ]
:: Loading module asix ... [  OK  ]
:: Loading module cx82310_eth ... [  OK  ]
:: Loading module et131x ... [  OK  ]
:: Loading module i40e ... [  OK  ]
:: Loading module i40evf ... [  OK  ]
:: Loading module mcs7830 ... [  OK  ]
:: Loading module pegasus ... [  OK  ]
:: Loading module plusb ... [  OK  ]
:: Loading module r8152 ... [  OK  ]
:: Loading module rtl8150 ... [  OK  ]
:: Loading module s2io ... [  OK  ]
:: Loading module xgmac ... [  OK  ]
:: Loading module i2c-i801 ... [  OK  ]
:: Loading module adt7475 ... [  OK  ]
Can not detect ADT device, Retry: 1...
:: Unloading module adt7475 ... [  OK  ]
:: Unloading module i2c-i801 ... [  OK  ]
:: Loading module i2c-i801 ... [  OK  ]
:: Loading module adt7475 ... [  OK  ]
Can not detect ADT device, Retry: 2...
:: Unloading module adt7475 ... [  OK  ]
:: Unloading module i2c-i801 ... [  OK  ]
:: Loading module i2c-i801 ... [  OK  ]
:: Loading module adt7475 ... [  OK  ]
Can not detect ADT device, Retry: 3...
:: Unloading module adt7475 ... [  OK  ]
:: Unloading module i2c-i801 ... [  OK  ]
:: Loading module i2c-i801 ... [  OK  ]
:: Loading module adt7475 ... [  OK  ]
:: Loading module synobios ... [  OK  ]
udhcpc (v1.16.1) started
udhcpc (v1.16.1) started
eth0      Link encap:Ethernet  HWaddr 00:15:17:F3:F2:38
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:16 Memory:fbfe0000-fc000000

eth1      Link encap:Ethernet  HWaddr 00:15:17:F3:F2:39
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:17 Memory:fbfa0000-fbfc0000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

:: Starting syslogd ... [  OK  ]
:: Starting scemd
:: Starting services in background
Starting findhostd in flash_rd...
Starting services in flash_rd...
Running /usr/syno/etc/rc.d/J01httpd.sh...
Starting httpd:80 in flash_rd...
Starting httpd:5000 in flash_rd...
Running /usr/syno/etc/rc.d/J03ssdpd.sh...
/usr/bin/minissdpd -i eth0 -i eth1
eth0 not RUNNING
eth1 not RUNNING
Running /usr/syno/etc/rc.d/J04synoagentregisterd.sh...
Starting synoagentregisterd...
Running /usr/syno/etc/rc.d/J30DisableNCQ.sh...
Running /usr/syno/etc/rc.d/J80ADTFanControl.sh...
Running /usr/syno/etc/rc.d/J98nbnsd.sh...
Starting nbnsd...
Running /usr/syno/etc/rc.d/J99avahi.sh...
Starting Avahi mDNS/DNS-SD Daemon
cname_load_conf failed:/var/tmp/nginx/avahi-aliases.conf
:: Loading module hid ... [  OK  ]
:: Loading module usbhid ... [  OK  ]
============ Date ============
Thr Apr  8 03:01:52 UTC 2021
==============================
starting pid 7513, tty '': '/sbin/getty 115200
Thu Apr  8 03:01:53 2021

DiskStation login: admin
Password:
Login incorrect
DiskStation login: admin
Password:
Login incorrect
DiskStation login: admin
Password:
process '/sbin/getty 115200 con
Thu Apr  8 03:03:44 2021

DiskStation login: admin
Password:
Login incorrect

 

Link to post
Share on other sites
On 2/28/2021 at 6:38 PM, IG-88 said:

pretty sure you will not be the last

 

download a rescue/live linux like system rescue cd (i used a "older" version 6.0.3, mdadm and lvm worked ootb, any newer should be fine too), transfer it to a usb (not your dsm boot usb) to boot from it


assemble your raid1 system partition like here (1st partitions of all disks as /dev/md0)

skip anything about swap or volume1 data partition, we only need access to the dsm system partiton
https://xpenology.com/forum/topic/7004-tutorial-how-to-access-dsms-data-system-partitions/

 

mount the assembled raid1 to /mnt with this


mount /dev/md0 /mnt

 

then remove some files with this


rm -rf /mnt/SynoUpgradePackages
rm -f /mnt/SynoUpgrade.tar
rm -f /mnt/SynoUpgradeindex.txz
rm -f /mnt/SynoUpgradeSynohdpackImg.txz
rm -f /mnt/checksum.syno
rm -f /mnt/.syno/patch/*

 

and shutdown the linux


shutdown -h now

 

now you will have to restore the kernel files on your boot usb to 6.2.3 (the udpate also replace files on the loaders 2nd partition)

win10 can have some difficulties with mounting the 2nd partitons of the loader, so look here
https://xpenology.com/forum/topic/29872-tutorial-mount-boot-stick-partitions-in-windows-edit-grubcfg-add-extralzma/

(it can also be done with linux but i have not tried what other tools will extract the kernel files but if you are familiar with linux you will find out

https://xpenology.com/forum/topic/25833-tutorial-use-linux-to-create-bootable-xpenology-usb/)

 

on 2nd partition delete all files except extra.lzma and extra2.lzma (if its 3615/3617 then its just extra.lzma)
use 7zip to open "DSM_xxxxx_25426.pat" (dsm 6.2.3 install file, depends on you dsm type 3615/3617/918+)

 extract "rd.gz" and "zImage" and copy it to the 2nd partition of your xpenology usb

<edit>

the assumption here is you already had 6.2.3 before the 6.2.4 udpate try, if not you would use the kernel files from the *.pat of the 6.2.x you had installed

as a example what could go wrong: if you had 6.2.2 and did 6.2.4 your extra/extra2.lzma on the loader where usually replaced with special ones made for 6.2.2, if you add 6.2.3 kernel files to the 6.2.2 extra/extra2 (drivers) then most of the drivers will not work as of the incompatibility with 6.2.1/6.2.2 with 6.2.0/6.2.3

if you are unsure about the extra/extra2 or you dsm version then use the original extra/extra2 from jun's loader (img file can be opened with 7zip, loaders kernel files and drivers in its extra/extra2 are 6.2.0 level) or use a extended version of the extra/extra2 made for 6.2.3 and use the kernel files of 6.2.3 if you had a older 6.2.x that would do a update to 6.2.3

</edit>

 

put back your usb to the xpenology system, boot up, find it in network (i used synology assistant) and migrate to version 6.2.3 (aka reinstall 6.2.3)
it will boot two times, one for 6.2.3, 2nd for 6.2.3_U3 (it will be downloaded automatically if internet connection is present)

 

everything should be back to normal except patches like nvme ssd patch (or other stuff you patched after installing 6.2.3 that is not dsm update resistant)

if that all works you i will  make a new thread in the tutorial section because if synology starts offering 6.2.4 with the web update there will be more people asking for a fix to come back to 6.2.3

please comment on how to make it easier to follow, its just a short version i tried once

 

if that sounds all to complicated then its still possible to use the other downgrade method (but you will loos all settings and end with a factory default DSM)

https://xpenology.com/forum/topic/12778-tutorial-how-to-downgrade-from-62-to-61-recovering-a-bricked-system/

 

 

It was my own fault. I completely forgot everything I know about change management and hit update on my live servers, only to watch both of them get bricked. Damn!  In my defence, I was still suffering from a rather nasty bout of gastric flu, but it does make me question whether I should turn in my ITIL certification...

 

Anyway, massive thanks to you @IG-88, I followed your process on both servers and they are now happily whirring away again.  I'll keep an eye on them to make sure nothing untoward happens, but so far, so good.  In my local parlance, you, sir, are a flippin' legend!

  • Like 1
Link to post
Share on other sites

Thanks @IG-88

I guess now I just need to work out which Slot is which in my Microserver as far as DSM is concerned and transfer everything to the genuine 1815+ that is sitting in my wardrobe that I've just never got round to moving the drives to for fear of everything crashing.

 

The recovery worked amazingly well - the only issue I encountered were my bonded ethernet ports - I had to move to a single port on my switch, then put the 4 cables back in their original switch port and reboot, after that everything came back up.

 

Once again, thanks for the information and I hope that soon we can get an EFI loader that works but I don't think it will be me who manages to do it :)

Link to post
Share on other sites

I did the upgrade from 6.2.3u3 to 6.2.4 like a noob.

On the morning I received the mail from Syno telling me there is an update available.

I checked the ReleaseNotes, meh it's just a minor upgrade let's do it.

Totally forgot to check the forum before applying the upgrade.

 

Thank you so much @IG-88 for your guide on how to downgrade to 6.2.3u3 !

The links you provide to other guides made your explanations really complete.

I personally do not see how to make it more clear.

 

I just had a doubt about deleting this file :

Citation

rm -f /mnt/SynoUpgradeindex.txz

It was  not present on my disk but there was  file named SynoUpgradeIndexAAA.txz (AAA = something I don't remembre -_-')

I juste assumed it was the same and deleted it ending with no more file named /mnt/Syno...

 

Thanks again, you made my DS918+ back online without loosing data or configuration :-)

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.