• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by WiteWulf

  1. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2-23739 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Gen8 Microserver - Additional comment: internal NIC disabled and compatible Intel PCIe NIC installed
  2. Hey all, belated follow up to this, but I just wanted to let interested parties know I successfully update to 6.2.2-24922 today 😎 Previously I was on 6.2-23739 on a HP Gen8 using the internal NICs. To upgrade I carried out the following steps: installed a PCI dual GigE Intel NIC matching the PCI IDs listed above created a new USB boot stick using Jun's 1.03b loader for DS3615xs with the relevant MAC addresses for my new NIC, VID and PID of the USB stick and a generated DS3615xs serial number disabled the onboard NICs in the BIOS rebooted to check that the new USB stick and NICs were working properly upgraded to 6.2.2-24922 from local PAT file Overall it was a far less painful exercise than the upgrade to 6.2 from 6.1, besides having to install some new hardware (and the minimal expense of that). Thanks to everyone contributing in this thread (and elsewhere) for the help and relevant information 👍🏻
  3. I can confirm this is almost exactly the same as I was seeing with my failed 6.2 upgrade and the first log entry is identical. It all start with "chmod failed for /var/packages (Operation not permitted)" and goes downhill from there. There is nothing logged to /var/log/messages before this that relates to the login or what is triggering the shutdown of services. Have a look in "/var/log/apparmor.log" as well, I was getting loads of entries in there at the same time. In fact, rather than just looking at individual log files, tail everything in /var/log when you login and see what comes up: tail -f /var/log/* That'll show you all the activity and what file it's occurring in. (Here's where I was trying to fix my box: )
  4. You can't run 6.2.1 on a stock Gen8 at the moment as the Synology software doesn't include compatible drivers for the onboard Broadcom NICs. You should be able to take a stock Gen8 to 6.2 simply by creating a new boot stick with the correct MAC addresses in your grub.cfg, rebooting and installing the correct PAT file (I'd recommend using the one for a DS3615xs). I say *should* as my update to 6.2 had some problems and needed manually fixing of a few shell scripts, ymmv.
  5. Just wanted to quickly bump this: I needed to be able to run 'lsof' against the Synology (not a docker container) as part of some debugging and the optware-ng repo at: https://github.com/Optware/Optware-ng ...still functions fine on my system using the 'x86_64' architecture files. But yeah, for 99% of other cmdline tasks I use a debian docker container these days (great for running mkvtoolnix and ffmpeg jobs on files that I want to mangle in my Plex library).
  6. Also note that, I believe, 6.2.1 won't work with a DS3617xs image on Gen8, even with a compatible Intel NIC. More info in the thread blue max already posted above, have a good read through that.
  7. I've been looking for a replacement for Plex as a media streaming server (long story, but I'm far from alone) and came across Emby (http://emby.media). I was very pleasantly surprised to see that they explicitly support Synology and Xpenology separately. The rationale being that, regardless of what CPU you actually have in your hardware, the Synology software always reports the CPU version for whatever .pat file you're running. This prevents the regular Synology Emby packages from utilising any CPU features that may aid in, for example, transcoding. To work around this, they create specific builds for different architectures that you can specify as a parameter in your repo URL. More info here: https://github.com/MediaBrowser/Wiki/wiki/Synology-:-Custom-Package-Architectures-for-XPEnology FYI, I'm presently running with the stock G1610T Celeron and there are *no* optimisations available for this, so I use the default package source URL.
  8. Cheers @bearcat, dunno where I'd gotten it into my head that the fake Synology MACs where required. FYI, I'm not using (or trying to use) any of their services beyond what's installed on my system.
  9. 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...
  10. 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.
  11. 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 🤣
  12. 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)
  13. 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...
  14. Yeah, just tailing it now and all those messages seem to have stopped, too. Job's a good'un 😉
  15. 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!
  16. 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:
  17. 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
  18. Same here, HP Gen8, baremetal, Jun's 1.02b loader. Very quick install, no reboot, only had to restart SMB
  19. 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.
  20. 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...
  21. 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!
  22. 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.
  23. I'm not updating until Synology actually put up some release notes for it!
  24. 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.