Jump to content
XPEnology Community

canzone

Rookie
  • Posts

    7
  • Joined

  • Last visited

Everything posted by canzone

  1. Hello guys, I started a project to migrate my several years-old "DSM 6.1.7-15284 Update 3", model DS3615xs to 7.2. Before messing up with the real deal, I've installed ARPL boot loader in a new USB stick and installed it with a new HDD just to see what happens. I've heard that one cannot move directly from 6.x to 7.2, so I did this first. Installed a DS3622xs+ model 42962 and DSM 7.1.1-42962 Update 6, the last one available. Couldn't be easier. Runs perfectly. Then I created a third USB stick with ARC 23.12.4 and tried several DS models: - DS3622xs+, DS6121xs+, RS3621xs+, DS1819+ hang when it tries to load DSM ("“Arc console - wait…”) - DS1520+ allows me to install the latest DSM version (7.2.1-69057). But, after booting, I get the DSM error (by accessing http://IP:5000) “Sorry, the page you are looking for is not found” I've tried to downgrade ARC boot loader to 23.12.3, 23.11.x, 23.10.x with the same results. Tried ARC with a lower DSM version (7.2.1 64570) and did not work. Also tried to use ARC with 7.1, did not work too. Tried direct boot, tried to play with addons... nothing helped. In time: on every try, instead of just recreating the boot loader directly, I burned the USB from scratch, to avoid any "side effects". Hardware is: Mainboard: ECS NM70-I2 (V1.0) CPU: Celeron 847-2M-Cache-1_10-GHz NIC: Realtek 8111E Any ideas? Thanks a lot!
  2. Hello everyone! I've set up DS3622xs+ with build number 42962 on a bare metal system, running DSM 7.1.1-42962 Update 6. It recognized my 4 HDDs and worked like a charm. Then I shut it down and attached a PCI SATA expansion card and connected an (original) DX510 expansion unit. Booted it up with an extra disk in this unit. It recognized the unit (see the following screenshot) but it did not recognize the disk. It "thinks" that three of the disks in the main system are also in the expansion (notice that the disk numbers are the same). For example, if I click the disk 1 in either the main system or the expansion, it shows me the same disk. But the 5th disk is actually there. The command "dmesg" shows it: [ 26.538418] ata8.01: Enhance DX510 compatibility, limit the speed to 1.5 GBPS [ 26.545547] ata8.01: ATA-8: SAMSUNG HM160HI, HH100-15, max UDMA/100 [ 26.551808] ata8.01: 312581808 sectors, multi 0: LBA48 [ 26.557025] ata8.01: SN:S1M5J56S700002 [ 26.563356] ata8.01: Enhance DX510 compatibility, limit the speed to 1.5 GBPS [ 26.570485] ata8.01: configured for UDMA/100 [ 26.574791] ata8: EH complete It is also seen in "fdisk -l": Disk /dev/sdhb: 149.1 GiB, 160041885696 bytes, 312581808 sectors Disk model: HM160HI Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes I've tried to "hack" the system, by editing /etc.defaults/synoinfo.conf and /etc/synoinfo.conf, making the system recognize the four first disks as internal and the other four as ESATA, but when I reboot, the config files are overwritten back to the "original" state. Long story short: seems that Synology is not scanning the new added disk. Is there a way to force this? In a way that I can keep my original installation (there is a lot of data in the disks, I don't want to reinstall and restore everything from my backup... it took me 4 days to load it. Thanks a lot!
  3. First of all, thanks a trillion times for this. I've been planning, for years, to upgrade my DSM 6.1.7 (Update 3) to the 7.x world, but I've read so many tragic stories, so I waited. I've installed RedPill in a new USB thumb drive (this is important, as I was facing the "Failed to install. Probably corrupt" message on 57% of the installation over and over again). I've installed the recommended version (DSM 7.1.1-42962 Update 6) during the installation process. Another thing that helped was to select DS3622xs+... I was trying to install DS3617xs (error on 57%) or DS3615xs (not even loaded). Last, but not least, one interesting option is to install the console Add-on. This allowed me to log into command line Synology and look at the logs, which gave me good insights on errors and issues. In time: I did not upgrade my NAS. I've installed RedPill in another thumb drive, with a separate set of hard drives, and I'm migrating the data from one to another (I'm old school).
  4. Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.7-15284 Update 2 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL (ASRock E3C226D2I, Intel BX80646G1840, Kingston KVR16LN11K2/16) - Additional comments: REBOOT REQUIRED - Had to power cycle hardware after update
  5. - Outcome of the update: SUCCESSFUL - DSM version prior update: 6.1.7-15284 Update 1 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock E3C226D2I, Intel BX80646G1840, Kingston KVR16LN11K2/16 - Additional comments: REBOOT REQUIRED
  6. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4-15217 Update 5 - Loader version and model: Jun's Mod V1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL (ASRock E3C226D2I, Intel BX80646G1840, Kingston KVR16LN11K2/16) - Additional comments: Updated through Control Panel, to 6.1.7-15284, then to Update 1. Reboot required.
  7. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 Update 2 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: Baremetal (ASRock E3C226D2I, Intel BX80646G1840, Kingston KVR16LN11K2/16) - Additional comments: None
×
×
  • Create New...