naasking

I had an older spare AMD mobo and mini server chassis with hot swap bays and a PCI SATA card similar to the one in my server, so I loaded it up fully with old drives and tried to install the latest M-shell on that using DS3622xs+ and that went great. Still no dice on my real server though. I even tried to launch the getty console, but that failed too. It registered my "g" but then immediately went to boot the kernel:

Do you mean this one, 1.0-beta3?

Tried again with arpl and the newest version of m-shell but this time with the DS3622xs+ version, same issue. Machine doesn't show up on the network although the screen does say it obtains the right IP. There must be something consistently going wrong here or some step I'm missing. Any suggestions?

Ok, M-shell got pretty far with DS3615xs. It installed and seemed to boot but the machine doesn't show up on the network after waiting for about 10 mins, either via find.synology.com or the synology assistant. The screen shows the attached. It does get an IP since I was able to connect briefly to the web terminal described in the attached screen pic. I tried setting up an image for the DS3622xs+ just to see if it would boot properly. I didn't see the "ERROR: Could not get IP" error in the screenshot, but the machine is still not reachable via either find.synology.com or the synology assistant. I'm not sure what to do from here.

Thanks for the clarification Peter, I do have a PCI SATA III card installed for one of the drives, so I assume that meets the HBA criteria and I can't use device tree. I hadn't come across the M shell option, thanks. I've just been using the standard TCRP install tutorial, and that seemed to succeed in building but failed on boot in grub with that grub option issue I showed above. I'll give M-shell a try tonight.

I tried the ARPL loader, and it seemed to successfully install but I couldn't find the system on the network and it just seems to randomly reboot. Maybe that's the instability issue that was described. It's looking like I might be in the unfortunate position that I have to install DS3622xs+ and setup my services again. 😕 Will switching editions affect my files at all? Edit: I suppose I can do an HDD migration to minimize the headaches, and then I might just have to setup the Let's Encrypt certificates from scratch, and maybe I can restore the mail server setup with HyperBackup.

I've tried this TCRP process twice now for my hardware, and both times grub fails to load after the last ``exitcheck.sh reboot`` step. I see a "grub_disk_native_sectors not found" error. See attached image. The first attempt I did the optional backup steps on step 7, the second time I did not, same outcome.

What is "HBA"? I tried searching for that term in the forum but it didn't turn up any results.

Thanks, I would but this install is running some services that wouldn't be convenient to have to setup again at this time. From my understanding I can only migrate to the same edition without having to set everything up again, or have I misunderstood something?

So it turned out to be the eSATA port. I basically had to disable it entirely in the UEFI firmware for TCRP to to build. Now the only issue I have is that some extensions don't seem to work for my architecure, DS3615xs. Currently "redpill-acpid", and "hv_netvsc" fail during build.

I tried a dry run of the TCRP setup on my server hardware, and while it detected all of my drives it said 1 port of 6 ports was bad and that DSM install would fail. My motherboard has 5 internal SATA ports and 1 eSATA port, so is that the "bad" port? I have my setup from my DSM 6.2.3 install that I can use as a reference if there's a simple mapping to the new setup.

After reading DSM 7.x overview, I don't understand what it means if a configuration does not list "direct platform migration from 6.2.x". I have a DSM 6.2.3 system running on AMD 3615xs. The 3615xs and 3617xs both list direct migration, but the recommended DS3622xs+ replacement does not, and I don't know what that means. Does that mean that I can't perform an upgrade to 7.1 from my current configuration and resume all system functions? I would have to do some kind of complete reinstall/rebuild? Also, 7.x has some changes that make a couple of packages I use incompatible, so I'm thinking of just upgrading to 6.2.4 for now. Is the process basically the same and I just use the 6.2.4 image in place of the 7.x images when setting up the new system?

Sorry for the duplicate posts, the interface wasn't updating so I wasn't sure what was going on and I can't seem to delete the dupes.

I don't understand what it means if a configuration does not list "direct platform migration from 6.2.x". I have a DSM 6.2.3 system running on AMD 3615xs. The 3615xs and 3617xs both list direct migration, but the recommended DS3622xs+ replacement does not, and I don't know what that means. Does that mean that I can't perform an upgrade to 7.1 from my current configuration and resume all system functions? I would have to do some kind of complete reinstall/rebuild? Also, 7.x has some changes that make a couple of packages I use incompatible, so I'm thinking of just upgrading to 6.2.4 for now. Is the process basically the same and I just use the 6.2.4 image in place of the 7.x images when setting up the new system?

I don't understand what it means if a configuration does not list "direct platform migration from 6.2.x". I have a DSM 6.2.3 system running on AMD 3615xs. The 3615xs and 3617xs both list direct migration, but the recommended DS3622xs+ replacement does not, and I don't know what that means. Does that mean that I can't perform an upgrade to 7.1 from my current configuration and resume all system functions? I would have to do some kind of complete reinstall/rebuild? Also, 7.x has some changes that make a couple of packages I use incompatible, so I'm thinking of just upgrading to 6.2.4 for now. Is the process basically the same and I just use the 6.2.4 image in place of the 7.x images when setting up the new system?