Search the Community

Result of my search. Took me less than 5 minutes. https://xpenology.com/forum/search/?&q="detected that the hard drives"&sortby=relevancy Produced the following results among others: https://xpenology.com/forum/topic/7507-tutorial-installmigrate-dsm-52-to-602-juns-loader/?page=39#comment-76396 https://xpenology.com/forum/topic/7483-problems-after-replacing-network-card/#comment-71952 https://xpenology.com/forum/topic/6253-dsm-6xx-loader/?page=80#comment-63770 https://xpenology.com/forum/topic/5549-hard-drive-migrating-problem/#comment-47932 https://xpenology.com/forum/topic/5442-downgrade-from-dsm-60/?page=2#comment-47260 The search function is powerful. Just try different word combinations.

If only people cared to search and read the forum there wouldn't be so many redundant topics and posts. Fear not I will restructure the forum soon enough and rules applied to the letter but that's for another day. The "We've detected that the hard drives of your current ds3615xs has been moved from a previous ds3615xs, and installing a newer dsm is required before continuing" message is a standard message when upgrading. I probably was the first person to ask about it a year ago. Click next and you will be given the choice to install then migrate.

ok, i tried anyway created a new VM , start clean, install DSM on a virtual disk (ssd), i turn off, i attach my other disk as soon as i start now 6 i get this message : we've detected that the hard drives of your current ds3615xs has been moved from a previous ds3615xs, and installing a newer dsm is required before continuing am i save to proceed? , probably it will overwrite, so i think i can continue?? if i continue, lets say, i want to go back to 5.2 , can i still do that then? will it downgrade? without loosing data offcourse

Hi all, I'm trying to migrate from DSM 5.2 to 6.0 using Jun's 1.01 loader and everything's been going fine and I can find my Syno using WebAssistant. However I have a question: By coincidence my previous version of DSM 5.2 set up for the same DS3615xs as used in Jun's loader. So now WebAssistant is saying: "We've detected that the hard drives of your current DS3615xs had been moved from a previous DS3615xs and installing a newer DSM is required before continuing". And only one button I can press - INSTALL. But I was expecting a Migrate button to be able to choose the target .pat file. I'm confused now... If I press install - will it erase all the data on my HDs? What should I do? Could you please help?

Hello all. So it;s the first time I try to install xpenology and I started with this tutorial. Setup: an old Lenovo m58p My problem: I get to the install part, it says "We've detected errors on your hard drives [drive number] and the SATA ports have also been disabled " I tried the force install, after restart if I select normal boot, I get the same error. I looked at the sata interfaces on the MB and I have sata1 and sata2 so I added: SataPortMap=1 (I only have an old HDD connected at sata1) No I always get the msg: "We detected that you had moved the hard drive to a new DS3615xs. Please click recover ...." I click recover but get the same msg after each restart... help?

не удачно обновился.... Теперь в статусе RECOVER We've detected that you had moved the hard drives to a new DS3615xs. Please click Recover if you want to recover your data and settings now. Помогите, пожалуйста, советом...

I'm jumping in to migrate from 5.2 to 6.1 with 1.02b loader, I've come to the step where i'm able to see the nas and I'm presented with the screen stating this below and the button "Install". I was expecting a migration option there. If I press "Install" does it automatically install most recent DSM? What should I do? We have detected that the hard disks of your current DS3615xs have been moved from an earlier DS3615xs, and installing a newer DSM is required before proceeding. Tried to reboot and choose the "reinstall" option from boot menu but still no option to migrate. I do not dare to press "Install" as I'm afraid to wipe out my drives.

I'm jumping in to migrate from 5.2 to 6.1 with 1.02b loader, I've come to the step where i'm able to see the nas and I'm presented with the screen stating this and the button "Install". I was expecting a migration option there. If I press "Install" does it automatically install most recent DSM? What should I do? We have detected that the hard disks of your current DS3615xs have been moved from an earlier DS3615xs, and installing a newer DSM is required before proceeding. Tried to reboot and choose the "reinstall" option from boot menu but still no option to migrate. I do not dare to press "Install" as I'm afraid to wipe out my drives.

I had to update my network card as the old one died. Unfortunately this seems to have changed PCI slot assignments and the NAS no longer thinks the hard drives are in the same place and is coming up with this message: "We've detected that the hard drives of your current DS3615XS have been moved from a previous DS3615XS, and installing anew DSM is required before continuing" Obviously I can't install a new DSM so is there any way around this? Or do I have to start from scratch?

On my test system I had the hard drives setup as AHCI and when I would boot up on jun's v1.02-alpha loader the system would come up and give me an error message regarding my hard drives. The message stated problems encountered with the hard drives and the sata ports were disabled. I have 4 hard drives so I changed SataPortMap=1 to SataPortMap=4. Same results after another reboot. I was able to install DSM 6.1-15047 with a forced install. The install was successful but each time I rebooted, I received the same error message as you. "The system has detected one or more crashed storage spaces." I also received the same error message on each reboot after creating a volume. So in testing I changed the hard drive setup to IDE. When the system booted there were no hard drive errors. I was able to do a normal install, not forced. After the install, the error message "The system has detected one or more crashed storage spaced." went away. I was able to create a volume. Now on each reboot no errors. I know on jun's v1.01 loader the hard drives needed to be setup on AHCI. I don't know why on my test system the hard drives needed to be in IDE mode vice AHCI for the normal install.

I've tried migrating to the new alpha, but got this error instead: "We've detected errors on the hard drives (6), and the SATA ports have also been disabled. Please shut down your DS3615xs to replace or remove the hard drives and try again." I'm using the same SATA configuration as 6.0.2 loader (SataPortMap=4), and I also tried SataPortMap=1, SataPortMap=5 and SataPortMap=6. No luck. I´ll try again later today using the forced mode.

I've rebased the vendor changes on 3.10.77 to 3.10.102, seems still works. Awesome Jun! having a bit of trouble! can someone please help me on this? Just tried to reinstall the loader, at first everything seems fine, take a look... 1º boot with baremetal reinstall option 2º go http://find.synology.com and choose connect (it shows the ip mac and says migratable) 3º it says that "we've detected that the hard drives had been moved from a previous and installing a new dam is required" 4º i hit migrate and it starts to download and install 5º the system reboots and goes to the screen that says "happy hacking note: this is a alpha build.." 6º i try to find.synology.com but nothing shows up! maybe the network drivers doesn't come up? ...a the third try it went well thanks again

Bit of advice please. I upgraded from 5.0 to 5.2 (update 1) and started the upgrade to 6.0 using v1.1 of Jun's loader (on a N54L). Following the instructions on here, but on step 9, I'm seeing the status as "migratable" in the Syno Assistant, but when connecting I'm only seeing an option to Install, not migrate. There's a message saying "We've detected that the hard drives of your current DS3615xs had been moved from a previous DS3615xs and installing a newer DSM is required before continuing". I don't want to lose any data (I can live with reinstalling packages etc), do I click install and then get more options?

Hardware: Dell OptiPlex 7010 SFF Install Type: Baremetal NIC Model: Broadcom, supported Storage: SATA, 1x500GB HDD Issue: Installation/Hard Drives Loader Version: 2.2 I am eager to test this new loader but I keep running into an error on the initial setup screen (see photo below). I only have one hard drive installed (HGST 500GB SATA) and the BIOS is configured for AHCI SATA operation mode and only the SATA-0 port is enabled in the BIOS. This is my XPE test box and has been fully compatible with ever other loader that's come across this website. I'm curious what the hangup is here. I was able to SSH into the configuration tool and ran the quick setup and also set the number of drives to 1 and I still get the pre-installation failure reporting, "We've detected errors on the hard drives (2,3,4,5,6), and the SATA ports have also been disabled. This error only slightly changes in drive numbering if I enable all (and unused) SATA ports. Not sure where to go from here but I wanted to post this issue in case anybody else doing a basic baremetal install is running into issues.

All hdd are connected and working fine with DSM v 5 the error starts when I put the new bootloader and try to update to v 6, with find.synology.com or the synology assitant I get the message: 'We've detected errors on your hard drives (1,2) and the SATA ports have also been disabled. Please shut down or repace or remove the hard disks to continue." again this happends on 3 baremetal servers which work fine with DSM 5 I have done data scrubbing and smart checks and the hdd and sata ports are working ok, I ask again if anyone found a solution to this? Regards

Same here, I also have "We've detected errors on your hard drives (2) and the SATA ports have also been disabled. Please shut down or repace or remove the hard disks to continue." It's a bare metal UEFI/E3815 board with wiped disks (smart ok). Any idea ? I have the same even if i remove the hdd it shows me the same error *EDIT* I got it working after a restart I could use the synology assistent to Migrate/Install with the 6.0.2-8451 but now quickconnect is not working it is working on a vm I am trying this on 3 bare metal install with precious xpenology latest 5xxx working, has anyone found a solution to this? I have tried rebooting and nothing cannot wipe since they are in production. Regards Solution to what? If it's for the error stated above then you should read the OP. It's clearly stated. Make sure to plug your HDDs in the sata ports starting from the first port, usually SATA0. For Quickconnect, this is really sad to see people trying to constantly rape Synology. Just sad.

Same here, I also have "We've detected errors on your hard drives (2) and the SATA ports have also been disabled. Please shut down or repace or remove the hard disks to continue." It's a bare metal UEFI/E3815 board with wiped disks (smart ok). Any idea ? I have the same even if i remove the hdd it shows me the same error *EDIT* I got it working after a restart I could use the synology assistent to Migrate/Install with the 6.0.2-8451 but now quickconnect is not working it is working on a vm I am trying this on 3 bare metal install with precious xpenology latest 5xxx working, has anyone found a solution to this? I have tried rebooting and nothing cannot wipe since they are in production. Regards

Setup a brand new 6.0.2.8451 from scratch and work great so far. My system Intel I7, 12G, internal marvell SATA (5 ports) and LSI SAS3081E-R 8 ports controller card. 10 hard drives, 5 connected to the internal SATA ports, and 5 connected to the LSI controller. Everything is fine and work normally. The issue is now, as soon as I add the 11th drive to the LSI controller, synology now see it as an esata drive.... is that normal? if esata, can I added them to the disk group? I change the sataportmap=58 and that did nothing. I tried other value but always detected as esata... Any suggestion? Thanks

I've managed to install original 8451 pat in Proxmox VM with Arcao uefi-boot img. (Mount qcow2 file as USB, Boot in UEFI from USB). No error 13. But after install I stuck on upgrade for now =)) Every time after reboot DSM shows me: We've detected that the hard drives of your current DS3615xs had been moved from a previous DS3615xs, and installing a newer DSM is required before continuing. Status: Upgrade required Firmware version: 6.0.2-8451 DSM version: 6.0.2-8451

Hi, did somebody successfully setup a e-sata external hard disks set (via FIS/port multiplier) ? I installed a Marvell 88SE9235, with an external x2 disks hosting box esata, and then under ESXi nothing is detected, but thanks to VT-d support I successfully configured an Ubuntu VM using the Marvell card directly, and both external disks are well managed/see, and I'm able to work on via passthrough and the 2 hard drives. Btw, hardware is well detected/configured under Ubuntu, everything is fully compatible of ESXi/VM use ... Now, I tried without success to reconfigure this external x2 disks to use as additional disks to the emulated 3615xs Synology (in addition to the 4 mains disks already configured ...). But, via passthrough to the Marvell card the 3615xs only see the 1st disk ... classicly it's a problem of driver ... Has somebody an idea how to setup/configure ? I already put a SataPortMap=42 (4 mains disks + 2 externals) Thanks !

OK... after spending few hours Saving / Recovering from a BAD upgrade, here are a few notes to keep in mind. [Less than 12 HDDs] If you have less than 12 Disk or less in your XPEnology DSM server, it's very safe to upgrade and completely painless. That being said, even if it's "safe" Make sure to Backup Your Data before you even attempt to upgrade, you never know when the universe will throw you a curve ball. [More than 12 HDDs] However! if you have more than 12 Disk in your DSM server... well get ready for some long work. There is no easy way around this, only Safety measure and best practices. 0. Make sure you have the new 5.2-5967.1 USB boot prepared and ready. (I had to create the USB twice, the first time didn't boot from the USB for whatever reason.) 1. Hot Swap eject all your HDD that are above Disk #12, so in my case I have from Disk # 13 to Disk # 24. (I should have ejected them to save myself some trouble) 2. Install or upgrade DSM 5.2-5644.5 to 5.2-5967.1 using the .pat file. 3. After you first boot back into the DSM, it'll be version 5.2-5967.1, you will have lost the settings from your synoinfo.conf, You'll be asked to also configure a few missing settings. (if you have a backup of the Synology settings file, you can restore after you bypass the menus) 5. Before you even bother editing the synoinfo.conf, it is HIGHLY recommended to upgrade the remaining disks 13 to 24 or whatever extras you have, to use the new DSM system partitions. You can use a cloning tool to only copy the system partitions from the existing upgraded volumes (any disk from 1 to 12) or You can go CYCLE your additional volumes located on Disk #13 and above. Both methods are tedious, as it require you to eject physical HDDs in volume groups to work with. I went with the Disk Cycling option, as it was a little more straightforward, but still annoying. From my disks 1 to 12, I had 2 separate volumes there, which made the job a little bit easier. When I created this server I knew and I expected this kind of trouble, so I intentionally created 1 large volume with 8 disks and a smaller volume with 4 disks, this let me easily swap the volumes in and out of the server via Hot Swap. So, I removed a full volume set of 8 disks then I proceeded to swap in the remaining Volumes that are still with the old DSM 5.2-5644.5 system partitions when you plug them in, it will be detected as Crashed, and It will ask you to Repair Repair is safe, by selecting Repair, it will update the DSM partitions to the new 5.2-5967.1 system partitions, your data will not be touched. So repeat this process a few time, until all your additional disks and volumes from Disk 13 and above are upgraded to the new DSM version. Once that is done, it'll be safe to update the synoinfo.conf to enable the additional drives. [Why?] Now, You'll probably ask WHY? not update synoinfo.conf first, and then not have to do the Hot Swap music chair? Because I tried the lazy way frst and it doesn't work, as soon as the new DSM 5.2-5967.1 boots up and detects some disks partitions are still running the old 5.2-5644.5, the DAMN thing will automatically reboot your machine to force it into Factory Default mode, then you'll be forced to do the steps 1 to 4 again, and all the hard work is gone and you need to start from scratch again. This is how I lost a few hours, when it could have been done in less than 30 min. I tried the other lazy way by adding the HDD after the upgrade, hoping it will offer you the option to "Repair" ... but nope, they will be detected as Brand NEW HDDs ("not initialized"), and you WILL lose your data if you select the option to create volume or initialize the disk. If you leave the HDDs pluged-in then it causes the endless reboot, because it keeps going into Factory Default mode. So, the only Safeway, and trouble free way, is by doing the Music Chair upgrade with the volume sets, or cloning the 5.2-5967.1 system partitions to the remaining drives.

@substorm The image i've posted (for UEFI/BIOS) already have 2 partitions (on an official synoboot, the first partition contain recovery kernel/rd and the second the running kernel/rd from last update). You can use W32DiskImager, it will create both partitions I followed the string "We've detected errors on the hard drives ({0}), and the SATA ports have also been disabled. Please shut down your {1} to replace or remove the hard drives and try again." and the error is triggered from /usr/syno/bin/synodiskport -portthawlist Someone with serial and sata error can you put the output of this command ? If sata works for you, it would be fine to put the output too .

Thanks for the new image but I get the same error as before (on bare-metal).. When accessing the synology NAS URL I get.... "We've detected errors on your hard drives (2,5,6) and the SATA ports have also been disabled." It then tells me to remove or reinstall them.. I've edited the grub.cfg to change my SN, MAC and PID but no joy.. #H

there is nothing more to see - just wait a minute or two and if your network driver is present you will see it through find.synology or in your routing table. this line confused me too until i saw the nic was reseted after a few seconds find.synology.com is detecting the device but now giving me the following error: We've detected errors on the hard drives (3, 4, 5, 6), and the SATA ports have also been disabled. Please shut down your DS3615xs to replace or remove the hard drives and try again.

Same here, I also have "We've detected errors on your hard drives (2) and the SATA ports have also been disabled. Please shut down or repace or remove the hard disks to continue." It's a bare metal UEFI/E3815 board with wiped disks (smart ok). Any idea ? I have the same even if i remove the hdd it shows me the same error *EDIT* I got it working after a restart I could use the synology assistent to Migrate/Install with the 6.0.2-8451 but now quickconnect is not working it is working on a vm