Jump to content
XPEnology Community

Search the Community

Showing results for '"detected that the hard drives"'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Information
    • Readers News & Rumours
    • Information and Feedback
    • The Noob Lounge
  • XPEnology Project
    • F.A.Q - START HERE
    • Loader Releases & Extras
    • DSM Updates Reporting
    • Developer Discussion Room
    • Tutorials and Guides
    • DSM Installation
    • DSM Post-Installation
    • Packages & DSM Features
    • General Questions
    • Hardware Modding
    • Software Modding
    • Miscellaneous
  • International
    • РУССКИЙ
    • FRANÇAIS
    • GERMAN
    • SPANISH
    • ITALIAN
    • KOREAN

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 22 results

  1. Please help! I was updating my BAREMETAL - Microserver Gen8 that ran DSM 7.0.1 DS3622xs+. I've read the forum and made the following: in DSM 7.0.1 gui I manually updated to 7.2.0 waited 10+ min, it hasn't rebooted but hasn't accessed HDD either so I manually rebooted it (possibly my mistake) loaded onto TCRP (no friend) run the following ./rploader.sh clean ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh build ds3622xsp-7.2.0-64570 withfriend (also run on another attempt w/o friend) exitcheck.sh reboot On the first try I after reboot got Loading Linux error: premature end of file /bzImage-friend. checked the sd-card, it had 67% filled rebooted to loader gui and repeated now after reboot the system shows a 'normal' start (i.e. like before the update, see screen) but the system doesn't access HDDs, only connection. The local ip-address of my old DSM isn't used, but another is used. There is 'SynologyNAS' device but under that new address and old port I cannot access it. I used Synology assistant and it shows that the system is 7.2.0 and 'recoverable' when I connect it says We've detected that the hard drives of your current DS3622xs+ had been moved from a previous DS3622xs+, and installing a newer DSM is required before continuing. what should I do?
  2. Hi Flyride, today I tried to restart it, I don't know how and why it gave me internal ip to the lan and then it connects me, only it tells me, in addition to the welcome back it has detected that the hard drives have been moved to a new one 918+, click on “overlay” to recover the data and settings. Except that when I do it, he executes a command that I don't know then gives me 10 minutes to wait and in the end he gives me that he wasn't able to execute and try again. I guess I busted everything, I had read in some threads about problems with disk mapping but I can't find it
  3. Hi guys, Thanks for this thread. I would like to share experience which is a little bid different. The story is that my HP N54L 6.2.1-23824 suddenly cannot be found on the network one day. Then I build another 1.03b DS3615xs USB stick, unplug all FIVE drives and insert an empty one (called A) at port 1. Installed and upgrade to 6.2.3-25426, then plug the old 2 3 4 5, got a message saying CRASH / DEGRADED. Then I click Repair which works very quick, then I shutdown and unplug A and plug 1, boot with the ANOTHER USB stick. Then I got the Welcome Back! screen 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" Status : Upgrade Requred Firmware version: 6.2.3-25426 DSM version: 6.2.1-23824 Therefore I click Install and then Reinstallation: Re-install DiskStation and keep my data... Then manual install DSM_DS3615xs_25426.pat and click Install NOW. Then Create an administrator account for this DiskStation (I think the rest should be standard procedure) Then I need to Repair the Degraded Storage Pool 1. I wonder how long 5 x 3T hard drives need to work on Repair (Checkin Parity Consistency) Thank you very much again. P.S. I did try Redpill Tinycore and did installed DSM 7.0.1 on empty drive A. But seeing only the interface beautify and ease of implementation, I think I will install the last stable version of DSM6.2.3 update 3 for now on this relatively new N54L.
  4. Hi all, DSM gets "continually broken" (I mean, I fix it but then it gets broken again) after a Proxmox 6 to 7 upgrade. Jun's loader shows (serial terminal): "lz failed 9 alloc failed Cannot load /boot/zImage" But please, let me first explain all details and read until the end because the situation is very strange... I'm using JUN'S LOADER v1.03b - DS3617xs in a Proxmox VM (on HP Gen8), with DSM 6.2.3-25426. I've been using this config for months without any problem on Proxmox **6.x** (this seems relevant). The other day I decided to upgrade Proxmox to **7.x**. I upgraded Proxmox and rebooted. All my VMs booted up perfectly... except DSM one I observed that I couldn't reach my network shares at DSM, and after a quick investigation, I discovered that DSM booted up in "installation mode", showing this message in web interface: "We've detected that the hard drives of your current DS3617xs has been moved from a previous DS3617xs, and installing a newer DSM is required before continuing.". I thought DSM partition may have been corrupted in some way or (most likely) Proxmox 7 introduced kind of a "virtual hw change" so now DSM thinks it's been booted in another hw. This last option is very plausible because Proxmox 7 uses qemu 6.0, while Proxmox 6 (latest) uses qemu 5.2. Maybe other changes in new version of Proxmox could have been introduced (for instance, I've read something regarding assigned MAC of a bridge interface being different). What I did was: 1/ Power off DSM VM. 2/ Back up partition 1 for all my 4 disks (i.e the md0 array which contains DSM OS). 3/ Power on DSM VM. 4/ I followed instructions in the web interface, chose "Migrate" (which basically keeps my data and config untouched), selected a manual installation of DSM and uploaded the .pat corresponding to the very same version I was already running before the problem, i.e. DSM_DS3617xs_25426.pat (DSM 6.2.3-25426). I didn't want to downgrade, and of course, I shouldn't upgrade because next version is 6.2.4, which is incompatible with Jun's loader. 5/ Migration got finished, DSM rebooted and... FIXED!!! DSM was working again with no loss of data nor config. *But* another problem arised later... When my server (Proxmox) got rebooted again, DSM VM resulted broken again but this time in a very different way: I couldn't ping my DSM VM, and after investigation, I concluded DSM kernel was not being loaded at all. Indeed, I attached a serial terminal to DSM VM and I could see Jun's loader being stuck at the very beginning with these messages: "lz failed 9 alloc failed Cannot load /boot/zImage" No idea why this is happening nor what these messages really mean (well, it seems obvius kernel is not being loaded but I don't know why) !! I managed to fix it again (yeah xD) by: 1/ Power off DSM VM. 2/ Restore partition 1 for all my disks from just the backup I took when solving former problem 3/ Power on DSM VM 4/ I confirmed loader worked again and that I got to the same point where DSM needed a migration 5/ I "migrated" exactly in the same way I had done minutes before :). FIXED!! What's the problem then? Easy... every time I reboot my server (so Proxmox reboots), my DSM VM got broken again with the second error ("lz failed... etc), i.e, loader's kernel not being loaded. I could temporarily fix it but sooner or later I'll need to reboot Proxmox again and... boom again Any of these problems are familiar to you? Any clue about how to solve this or a least, some ideas I should focus my investigation on? PLEASE, help!! :_( PS: My Proxmox VM config (a.k.a. qemu config) (with some info redacted): args: -device 'nec-usb-xhci,id=usb-ctl-synoboot,addr=0x18' -drive 'id=usb-drv-synoboot,file=/var/lib/vz/images/100/synoboot_103b_ds3617_roman.img,if=none,format=raw' -device 'usb-storage,id=usb-stor-synoboot,bootindex=1,removable=off,drive=usb-drv-synoboot' -netdev type=tap,id=net0,ifname=tap100i0 -device e1000e,mac=00:XX:XX:XX:XX:XX,netdev=net0,bus=pci.0,addr=0x12,id=net0 bios: seabios boot: d cores: 4 cpu: IvyBridge hotplug: disk,network,usb memory: 2048 name: NAS-Synology numa: 0 onboot: 1 ostype: l26 sata0: /dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4NXXXXXXX,size=2930266584K sata1: /dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4NYYYYYYY,size=2930266584K sata2: /dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4NZZZZZZZ,size=2930266584K sata3: /dev/disk/by-id/ata-WDC_WD40EFRX-68N32N0_WD-WCC7KAAAAAAA,size=3907018584K scsihw: virtio-scsi-pci serial0: socket smbios1: uuid=9ba1da8f-1321-4a5e-8b00-c7020e51f8ee sockets: 1 startup: order=1 usb0: host=5-2,usb3=1
  5. We have just had a major power cut, followed by 3 spikes - on - off The Boot USB is no longer seen by the motherboard. I created a new one, it boots, but ... DSM 6.1.4-15217 Update 1 DS3615xs The message onscreen says 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 Is it safe to click on INSTALL
  6. Hi, I was curious as to how you got on? I have an HP ProLiant Gen8 G1610T MicroServer running on 6.0.2 and want to upgrade to 6.2.2 so followed the same steps you had above but in step 3e it didn't let me choose "migrate". It told me "We've detected that the hard drives of your current DS3615xs have been moved" and told me I needed to do an install. I'm worried that with an install I will lose all my settings and setup, so I aborted. Do I need to go to 6.1.x first and from there go to 6.2.2? Thanks.
  7. Hi all - first post, so apologies if it is in the wrong section. I've been running XPEnology on a HP Gen8 Microserver for a number of years and all has been going well. I have always had the auto-updates disabled so I don't believe anything has changed on the NAS. However, this morning when trying to connect to my NAS it had an error message asking me to Install - "We've detected that the hard drives of your current DS3615xs had been moved from a previous DX3615xs, and installing a new DSM is required before continuing" (see attached screenshot). If I select "Install" then I am given two options: (1) Migration or (2) Reinstallation. Which one should I choose? If any? As I am concerned that the latest DSM may be downloaded which could be incompatible with my system and end up making things worse. It also seems I can do a manual install and provide my own image. Again, is this a better option? Can't remember the exact version of Jun's loader, but think it is 1.03b (am trying to find out, but can't access my ILO at the moment). Thanks for any guidance.
  8. Hi All, My subject title could be misleading but could be related. My DSM 6.1.4-15217 Update 5 seems to have crashed or something has gone wrong. I did the update a little while ago and everything has been fine (including the reboots) until my last reboot a couple of nights ago. Now the Xpenology comes back online but seems to have lost its static IP address and getting a new DHCP address. I cannot access it via telnet or SSH but through a web UI. It is asking to "Install" with the message, "We've detected that the hard drives of your current DS3617xs had been moved from a previous DS3617xs ...". Please see attached screenshots (I tried but cannot seem to upload images. Will keep trying). Could anyone please help me with some guidance: 1. Is there any fix or workaround for this issue? 2. What would happen if I went ahead with the installation? Would I lose all of my data and settings etc.? Please note my setup: Xpenology as a VM in an ESXi 6.5 host Physical Box: HP Microserver Gen8 DSM 6.1.4-15217 Update 5 Memory: 4GB June's loader 4 virtual hard drives Happy to share more details are required. Thank you!
  9. hi been using 5.2 for a while, on baremetal and now switched over to ESXI setup in esxi, 1 virtual disk (dsm & apps located) , passthroughd my sata controller for my other 4 disks that contains data now 6.1 so i create a new VM, give it again 1 virtual disk, i install DSM 6.1 , working perfect so far now i attach my sata controller again in passthrough to gain access to my data now when in boot DSM6.1 i have this warning 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 is it safe to proceed? probably there is stuff on a hidden partition on it, do i loose data? since i have esx, i have tried to replicate this when creating a new 5.2 with virtual disks, then attach those virtual disks to a new clean 6.1 install, but i dont get that warning anymore thnx again
  10. 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.
  11. 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.
  12. 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
  13. 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?
  14. 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?
  15. fosi

    DSM 6.1.x Loader

    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
  16. 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?
  17. lazygatto

    DSM 6.1.x Loader

    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
  18. I currently have a similar problem. firstly I am a Newb in all this My son setup the original EXPenology site for me and is currently unavailable to help. I am computer literate and can follow directions... here is my dilemma! something I have done has caused my site to become unavailable on my network...( it was probably me...however I dont know what caused the problem nor do I know how to fix it!) anyway... I found that when booting up fromUSB it would stall at this: Excution Error ============Date============ Sat June 11 14:44:55 UTC 2016 =========================== DiskStation Login: (Execution is mis-spelt.) I created a new USB Boot using the latest 5.2-5645.5 image, and I picked up on the forum how to apply Synology Helper and got the following message: 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. Device Info: Model DS3615xs IP Address: 10.1.1.25 Serial Number: C8KWN00266 Mac Address: 00:11:32:16:24:26 Status: Update required Firmware version: 5.2-5644 DSM version 6.0-7393 I can see that there is something wrong here but I need help on how to fix it Thanks Peter
  19. Hi, I have an HP Proliant that I installed DSM 5.2 on a while ago. Everything has been running smoothly until tonight, when I tried to log on it loaded up the web assistant saying "Welcome back, we've detected that the hard drives of your current Ds3615xs had been moved from a previous DS3615xs, and installing a newer version of DSM is required before continuing". Has anyone ever encountered this? I'm not sure how to proceed as I don't want to loose all my data and setup. I can't get into the web interface to back anything up. Thanks.
  20. I need some help / assistance here!! I stupidly left the XPEnology Diskstation to auto update and its updated itself, all I get now when I log into the Diskstation via the Web Assisant is; "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" Device info; FW 5.2-5644 DSM Ver; 6.0-7321 I've tried to install via the Web Assisant, nothing seems to install, I just go back to the above message on rebooting If i check the status via Synology Assistant it reports as "Migratable" I've also hooked up a monitor to the diskstation but cant log in, the keyboard doesnt seem to work. I dont even think SSH is enabled either; help anyone!!
  21. Hey guys, just wanted to confirm that these instructions also work for those who have xpenology under esxi. Mine updated on its own over the weekend and I was able to restore it back following these instructions. Many thanks to the original poster. It's even easier in esxi because you get to see what ip address synology gets reset to in console and your don't need putty. It can all be done in vsphere client. Mine wasn't even booting into 6.0 as it kept saying that "We've detected that the hard drives of your current DS3615xs had been moved..." I chose the 2nd option under installation prompt, but don't worry it won't format your drives. I don't think 6.0 can get access to your drives if you are using xpanoboot anyway. I let it download the files on its own because it wouldn't accept any of my pat files. Once you set your admin account your can just follow the instructions from here from the console. The 2nd time it let me use my old pat files. And yes use sudo su and vi. If you are using a different bootloader, I can't say this method will work. You can always create a new VM and use your old disk images.
  22. Ok, so I update to 5.2 and no matter what I do I can't get rid of 5.2. I'm ok if I have to lose the data on my drives. On the Web GUI, under the Install button, is says, "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." then a Device Info link, which opens a small window with some info.. including: Status: Update Required Firmware: 5.1.5022 DSM: 5.2.5565 I've tried to unplug some of my drives, change the order of how they were plugged in, but nothing seems to work. I boot from a ssd drive and have pulled that and put a fresh copy of the img on it, but again nothing seems to work. Anyone got any ideals? Thanks, Kevin
×
×
  • Create New...