Morning all, got a bit of a weird one here. I've just upgraded to 6.2 (23739) but can't login to the DSM web interface and my system seems to have changed from a static IP to DHCP. More detail below:
The system is a baremetal install on an HP Gen8 Microserver. It was running Jun's boot loader v1.02b and DSM 6.1.7-15284 Update 2.
Using this as a guide (https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/) I created a new USB stick with "Jun's Loader v1.03b DS3615xs". I update the VID, PID, serial number and MAC addresses in grub.cfg as detailed in the guide, flashed it to the USB stick and booted up with the new USB stick in place of the old one.
The system soon showed up in Synology Assistant as "migratable" system so I opened the web page, chose to keep settings and data, and gave it the "DSM_DS3615xs_23739.pat" file to update to. I wanted to take it to 6.2 first, then upgrade to 6.2.1.
As far as I could tell the install worked okay, the system rebooted and I soon received a few emails from the system telling me about turning on SMART monitoring and warning me that I was running out of disk space. However, the system seems to have stayed on DHCP, using the IP address it acquired during the upgrade phase and not using the static address it was configured with previously. I can browse to the login page for DSM using the DHCP address and enter my username (or admin account name) and password and it seems to accept either, but I get a "Loading..." message and never get the UI.
Spoiler
If I refresh the page I just get a plain white page. I can, however, SSH into the system using my regular account and admin. Services appear to be running: Plex is accessible on the DHCP address, as is LibreNMS (which is running in a docker container on a bridged network on the server).
I next put in a DHCP reservation on my router to ensure the server got the IP address it /was/ configured with staticly. That worked, it's now on the old IP address, but I still can't login to DSM.
Digging a bit deeper, I tail'd /var/log/messages and get the following messages repeating every few seconds. So it looks like there's a permissions error somewhere in /var/packages and /usr/local/rc.d, but I don't know what it is. The HDDs in the system sound very busy, but from looking at the output from 'top' that's just Plex doing a library scan ¯\_(ツ)_/¯
Help, please!
*edit* the output below in /var/log/messages only begins appearing *after* I try to login to DSM. If I log in via SSH I can see that /var/log/messages is pretty quiet until I try to login to the web UI
*edit* /usr/local/etc/rc.d had nothing in it but a old init script to turn on CPU frequency scaling. I've deleted that but am still seeing the same messages
Quote
2019-01-08T13:29:58+00:00 diskstation synopkg: pkgtool.cpp:2284 chmod failed for /var/packages (Operation not permitted)
2019-01-08T13:29:58+00:00 diskstation synopkg: pkgtool.cpp:2293 chmod failed for /usr/local/etc/rc.d (Operation not permitted)
2019-01-08T13:29:58+00:00 diskstation synopkg: extra_env.cpp:71 Failed to dump /tmp/synopkgctl.tmp-CloudSync [0x0900 file_set_pair.c:18]
Question
WiteWulf
Morning all, got a bit of a weird one here. I've just upgraded to 6.2 (23739) but can't login to the DSM web interface and my system seems to have changed from a static IP to DHCP. More detail below:
The system is a baremetal install on an HP Gen8 Microserver. It was running Jun's boot loader v1.02b and DSM 6.1.7-15284 Update 2.
Using this as a guide (https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/) I created a new USB stick with "Jun's Loader v1.03b DS3615xs". I update the VID, PID, serial number and MAC addresses in grub.cfg as detailed in the guide, flashed it to the USB stick and booted up with the new USB stick in place of the old one.
The system soon showed up in Synology Assistant as "migratable" system so I opened the web page, chose to keep settings and data, and gave it the "DSM_DS3615xs_23739.pat" file to update to. I wanted to take it to 6.2 first, then upgrade to 6.2.1.
As far as I could tell the install worked okay, the system rebooted and I soon received a few emails from the system telling me about turning on SMART monitoring and warning me that I was running out of disk space. However, the system seems to have stayed on DHCP, using the IP address it acquired during the upgrade phase and not using the static address it was configured with previously. I can browse to the login page for DSM using the DHCP address and enter my username (or admin account name) and password and it seems to accept either, but I get a "Loading..." message and never get the UI.
If I refresh the page I just get a plain white page. I can, however, SSH into the system using my regular account and admin. Services appear to be running: Plex is accessible on the DHCP address, as is LibreNMS (which is running in a docker container on a bridged network on the server).
I next put in a DHCP reservation on my router to ensure the server got the IP address it /was/ configured with staticly. That worked, it's now on the old IP address, but I still can't login to DSM.
Digging a bit deeper, I tail'd /var/log/messages and get the following messages repeating every few seconds. So it looks like there's a permissions error somewhere in /var/packages and /usr/local/rc.d, but I don't know what it is. The HDDs in the system sound very busy, but from looking at the output from 'top' that's just Plex doing a library scan ¯\_(ツ)_/¯
Help, please!
*edit* the output below in /var/log/messages only begins appearing *after* I try to login to DSM. If I log in via SSH I can see that /var/log/messages is pretty quiet until I try to login to the web UI
*edit* /usr/local/etc/rc.d had nothing in it but a old init script to turn on CPU frequency scaling. I've deleted that but am still seeing the same messages
Link to comment
Share on other sites
7 answers to this question
Recommended Posts