Jump to content
XPEnology Community

zugu

Rookie
  • Posts

    7
  • Joined

  • Last visited

Everything posted by zugu

  1. Thanks so much for the help! I found the culprit: in order to hide the third Grub menu entry, I commented the line in grub.cfg, but I did not also comment the following lines, so they were being executed.
  2. I think I used Notepad instead of Notepad++ and that might have caused the problem. I'll definitely use WOL, so I'll also change the MAC. Curious thing, before performing the change, two of the USB stick partitions were visible and accessible in DSM, but after updating grub.conf they're not visible anymore. (This is how I was actually able to access the file and make the change.) How can I access the USB stick now?
  3. I know it doesn't make sense, but it is how it is. Installation: baremetal on Intel Celeron G1820 on an Asrock H81M-DG4 motherboard with 4 GB DDR3 RAM. Two Seagate HDDs, 160GB and one IronWolf Pro 4TB. I flashed Jun's v1.03b Loader for DS3615xs on a 4 GB Kingston DataTraveler USB stick using Balena Etcher, but I could not find the DiskStation at all in the network. Jun's 1.04b Loader for DS918+ worked and the DiskStation was found, but I got an error which was solved by changing SataPortMap to 2 in the grub config. I proceeded to install DSM 6.2.3-25426 for DS918+ (don't know why I did not go straight for Update 3). Got an error towards the end of the installation: Installation ERROR - The file is probably corrupt. (13). I double checked the PID and VID of the USB stick and there was no issue there; but I used a grub prompt to add them again, along with other commands: vid 0x0951 pid 0x1666 append SataPortMap=2 boot and the error went away. The installation succeeded, but when I tried to reboot, the web interface would not come up. The only thing shown on a locally connected monitor would be a blinking cursor. But inputting the commands again resulted in a successful boot. Through elimination, I found out the first three commands are not actually needed, but the boot command is absolutely required. So now, in order to be able to successfully boot, I press the c key and type in boot after every restart. Everything else works smoothly, this is the only thing nagging me.
  4. If I choose that option, the DSM never properly boots. If I type boot at the grub CLI, it works. I would really like to be able to reboot without assistance, a keyboard and a monitor.
  5. It's just that, a blinking cursor in the top left of a black screen. The web interface does not become available. If I type boot in the grub terminal though, I also get a blinking cursor on the next line below the boot command, but DSM web UI becomes available in 20 seconds or so.
  6. Hello! I've installed DSM 6.2.3 on an old Haswell Celeron PC and after some fiddling, I managed to get everything working. I used the DS918+ as a platform, and Jun's 1.04b Loader. The funny thing is, if I reboot the PC and I do not intervene, the first menu entry is automatically selected and I get the dreaded blinking cursor. The only way I can boot is to invoke a grub command line by pressing the c key while the boot options are present on the screen and type: boot Of course, I would like to be able to boot without resorting to typing this command. Can anyone help me with this?
×
×
  • Create New...