mckaycr

One server was a fresh install, and the other I migrated only had hyperbackup running on it. No issues.

Shot you a private message with a link to the image I used.

If you'd like I can share my image with you, you would just need to change the MAC Addresses and the Serial, everything else should boot right up

Hardware: Dell PowerEdge R410 with 6.2.2 24922 DSM version DSM Version: 6.2.2 24922 Update 4 Install Method: Migration from 6.1.7.51284 Results: Success Notes: I migrated from from DS3615xs 6.1.7.51284 to DS3617xs 6.2.2 24922 for no real reason, just wanted to try. All data was successfully migrated as well.

- Outcome of the update: SUCCESSFUL - DSM version prior update: 6.1.3-15152 Update 7 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: Baremetal - Additional comments: REBOOT REQUIRED - Failing HHD prior to update, not recognized after update resulting in a degraded volume. Most likely unrelated to update.

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5-15254 Update 1 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: YES - extra.lzma for DS3615 v4.7 from IG-88 - Installation type: DELL PowerEdge T410 (Intel Xeon CPU E5520 @ 2.27GHz) - Additional comments: REBOOT REQUIRED

Has anyone built an image that works with openstack? Based on other threads I have read, DSM is incapable of seeing virtual disks during the install. I have also seen that with the write smarts (that of which I don't have) the kernel can be modified to see virtual disks. So I'm wondering if anyone has attempted this successfully and posted their results?

I had a similar issue. I found that removing all drives except the one where the system partition uses during the setup wizard allowed the install to finish. Then once the system boots successful, add the additional drives and create your volumes. I can't tell you why this worked, but I saw this on three different servers I built, all different models. Sent from my SAMSUNG-SM-G920A using Tapatalk

nevermind. I'm a noob

I have a system that I can ssh into, but that's about it, caused by a degraded volume. I got all my data off of it, now I want to do a fresh install and start from scratch. I have tried Jun's 1.0.2b reinstall option, but that didn't really do much. I'm wondering if I need to delete the current system partition?

Ok, well the recovery finished, and the web interface for my NAS automatically became available. Guess I just needed to be patient.

I ssh'd into my system and found the hard drives with parted -l and I also found /dev/md2 like this Error: /dev/md2: unrecognised disk label Model: Linux Software RAID Array (md) Disk /dev/md2: 2986GB Sector size (logical/physical): 512B/512B Partition Table: unknown Disk Flags: Is there anyway I can put this array back together? I followed the suggested instructions and got this mdadm: Found some drive for an array that is already active: /dev/md/0_0 mdadm: giving up. mdadm: No arrays found in config file or automatically which doesn't resolve anything. UPDATE: I just ran cat /proc/mdstat and it shows md2 undergoing recovery, I'm going to wait for it to finish and see whats what.

I never touched the original drives though, I only added more, I'm not sure how the original drives would be out of order, but I'll give it a try and see what happens Sent from my SAMSUNG-SM-G920A using Tapatalk

I added some drives to my system, rebooted and now the system wont start. Synology assistance says its ready, I can SSH into the system and see that all my data is missing. I removed the drives I added, rebooted again, same thing. Any suggestions?

Great guide, I was able to follow it to success except for the update to 4528. Getting a error 21 or something. Anyway my question is actually about the boot process, how do I move the boot from the USB to the computers hard drive? I'm sure this is probably outlined on another thread, but I can't seem to find it.