roadx

Members
  • Content Count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About roadx

  • Rank
    Newbie

Recent Profile Visitors

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

  1. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.7-15284 - u2 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - Gygabyte GA-C1037UN-EU (see my signature) - Additional comments: REBOOT REQUIRED (self-reboot after update)
  2. roadx

    DSM 6.2 Loader

    @ideasman69: Thank you for you advise! This is what I was waiting for.. Also do I, thinking 6.1.7 is much better (and safer!) than 6.2 regarding the updates... Speaking of this, in 6.1.7, once I've make the settings as you suggest, the OS never bothers me with 6.2 announcements. But in 6.2, even I choose the 2nd option (as you suggest for 6.1.7 case) , the OS always bothers me with 6.2.1 update (which is fatal for my HW) Thank You!
  3. roadx

    DSM 6.2 Loader

    Hi guys! After a while, now I make from scratch my server (bricked up by validate upgrade from 6.1.7 (w BL v1.02b) to 6.2 (I know, I know... I should read forum before, but ******* happens!) Now, after I wipe my 3Tb HDD (having in mind to start from a clean install) I am faced with two options (both working on my HW -see signature): 1.- install and stays with DSM 6.1.7 on ds3615xs, w Jun's BL v1.02b (...! and never update/upgrade to 6.2!); (I read that is much stable...) 2.- install and stays with DSM 6.2 on ds3615xs, w Jun's BL v1.03b (...! and never update/upgrade to 6.2.1!); I want to make a decision before start restoring my user data on the server's HDD. Any suggestions!? Thx in advance!...
  4. roadx

    DSM 6.2 Loader

    @bearcat: ...so... after all, there IS a special treatment... BIOS stuff... (at least for your kind of servers...) Sorry to not be able to help further! I am "not in the club" (see my signature)!
  5. roadx

    DSM 6.2 Loader

    @bearcat, @flo89: Far as I read around here regarding the used processors, AMD has a "special" treatment regarding the used Jun's BL. At least, not all BLs works with AMD processors. Right? (...or, maybe I'm wrong.. Anyway, @bearcat seems to know better than me, so don't shoot the piano player )
  6. roadx

    DSM 6.2 Loader

    @flo89: A silly Q: do you have more than one NIC in the system? (asking this, because I've experienced some issue regarding the NICs -personally having 2- and allocated MACs)
  7. roadx

    DSM 6.2 Loader

    Hi, I discover that my NIC driver is based on "r8169" (?), so, I answered with this on a previous Q... Now... Navigating through my server's BIOS, I have no ideea to make something crucial changes, but to be honest, the MAC addresses for those two NICs has been switched. Suddenly, the ping command start working after I boot (Nth times and variants like : "with custom extra.lzma"... without "custom extra.lzma", with "v1.02b for GPT"... with "v1.02b Genesys"... UEFI... Legacy... and so on...). The "final" working variant is: BL v1.02b, GPT (or Jun's variant - NOT Genesys!) without custom "extra.lzma" file in whatever mode: UEFI or Legacy, doesn't matter! BTW: On my previous post I claim that the server reboots after 1..2 minutes, again and again... It was from custom "extra.lzma" file usage! Once I leave the BL v1.02b as it was (except grub.cfg file, modified with my particular vid/pid/sn and mac1 values), the boot sequence comes stable and I was able to discover the DSM and install DSM 6.1.7 !!! Maybe I am a little bit confused in explanations, but I am happy all it's working again (fresh install). ...Oh! Almost I forgot! As I said, to force fresh install I deliberately wiped my HDD (all partitions has been deleted using GParted!) Still, I had to make a strange remark: If nothing remains on my HDD, how come the Synology_Assistent, when found the server also "discovered" even a DSM version!!?? Which, btw, I don't used in the past.... (see the attached picture, the 6th column named "Version") Maybe my findings (regarding the root cause of again-and-again reboot cycles) is useful around here, in this topic. Thank You, guys! CU... LastEdit: I know what I've done in BIOS: I disabled the LAN Controller #2!! And because I had only one NIC, the allocated MAC, is the one for eth0, I mean, the MAC I've used!! YUPYY!
  8. roadx

    DSM 6.2 Loader

    Hello all, A short intro (as this is not my 1st post on this subject - also I post this somewhere else in this forum, but maybe that thread is dead...): In the past I had a functional DSM 6.1.7 on ds3615xs using Jun's BL v1.02b. The used HW is the one described in the signature. By my mistake, I validate the upgrade action, from 6.1.7 to 6.2 ==> my DSM server has been bricked out. Ok! After a lot of failures to make my server working again (including playing with BL v1.03a2+ds918+, BL v1.03b+ds3615xs) I gave up and I've erased everything on the HDD, having in mind to start again, from the beginning with a clean install (as I've done in the past, considering if I've done that, then I should be able to do it again!) So, I took a fresh new BL v1.02b and I've done all operations regarding the VID/PID/SN/MAC1 as I've done before. My intention is to make a fresh install of DSM 6.1.7 on ds3615xs. (my server's HDD - a 3TB SATA-III has been erased and at this moment not even a partition is not created on him! And is connected to SATA0...) But... !!! When I restart the server (having the prepared usb stick, connected in one of the usb port), either in UEFI mode or Legacy mode, the screen with "Happy hacking" appears, but after a while he restarts over and over again... Meanwhile, using Synology Assistant, I couldn't see anything in the LAN (as Synology server...) to permit me to make a fresh install. What I've missed? I try also with/without extra_lzma customized file (I think -but I am not so sure- in the past, when the server has worked, I used this customized file...I am not sure...) Still wonder why I do not see anything in the LAN and why the server reboots after a while?! Nothing changed in the HW configuration (not even the USB stick...!) Any suggestion(s)?! Thx in advance...
  9. Hello, In the past I had a functional DSM 6.1.7 on ds3615xs using Jun's BL v1.02b. The used HW is the one described in the signature. By my mistake, I validate the upgrade action, from 6.1.7 to 6.2 ==> my DSM server has been bricked out. Ok! After a lot of failures to make my server working again (including playing with BL v1.03a2+ds918+, BL v1.03b+ds3615xs) I gave up and I've erased everything on the HDD, having in mind to start again, from the beginning with a clean install (as I've done in the past, considering if I've done that, then I should be able to do it again!) So, I took a fresh new BL v1.02b and I've done all operations regarding the VID/PID/SN/MAC1 as I've done before. My intention is to make a fresh install of DSM 6.1.7 on ds3615xs. (my server's HDD - a 3TB SATA-III has been erased and at this moment not even a partition is not created on him!) But... !!! When I restart the server (having the prepared usb stick, connected in one of the usb port), either in UEFI mode or Legacy mode, the screen with "Happy hacking" appears, but after a while he restarts over and over again... Meanwhile, using Synology Assistant, I couldn't see anything in the LAN (as Synology server...) What I've missed? I try also with/without extra_lzma customized file (I think -but I am not so sure- in the past, when the server has workinged, I used this customized file...) Still wonder why I do not see anything in the LAN and why the server reboots after a while?! Any suggestion(s)?! Thx in advance...
  10. roadx

    DSM 6.2 Loader

    @bearcat: The only info known by me related to my server's NICs (there are two of them, on-board) is the info found on the Gigabyte site and is the one as it showed in the signature. I have no idea which kind of particular controller do I have. On the Realtek site ( https://realtek-download.com/realtek-pcie-gbe-family-controller/ ), they said: Realtek PCIe GBE Family Controller RTL8111B / RTL8168B / RTL8111 / RTL8168 / RTL8111C / RTL8111CP / RTL8111D (L) / RTL8168C / RTL8111DP / RTL8111E / RTL8168E / RTL8111F / RTL8411/ RTL8111G / RTL8111GUS / RTL8411B(N)RTL8118AS Anyway, I succeed to save the files from inside the server's (user) partition, where I found all user(s) files and structure (the one containing my files), but... (as you can see, always is a "but..." ) Despite my server has one SATA III HDD (3Tb, 2.5" form), the DSM software make 4 partitions on him: one big pure ext4 partition (for user's usage) which I could accessed 'normally' and 3 other partitions which seems to be some RAID-like partitions (for OS and DSM stuff, I guess...) Ok! In order to have some results in making the server working again, I want to go into the DSM's root structure to see if I could find there the famous '/.xpenoboot' directory, which I read about it around here. Some guys said (if I understood well), if this directory is deleted, then, on re-boot (using BL 1.02b as before), it could be possible to obtain an working server having the 'old' version (in my case, 6.1.7) instead of 6.2 because the real upgrade (from 6.1.x to 6.2) would have to be executed upon restart, but the real restart never occur because the BL (v1.02b) was not compatible with the preparations made by the upgrade core before restart. Maybe is wrong what I understood... So, I need to "see" somehow those RAID-like partitions (from a Linux live USB). I read something about this (how it could be possible to see them) around here, but frankly, I don't remember well on which page I read about the DSM and 'mdadm' stuff. (and are a lot of pages... - btw: maybe the admin(s) would make another particular thread for VMware & ESXi stuff... just saying...) Somebody could help me to refresh my 'pointers'? Thank you, again for your answer(s)! (last edit): maybe here? I would see...
  11. roadx

    DSM 6.2 Loader

    @bearcat: Thank you for the answer! Still, about my HW, you said: ... but NOT with the Realtek NIC, right?! I should install an Intel NIC if I found one half-sized. Anyway, the DSM 6.1.7 (ds3615xs) with BL v1.02b is all I need: file -server, media-server, sharing place. So, I will try to see if I could revert back to what it was before 6.2 update/upgrade Keepin' touch! Meanwhile, if you, guys, have any other suggestion(s), I'll appreciate! Thx!
  12. roadx

    DSM 6.2 Loader

    Hello guys! As I said, at this moment, my formerly server ( a ds3615xs with DSM 6.1.7, using BL v1.02a), which has been bricked out by myself when I validate (wrong choice!) the upgrade action from 6.1.7 to 6.2 is unusable. Waiting for BL v1.03b, now, I proceed to make my server working again, but... Doing all as I previously done (VID/PID/MAC/SN modified on 'grub.cfg' file as I've done for BL v1.02b), now, I have a failure, because my server (using BL v1.03b this time) is not found on LAN by the Synology Assistant, nor by pinging his static internal IP address (192.168.1.2 - which is given by my router's DHCP according the used MAC) 😟 Reading around here, it seems the cause of my server malfunction is the Realtek NIC (it's a built-in one, but successfully used before with BL v1.02b) which is not supported by the BL v1.03b and DSM 6.2 (as I understand by reading this topic...) (the HW is showed in the signature!) Is that right? Should I re-install DSM 6.1.7 and using the "old" BL v1.02b and stop update/upgrade for the future?! Any suggestion is welcomed! Thank you!
  13. roadx

    DSM 6.2 Loader

    Sorry for this long post, but my HW specs has been requested... I promise the next one will be short one.. So, my DSM 6.1.7 server (DS3615xs with v1.2b Jun's bootloader) has been installed (and works until I validate the upgrade to 6.2.x -I don't remember well) on the following HW: MB: Gygabyte GA-C1037UN-EU (rev. 1.0) CPU: Built in with an Intel® Dual-core Celeron® 1037U processor (1.8 GHz) 2 MB L3 cache Chipset Intel® NM70 Chipset Memory: 2 x 1.5V DDR3 DIMM sockets supporting up to 16 GB of system memory; 2 x 1GB DDR3 / 1333 MHz memory modules installed in Dual channel memory architecture; Onboard Graphics Integrated Graphics Processor: 1 x D-Sub port 1 x HDMI port, supporting a maximum resolution of 1920x1200 * Support for HDMI 1.4 version. Maximum shared memory of 1 GB Audio: Realtek® ALC887 codec High Definition Audio 2/4/5.1/7.1-channel LAN: 2 x Realtek® GbE LAN chips (10/100/1000 Mbit) Expansion Slots: 1 x PCI slot Storage Interface Chipset: 1 x SATA 6Gb/s connector (SATA3 0) 2 x SATA 3Gb/s connectors (SATA2 1~2) 1 x eSATA 3Gb/s connector on the back panel JMicron JMB368 chip: 1 x IDE connector supporting ATA-133/100/66/33 and up to 2 IDE devices USB Chipset: 8 x USB 2.0/1.1 ports (4 ports on the back panel, 4 ports available through the internal USB headers) As I said, logically speaking, this HW worked from DSM 6.1.2 till 6.1.7 ( I validate all proposed updates! - bad idea!) very well using Jun's bootloader v1.02b for ds3615xs. Now, using the same HW (the same LAN connection, the same USB stick) but with Jun's bootloader v1.03b from August 2018 (having grub.cfg modified accordingly), I am not able to detect anything on LAN, using Synology Assistant (v6.2-23733) (UEFI and Standard has been tested also at boot time). No BIOS modifications! If I boot from a Linux live stick with PartitionMagic, I could see my LAN (I ping successfully my router at 192.168.1.1; my HW having 192.168.1.2 as fixed address given by router's DHCP) Also I could see the server's disk (one SATA disk connected on SATA3 port, having 3GB) with some raid partitions (DSM specific) and one big partition ext4, with all my files and directory structure on it. But when I boot from the bootloader v1.03b, nothing happen, as I said... Any suggestions, please?! Thank you, guys!
  14. roadx

    DSM 6.2 Loader

    Hello all! Because I do not read on time what's happen if the DSM 6.1.7 updates to 6.2, my running 3615xs system has been bricked up! The 1.02b loader don't work anymore, so I wait till the Jun makes some research and give us a new bootloader able to work with DSM 6.2 (Thank YOU, Jun, for your great work!) At this point, I think, is not so important what kind of HW do I have, because: - I use the same barebone Intel based HW as when the DSM 6.1.7 runs on a 3615xs system; - I use the same USB stick (having the same VID & PID) as in the past; - The LAN connection is the same; the MAC address and reserved IP address given by my DHCP router are the same; Nevertheless, using the Jun's bootloader v1.03b for DSM 6.2 (created on 07.08.2018) and editing the SN, MAC, VID and PID in the grub.cfg (as I said, using the same values as for v1.02b), the Synology_Assistant could not find any server on the LAN. Not even to be able to make a fresh install using the proper PAT file. The server's screen shows the thing with "...Happy..." - you know what I am talking... and that's it! I wonder: why is that? Anybody? Why, bootloader v1.02b worked in the past, and using the same HW, LAN setting, USB stick but with v1.03b bootloader, I am not able even to see my HW?! (Sorry, if it will be requested, I could provide all my HW specs, but I don't want to make the post to complicated when -if you ask me- the logic says there is no need of HW specs if with the same HW it worked flawless in the past!) Thank you in advance, guys! Please help! ...Or suggest...