manfriday

- Outcome of the update: UNSUCCESSFUL - DSM version prior to update: DSM 6.2.1-23824 update 6 - Loader version and model: Jun v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock J3455-M Additional Notes: Single onboard NIC only (no lights on NIC after attempted update. Tried a fresh install by re-formmating the disks and same result. Installs okay but lights out for onboard NIC

Another failed upgrade attempt and another fall back to 6.1.7....followed the input of SBV3000 1) Disconnect your raid drives 2) Connect spare HDD to SATA port 1 3) Install DSM 6.x from fresh 1.02b loader, create admin user and server name matching live system, DONT create volume/raid. Update DSM to match your pre-beta version 4) Shutdown, reconnect raid drives to SATA ports 2-n 5) Boot, login, repair system partitions on raid, shutdown 6) Remove spare HDD and reconnect raid drives to SATA ports 1-n 7) Boot, repair packages etc However one additional note. I have two volumes, one is Hybrid Raid SHR 5xHDDs and one volume RAID1 BTRFS 2xHDDs. I unplugged all drives and rebuilt only the BTRFS volume, Shutdown plug in remaining 5 HDD and allowed rebuild.

Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.1-23824 Update 4 - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Asrock J3455 M - Additional comments: reboot required

Yes thanks

thanks for follow up Cheers MF

I inadvertently ended up with 2 working systems both running 6.2.1 (DS 918+) and both with the same serial number. I have searched but can only find info on changing serial numbers for v5 and earlier releases. Any help is appreciated. MF

Thanks for the explanation and quick response. I have a few hours to go with current rebuild before I can rework the "failed partition" Cheers MF

Attempting to shuffle drives around in order to get more capacity I decommissioned a 4TB hdd from a 1 drive pool (no data loss as there was no data in pool) and a second drive from a populated Vol Pool. I pulled the 2 drives (and also removed a 2port SATA card). I replaced one of the drives with a higher capacity drives and powered system on. Took a long time to boot. I was expecting, and received a Vol Degraded message, however I also received a System Partition Failed for a different drive. System is currently rebuilding with the newly added drive but I am not sure what effect the failed system partition is or will have. The drive itself appears to be okay but I wont know until I finish the 1st task. All the data on the Pool is still intact and nothing else appears impacted. I'm not sure if I have question but has anybody else had a system partition failure? system: Baremetal ASrock J3455 DS918+ DSM 6.2.1-23824 Update 4.

Use the real MAC address from the NIC or MB you are installing on

Sure....perhaps you should stay awhile and take a look around

- Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.1-23824 - Update 1 - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock J3455M - Additional comments: 2nd NIC (Intel) 4 port SATA card

You seemed to have answered your own question. The Fuji looks to goods

I have tried NVMe with adapter https://www.amazon.com/gp/product/B07F9RBP5W/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1 in PCIe slot with 512GB stick. Only works in DS918+ config and is only read only cache as there is one stick of storage. BTW you can certainly use more than 8 drives in the DS918+

for transcoding 8700 will work fine but my POV is from power consumption and power on hours. I run my server 24*7 and low power (given $ per kw/h that I pay) is important to me. Maybe not to you so plan accordingly. Ryzen is AMD (Duh) and has it's own requirements but I believe Juno's splendid efforts have counted for that.

If you are streaming and not transcoding the 8700 is overkill. I run an ASrock AD2550R Atom dual Core. Hardly breaks a sweat streaming to Samsung (smart tv).

- Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.1.7-15284 on DS3617xs - Loader version and model: JUN'S LOADER v1.04b - DS918+ 6.2.1-23824 updt 1 - Using custom extra.lzma: NO  - Installation type: BAREMETAL - 3455M 8GB SATA 4 port card, Intel NIC - Additional comments: 2 volumes, 1 encrypted

- Outcome of the installation/update: SUCCESSFUL - DSM version prior update: ~DSM 6.1? unsure what version as I used a drive from an earlier install and opted for migration option during installation - Loader version and model: Jun v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock J3455M 4GB memory - Additional comments: Intel and onboard NIC both reported but 2 completely different IP address ranges. Connected LAN 2 (intel) is 192.168.x.x address, onboard LAN 1 is 168.254.x.x Also have 4port SATA card attached with attached drive...all working fine but not completely tested all functions

- Outcome of the installation/update: UNSUCCESSFUL - DSM version prior update: DSM 6.2-23739 update 2 - Loader version and model: JUN'S LOADER v1.04 - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Asrock J3455M - Additional comments: Baremetal install onto clean drive / 4 port SATA card also installed. Update fails at 2% with Unknown Error(21)

generator works fine, try another browser 3615xs - 1230LWN003804

Alas, my copy is 1.03a2. BTW a thanks to you for suggesting the removal of all the peripherals (keyboard etc) in order to get the boot to complete successfully. I have not put any serious effort into playing with the J3455 system due to performance being sub par and rebuilding bricked system.

6.2 is definitely a WIP. I have rebuilt a bricked system for the 2nd time (ASRock J3455M) first time trying to move to 6.2 as a DS918, the second as DS317xs. Yet I have the same mobo successfully running 6.2 from Juno first release of DS918 . I have seen what others have observed, slow boot and transfer with the J3455 setup. The shake out continues........

I followed the steps from other posters based on a 6.2 upgrade failure. My hardware is Intel based (J3455M) vs your AMD (I don't know if this makes a difference). Perhaps try another recovery process from earlier in this thread?

1) Disconnect your raid drives - Did this 2) Connect spare HDD to SATA port 1 - Did this 3) Install DSM 6.x from fresh 1.02b loader, create admin user and server name matching live system, DONT create volume/raid. Update DSM to match your pre-beta version - Did this actually tried to install a PAT version earlier than the last version I was running. Syno Assistant told me which version I had to install and so I did. 4) Shutdown, reconnect raid drives to SATA ports 2-n - Did this but shutdown system at about 10% rebuild process. It occurred to me that leaving the spare HDD in to be part of the rebuild is redundant. 5) Boot, login, repair system partitions on raid, Shutdown Did this 6) Remove spare HDD and reconnect raid drives to SATA ports 1-n - Did this 7) Boot, repair packages etc The above was posted by SBV3000 and many thanks. I did make a couple of changes to shorten the process. It worked for me but no warranty implied Everything in coloured text is mine, all else belongs to SBV3000 and others