bglf83

Members
  • Content Count

    135
  • Joined

  • Last visited

Community Reputation

1 Neutral

About bglf83

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. bglf83

    DSM 6.2 Loader

    I am using 1.03b DS3615xs version with Legacy Boot. I was under the impression that it only works that way.
  2. bglf83

    DSM 6.2 Loader

    Why not just use the DS3615XS 1.03b loader?
  3. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.7-15284 Update 3 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: Bare Metal, Supermicro X10SRi-F, integrated NICs Intel but disabled, Intel Pro/1000 PT (EXPI9400PTBLK listed as 82572) - Additional comments: Computer needs to be booted in Legacy BIOS mode, I confirmed the Intel 82572 chipset uses Intel e1000e drivers and I had to delete the root .xpenoboot folder and reboot for everything to work right.
  4. I was successfully with DS3615xs 1.03b loader. I did have to delete the old xpenoboot folder as detailed below to resolve my network issues after I migrated from the 3617 to the 3615. I have an e1000e drive loaded for my NIC. I disabled all my other NICs. To check what driver your NIC is using, log into SSH and run these commands. (I got this info from another person on the forum) ---------------------------------------------- Open a SSH connection to your NAS, and type: lspci | grep 0200 (this will list your nic's) you should see something like: ... Device 8086:xxxx (indicating Intel) This should be eth0, so type: ethtool -i eth0 you should see something like: driver: e1000e (this is a driver supported in 6.2.1) If not, try using the above :xxxx device id to check if it is supported by the bootloader/DSM version you will try to us ------------------------------------------------
  5. I am not sure if there is a difference between the 3615 and 3617 but I had to ask. I have an Intel Gigabit PRO 1000 CT that can load 1.04b on the current update, but it does not show the network adapter in the network list. I also have not been able to update all the way with the DS3617XS loader. I am considering getting the HP card, but I am not sure that is my issue. I am continuing research and it looks like with 1.04b, the issue I was having may be fixed by doing this: ------------------------------------- @XbladeX From earlier experience with a problem like that: try these steps: Activate the SSH service in DSM (if not active) Connect to your NAS with an SSH client (e.g. putty) (or from Win 10, open a cmd window, run : ssh admin@my.nas.ip (replace with the actual IP) Enter your credentials (user: admin) Change folder to root (cd /) Delete the xpenoboot folder (sudo rm -r .xpenoboot) If the SSH service keeps stopping, you have to be quick. --------------------------------------
  6. Are you using the ds3615xs or ds3617xs loader?
  7. I run Plex as a native package. I only have to reboot for updates or maintenance. Sometimes it will go many months.
  8. Depends on use. As a file server, it's very good. Plex transcoding should be pretty decent as well.
  9. Plex supports video accelerated transcoding on some Synology boxes. I would at least look into that if I were looking today. Sent from my HTC 10 using Tapatalk
  10. Necessary for photo station and video station to transcode. Sent from my HTC 10 using Tapatalk
  11. I use a deluge docker. It's worked for 2 years now. Sent from my HTC 10 using Tapatalk
  12. I did. Nothing g strange reported though. Sent from my HTC 10 using Tapatalk
  13. If it would have been like this 2 years back I would have just purchased a syno unit instead of building. Sent from my HTC 10 using Tapatalk