Jump to content
XPEnology Community

rebos

Rookie
  • Posts

    3
  • Joined

  • Last visited

rebos's Achievements

Newbie

Newbie (1/7)

0

Reputation

  1. tried this too, but always get a checksum error, any way to solve it? System: SM X9SRL-F, Xeon E5, 32GB Ram LSI 9300-16i HBA, QLE 10GB NIC, D-Link 10G NIC I guess due your relatively new/non-widely used as standard NIC chipset. most checksum errors in this stage come from the ETH level.. Maybe quicknick has seen this behaviour before, but he is possibly working hard on the 2.4 now
  2. Might be why, not sure. we have run several sequences and each time you upgrade (also from 2.3 to 2.3, which justs redownloads i guess) it happens. rebooting keeps the values (indeed 400's)
  3. We have several Custom Build configurations running on an Asus Mini-ITX, Z170N-WiFi (rev.01). (This board uses Intel GBE NICs) One of them is currently designated as 'test' unit. The last few days we read several forumposts and started a migration, in which we (finally) succeeded doing to following: Take-off configuration: DSM 5.2-5644_update5 (boot device: XPENoboot USB) Final successful method applied: -manually applied DSM 6.0.2_8451 (primary pat file) -booted on USB key using quicknick's 2.2 version -started with option 5 --> quicknick's menu via SSH (yes, just read the f.a.q.'s like quicknick says and it will work) -reviewed USB Vid and Pid, serial which were edited in the grub.cfg via Windows whilst creating the boot device. (not required, can be done via the quicknick menu also) -upgraded the USB bootdevice files to version 2.3(betastate) (How? just used the options in the menu, that's what there for ) + REMARK: the Vid and Pid are changed once you upgrade the device version. You have to reboot and go into the menu again via SSH afterwards to correct the Vid and Pid Now here is where we were required to leave the quicknick path for a bit: - reinserted the 5.2 XPENoboot USB device and restarted the unit again, booting it normally - start Syno Assistant and discover the unit (Windows requires a second discovery, it will not show up in the list the first scan) - either right-click it and choose 'install' or just select Connect (which does about the same via a separate browser window/tab) - It will be shown as migratable. (Using the 6.02 bootdevice will give you either error 13 or 46 after 56% (..installing DSM). whether you upload .pat manually or have it download during from Synology) - migrated, whist having .pat downloaded from synology (shows that there is no adjusted .pat required) - after required restart, left 5.2 XPENoboot as bootdevice. rediscovered the unit using Syno Ass. - tried update DSM (either internet download or manually upload .pat (update 5) will not work. Also the device does not show the volume (discovered before migration, hence 'migratable unit') - restarted using the quicknick 2.3(beta) bootdevice, option 1, boot normally - logged in succesfully onto DSM 6.02 - volume is there, folder contents is there, packages were not (was only running 1 before the entire operation was started) *so this is still to be determined why and possibly requires some attention) - updated to .pat update5 manually, restarted - logged in successfully onto DSM 6.02-update5 - updated to .pat update6 via Synology download and update buttons, restarted - system running smooth on 6.02-update6 (released 9 dec 2016) @quicknick: any explanation on the fact that the Vid and Pid are reset when upgrading from 2.2 to 2.3 via the menu?
×
×
  • Create New...