Jump to content
XPEnology Community

naasking

Member
  • Posts

    49
  • Joined

  • Last visited

Everything posted by naasking

  1. 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:
  2. Do you mean this one, 1.0-beta3?
  3. 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?
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. What is "HBA"? I tried searching for that term in the forum but it didn't turn up any results.
  9. 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?
  10. 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.
  11. 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.
  12. 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?
  13. 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.
  14. 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?
  15. 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?
  16. 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?
  17. I'm running DSM 6.2.3-25426 Update 3 on an AMD CPU, and I'm trying to setup octoprint on my NAS. My understanding of the setup on DSM is roughly as follows: Install octoprint via docker image (done and running) Download the octoprint docker settings in .json format (done) Change the "devices" to point to the ttyUSB device for the printer. (problem) Import the settings and restart the container. Straightforward, but my DSM apparently doesn't have the USB serial drivers because the ttyUSB device never appears. lsusb shows: |__usb1 1d6b:0002:0310 09 2.00 480MBit/s 0mA 1IF (ehci_hcd 0000:00:12.2) hub |__1-3 f400:f400:0100 00 2.00 480MBit/s 200mA 1IF (SanDisk' Cruzer Fit 4C530000261002111053) |__usb2 1d6b:0002:0310 09 2.00 480MBit/s 0mA 1IF (ehci_hcd 0000:00:13.2) hub |__usb3 1d6b:0002:0310 09 2.00 480MBit/s 0mA 1IF (ehci_hcd 0000:00:16.2) hub |__usb4 1d6b:0001:0310 09 1.10 12MBit/s 0mA 1IF (ohci_hcd 0000:00:12.0) hub |__4-2 04f2:1060:1400 00 2.00 1.5MBit/s 100mA 2IFs (CHICONY USB Keyboard ffffffd0ffffffa2ffffffc3ffffffac) |__usb5 1d6b:0001:0310 09 1.10 12MBit/s 0mA 1IF (ohci_hcd 0000:00:13.0) hub |__5-2 0764:0501:0200 00 2.00 12MBit/s 2mA 1IF (CPS CP1500AVRLCDa CTHLQ7002009) |__usb6 1d6b:0001:0310 09 1.10 12MBit/s 0mA 1IF (ohci_hcd 0000:00:14.5) hub |__usb7 1d6b:0001:0310 09 1.10 12MBit/s 0mA 1IF (ohci_hcd 0000:00:16.0) hub |__usb8 1d6b:0002:0310 09 2.00 480MBit/s 0mA 1IF (xhci_hcd 0000:07:00.0) hub |__8-1 058f:9254:0312 09 1.10 12MBit/s 100mA 1IF (ALCOR Generic USB Hub ffffffd6ffffffa3ffffffebffffffcb) hub |__8-1.1 1a86:7523:0264 ff 1.10 12MBit/s 98mA 1IF ( ffffffd8ffffffb9ffffffd0ffffffa2) <-- this is the printer |__8-1.3 064e:d104:0110 ef 2.00 12MBit/s 500mA 2IFs (SuYin USB 2.0 Camera CN031B-M08C-MI012-VS-R01.01.00) |__usb9 1d6b:0003:0310 09 3.00 5000MBit/s 0mA 1IF (xhci_hcd 0000:07:00.0) hub |__usb10 1d6b:0002:0310 09 2.00 480MBit/s 0mA 1IF (xhci_hcd 0000:08:00.0) hub |__usb11 1d6b:0003:0310 09 3.00 5000MBit/s 0mA 1IF (xhci_hcd 0000:08:00.0) hub I've identified the Marlin printer in the text above. The thread I linked above suggests missing drivers, and they link to this github which provides builds for USB serial drivers for DSM 7, but these likely won't work for a DSM 6 xpenology install. Before I go down the rabbit hole in setting up a dev environment to maybe build some drivers myself, is there a better option? For instance, if the status of DSM 7 loaders is fairly solid now, perhaps I should just upgrade and try to use the prebuilt drivers from that github. Or perhaps there's a simpler option I'm just missing? Yes, I could just setup a raspberry pi, but I have an overpowered NAS sitting right next to the printer doing very little, so I'd rather just make use of it than waste new hardware on a simple task like this. Any suggestions appreciated.
  18. Presumably the certificate feature on DSM is using some programs like curl to download and validate the certificates. Is it possible to just build new statically linked versions of these tools and replace the stock binaries just to get Let's Encrypt certificates working again on older DSM versions?
  19. No, never found a solution. Strange that it still seemed to work running ordinary Linux, just not under DSM.
  20. Well, a fresh install seems to have done the trick. My previous configuration had been updated since DSM 5.1ish, so some errors had to have crept in over time.
  21. I'm running into exactly this error. Had DSM 6.2 running fine on this exact same hardware to backup my old server, then swapped the old server disks into this machine and migrated. Everything seemed fine except accessing DSM and ssh simultaneously kills the network and all network services, and I see these syslog errors everywhere. I've tried a reinstall with a different USB drive and the same flash image, same problem. I just tried a brand new flash drive with a freshly constructed flash image, as I thought perhaps the image itself got corrupted, but the problem remains. I think at this point whatever the problem is, it must be on the system partitions and it must somehow persist across reinstalls. Unless anyone has any other suggestions, I might have to do a completely fresh reinstall instead of trying to preserve all of my settings.
  22. The guides lately have been pretty helpful, but I have to say I'm still confused at how this works, or why certain apparent inconsistencies happen. For instance, I'm setting up a new machine with the 1.03b loader and the 6.2 series for the 3615. Jun's loader runs fine and I can load the installation page (http://find.synology.com) and setup the machine, but on reboot after installing the .pat file, it's no longer reachable on the network. Why would the installation load with the correct network driver, but the later step fail to load? Edit: I figured it out, on reboot the system was booting from the USB using UEFI. I had to disable all UEFI booting in the firmware to use 3615 with 6.2. One real bummer though is that hybrid raid/shr no longer seems available in 6.2 for the xs series.
  23. I have a working DSM 6.1 installation using jun's 1.02b on an AMD E-350 system, and I'm trying to see if DSM 6.2 with the new new jun 1.04b and 1.03b loaders are compatible. I've followed the typical instructions but upon selecting the right option from the grub menu, the machine immediately restarts. I assume this is because they aren't compatible, or is it perhaps only because there's a driver missing. Is there an extra.lzma with more drivers for these loaders?
  24. Is it possible to move a DSM volume to a new machine by moving over all of the disks? If so, what are the steps? For instance, does the new motherboard need the same number of SATA ports and I have to plug in the drives in the exact same slots on the new board?
×
×
  • Create New...