WiteWulf
-
Posts
423 -
Joined
-
Last visited
-
Days Won
25
Posts posted by WiteWulf
-
-
Thanks for all the additional info @flyride, it's really appreciated. I've got a stack of Intel PCIe cards in the office that I may have a look through to see if I can find anything matching those PCI device IDs.
-
Ah, okay, I thought the 1.04b loader and 6.2.1 were inextricably linked. Having re-read Jun's post on the topic now, I see that all non-Synology provided PCIe drivers have stopped working in 6.2.1, so you basically need a NIC with the same chipset as a "real" Synology box.
Lol, this is reminding me of when I used to have a Hackintosh and went searching for cheap Dell wireless cards with the same drivers as Apple gear 🤣
-
Ah, I was under the impression it was a CPU architecture incompatibility, rather than just a NIC driver thing. Does the 1.04b loader simply lack the drivers for the Broadcom NIC in the HP servers, then?
(I only just updated to 6.2 from 6.1.7 yesterday, so am playing catch up here)
-
I'm also curious about the future of this platform now. I've got a Gen8 with the stock G1610T Celeron CPU in it (it does what I need it to ¯\_(ツ)_/¯ ) running 6.2 U2, also, and it would be great if it was possible for Jun or QuickNick to produce a bootloader for 6.2.1 and this hardware.
Failing that, it seems my other option is to backup all my data (9TB!!!), rebuild the server as an ESXi host, and go virtual...
-
2 minutes ago, m3rlinux said:
Apparmor error
Yeah, just tailing it now and all those messages seem to have stopped, too. Job's a good'un 😉
-
Just now, m3rlinux said:
Did you get this message yet?
What message?
-
Okay, fixed it, what a pig that was!
Following saoclyph's post here:
...I started digging around in /etc. I replaced all the rc.* files with copies from the installer .pat file (it's a tar file, you can extract it and find the files you need) and also deleted an old .xpenoboot folder in root. Rebooted and I'm in to the DSM interface with no problems. Hope this is of help to others who run into the same or similar problem!
-
I'm also getting the following chunk of output repeated every few seconds in /var/log/apparmor.log
It's really quite unhappy about something, it's either not starting the DSM UI service or refusing to log me in, not sure which:
Quote019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /var/log/synopkg.log denied by profile /usr/syno/sbin/synoscgi//SYNO.Core.Desktop.Initdata
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /lib/openhook.so(+0xafb) [0x7f17d59b9afb]
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /lib/openhook.so(fopen64+0x4a) [0x7f17d59b9e9a]
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /lib/libstdc++.so.6(_ZNSt12__basic_fileIcE4openEPKcSt13_Ios_Openmodei+0x34) [0x7f17d4b10c18]
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /lib/libstdc++.so.6(_ZNSt13basic_filebufIcSt11char_traitsIcEE4openEPKcSt13_Ios_Openmode+0x36) [0x7f17d4b3415c]
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /lib/libsynopkg.so.1(_ZN15SYNOPackageTool14PMSWriteSysLogEPKc+0x19e) [0x7f17d57082ee]
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /lib/libsynopkg.so.1(_ZN15SYNOPackageTool14PackageManager20serviceControlActionENS_21PKG_INSTALLATION_TYPEERKSsbPKcS5_NS_8MSG_TYPEE+0x2f9) [0x7f17d5722e99]
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /lib/libsynopkg.so.1(_ZN15SYNOPackageTool14PackageManager19serviceControlOnOffESt6vectorISsSaISsEEbb+0x1ac) [0x7f17d5726b1c]
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /lib/libsynopkg.so.1(_ZN15SYNOPackageTool14PackageManager22serviceControlOnOffALLEbbPKcS2_+0x340) [0x7f17d5727d70]
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /usr/syno/bin/synopkg() [0x406aca]
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /usr/syno/bin/synopkg() [0x4035f6]
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /lib/libc.so.6(__libc_start_main+0xf0) [0x7f17d44fb030]
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /usr/syno/bin/synopkg() [0x40376a]
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /tmp/synopkgctl.tmp-CloudSync denied by profile /usr/syno/sbin/synoscgi//SYNO.Core.Desktop.Initdata
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /lib/openhook.so(+0xafb) [0x7f17d59b9afb]
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /lib/openhook.so(fopen64+0x4a) [0x7f17d59b9e9a]
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /lib/libsynocore.so.6(SLIBCFileSetPair+0x2e) [0x7f17d4d91f1b]
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /lib/libsynopkg.so.1(_ZN15SYNOPackageTool7Service12DumpExtraEnvERKSsNS_21PKG_INSTALLATION_TYPEEPKcS5_+0x13b) [0x7f17d57809ab]
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /lib/libsynopkg.so.1(_ZN15SYNOPackageTool14PackageManager20serviceControlActionENS_21PKG_INSTALLATION_TYPEERKSsbPKcS5_NS_8MSG_TYPEE+0xc1f) [0x7f17d57237bf]
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /lib/libsynopkg.so.1(_ZN15SYNOPackageTool14PackageManager19serviceControlOnOffESt6vectorISsSaISsEEbb+0x1ac) [0x7f17d5726b1c]
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /lib/libsynopkg.so.1(_ZN15SYNOPackageTool14PackageManager22serviceControlOnOffALLEbbPKcS2_+0x340) [0x7f17d5727d70]
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /usr/syno/bin/synopkg() [0x406aca]
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /usr/syno/bin/synopkg() [0x4035f6]
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /lib/libc.so.6(__libc_start_main+0xf0) [0x7f17d44fb030]
2019-01-08T13:39:10+00:00 diskstation synopkg: AppArmor: /usr/syno/bin/synopkg() [0x40376a]
-
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
Quote2019-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]
2019-01-08T13:29:58+00:00 diskstation synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-CloudSync (err=-1) [0x0900 file_set_pair.c:18]
2019-01-08T13:29:58+00:00 diskstation synopkg: extra_env.cpp:71 Failed to dump /tmp/synopkgctl.tmp-LogCenter [0x0900 file_set_pair.c:18]
2019-01-08T13:29:58+00:00 diskstation synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-LogCenter (err=-1) [0x0900 file_set_pair.c:18]
2019-01-08T13:29:58+00:00 diskstation synopkg: extra_env.cpp:71 Failed to dump /tmp/synopkgctl.tmp-WebStation [0x0900 file_set_pair.c:18]
2019-01-08T13:29:58+00:00 diskstation synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-WebStation (err=-1) [0x0900 file_set_pair.c:18]
2019-01-08T13:29:58+00:00 diskstation synopkg: extra_env.cpp:71 Failed to dump /tmp/synopkgctl.tmp-DownloadStation [0x0900 file_set_pair.c:18]
2019-01-08T13:29:58+00:00 diskstation synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-DownloadStation (err=-1) [0x0900 file_set_pair.c:18]
2019-01-08T13:29:58+00:00 diskstation synopkg: extra_env.cpp:71 Failed to dump /tmp/synopkgctl.tmp-EmbyServer [0x0900 file_set_pair.c:18]
2019-01-08T13:29:58+00:00 diskstation synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-EmbyServer (err=-1) [0x0900 file_set_pair.c:18]
2019-01-08T13:29:58+00:00 diskstation synopkg: extra_env.cpp:71 Failed to dump /tmp/synopkgctl.tmp-OAuthService [0x0900 file_set_pair.c:18]
2019-01-08T13:29:58+00:00 diskstation synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-OAuthService (err=-1) [0x0900 file_set_pair.c:18]
2019-01-08T13:29:59+00:00 diskstation synopkg: extra_env.cpp:71 Failed to dump /tmp/synopkgctl.tmp-py3k [0x0900 file_set_pair.c:18]
2019-01-08T13:29:59+00:00 diskstation synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-py3k (err=-1) [0x0900 file_set_pair.c:18]
2019-01-08T13:29:59+00:00 diskstation synopkg: extra_env.cpp:71 Failed to dump /tmp/synopkgctl.tmp-FileStation [0x0900 file_set_pair.c:18]
2019-01-08T13:29:59+00:00 diskstation synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-FileStation (err=-1) [0x0900 file_set_pair.c:18]
2019-01-08T13:29:59+00:00 diskstation synopkg: extra_env.cpp:71 Failed to dump /tmp/synopkgctl.tmp-StorageAnalyzer [0x0900 file_set_pair.c:18]
2019-01-08T13:29:59+00:00 diskstation synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-StorageAnalyzer (err=-1) [0x0900 file_set_pair.c:18]
2019-01-08T13:29:59+00:00 diskstation synopkg: extra_env.cpp:71 Failed to dump /tmp/synopkgctl.tmp-Plex Media Server [0x0900 file_set_pair.c:18]
2019-01-08T13:29:59+00:00 diskstation synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-Plex Media Server (err=-1) [0x0900 file_set_pair.c:18]
2019-01-08T13:29:59+00:00 diskstation synopkg: extra_env.cpp:71 Failed to dump /tmp/synopkgctl.tmp-Docker [0x0900 file_set_pair.c:18]
2019-01-08T13:29:59+00:00 diskstation synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-Docker (err=-1) [0x0900 file_set_pair.c:18]
2019-01-08T13:29:59+00:00 diskstation synopkg: extra_env.cpp:71 Failed to dump /tmp/synopkgctl.tmp-SynoFinder [0x0900 file_set_pair.c:18]
2019-01-08T13:29:59+00:00 diskstation synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-SynoFinder (err=-1) [0x0900 file_set_pair.c:18]
2019-01-08T13:29:59+00:00 diskstation synopkg: extra_env.cpp:71 Failed to dump /tmp/synopkgctl.tmp-domoticz [0x0900 file_set_pair.c:18]
2019-01-08T13:29:59+00:00 diskstation synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-domoticz (err=-1) [0x0900 file_set_pair.c:18]
2019-01-08T13:29:59+00:00 diskstation synopkg: extra_env.cpp:71 Failed to dump /tmp/synopkgctl.tmp-Java7 [0x0900 file_set_pair.c:18]
2019-01-08T13:29:59+00:00 diskstation synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-Java7 (err=-1) [0x0900 file_set_pair.c:18]
-
1
-
-
Same here, HP Gen8, baremetal, Jun's 1.02b loader. Very quick install, no reboot, only had to restart SMB
-
Just wanted to say a quick thankyou and report that this worked perfectly to update my HP Microserver Gen8 on 6.0.2 directly to 6.1.4 update 1 with no issues. Top work chaps.
-
Just wanted to say a quick thankyou to all involved in this. I've just updated from 5.2 to 6.0, bare metal on HP Gen8 with no issues whatsoever.
I decided to change the MAC address and create a "proper" serial for the box as part of the upgrade but can't get it to login to my synology account, but that's another story...
-
Never going to happen. Just like Apple, Synology is making money on selling overpriced hardware.
When you buy a Synology device, you're buying hardware, software and warranty support. The hardware appears overpriced because you can get the software and 'support' from here for free. Essentially, you're assigning 0 values to software and support in the cost = hardware + software + support equation.
Indeed...and those of you with long memories may recall the brief point in time when you could buy Apple PowerPC clones with officially licensed ROMs and copies of System 7. Apple saw their hardware sales plummet and ended the program within 2 years of it starting. The rest of the hardware industry learned a useful lesson from this!
-
Evening all, I was on the closed beta of Let's Encrypt that's now on Public Beta. They're doing some really interesting work with making SSL certificates available for free and they can be used on [sy|Xpe]nology boxes. There's no native client yet, but a chap has written up a good howto for running the client on a syno box.
https://community.letsencrypt.org/t/syn ... ity/453/15
NB. you will need access to another linux box to complete the process.
Hopefully there'll be official support for the service in future Synology releases or a community package released.
-
I'm not updating until Synology actually put up some release notes for it!
-
I just did the same as kuma16830: was already running on Update 1, installed Update 2 through the web interface, rebooted, server locked up part way through boot, reset, booted successfully. All good now.
-
-
Hmm...strange...may give it another go then. I used XPEnoboot_DS3615xs_5.2-5565.1.img to boot with
-
You mean G7 N54L only or the complete series? (N40L/N54L/N36L)?
This is a good question! I am running a N40L but am holding back until this has been clarified
I just tried booting on an HP Gen8 Microserver and had no ethernet or USB keyboard available once the login prompt was displayed. Re-loaded 5.1-5055 on the USB stick and all was back to normal. I'll wait and see how this develops but thanks for the effort so far!
-
Thanks for the heads-up. Was just about to click Go on this one (as past point releases had been safe) but thought I'd check first. Glad I did
-
See if you can find the howto for reducing CPU speed that was on xpenology.nl, I installed this on my HP Gen8 and it brings the clock speed down from 2.3GHz to 1.6GHz and will allow it to speed up again automatically on demand.
You could also look into the HDD hibernation features (ie. spinning disks down when not in use) but I'm not sure how well this works on non-synology hardware.
-
Just a quick /me too for all working installed through the web interface.
I tried it on a virtualbox VM first to check then installed for real on my HP Microserver Gen8
-
Hiya, first post so apologies if I'm stating the obvious: please note that DSM states it's disk/network throughput in BYTES per second, not BITS, so multiply your monitor readings by a factor of 8 to compare it to your LAN wire speeds.
Your stated 10-30, peaking at 42 translates to 80-240Mb/s peaking at 336Mb/s which is actually pretty good! Although you're connected to a gigabit switch the internal bus between the NIC and storage become a bottleneck on low-end hardware like the microservers.
Rusty > very impressive, you'll not get more than 80% utilisation on an ethernet network so you're maxing it out there.
HP Microservers above 6.2
in DSM 6.x
Posted
I take it that adding in an HP NC360T card to a system would still require a) "compatible" MAC addresses flashing to the adapter and b) those MAC addresses adding as parameters in grub.cfg?
There's a guy selling SFF NC360T cards on ebay at the moment for £13 so I'll give this a try...