Jump to content
XPEnology Community


Transition Member
  • Posts

  • Joined

  • Last visited

Everything posted by totenkopf4

  1. - Outcome of the update: SUCCESSFUL - DSM version prior to update: DSM 6.1.7-15284 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: YES - extra.lzma for DS3615 v4.8 made by IG-88 - Installation type: BAREMETAL - HP DC5300 desktop PC - Additional comments: Upgraded from DSM 5.2 to DSM 6.1.4 then to 6.1.7-15284 final update was to 6.1.7 - 15284 -Update 3 - Several reboots
  2. Greetings all ... Just a Follow up on my XPenology box that has been working since 5x was upgraded to 5.1 then to 5.2. on the original loader. This is configured as a ds3615, it has only 4 Hard Drives. Hardware is an old HP DC5800 E8400 that was used on the Xpen 5.x versions w no issues. Since this version of the motherboard / CPU hardware was not setup for UEFi Bios. it was using a MBR boot loader which was as it was w the original loader file for 5.x. As per the instructions I used @Genesys's v1.02b file for the MBR boot functions when I made the USB. Of course we edit the grub file did the VID and PID and used the same MAC address and the serial number used for the DS 3615 which was used for Xpen 5.x: I also added to the image file for the 2nd partition - "extra.lzma" This may have not be required but I wanted to have all the bases covered. Just followed the instructions as listed and it worked. Changed to the new usb and reboot the computer. Used Synology Assistant to find the server and connected to it to do the migration. Used the DSM_DS3615xs_15217.pat file to apply to the migrate by the Manual method. DO NOT update from the SYNOLOGY servers. Since this is an upgrade / migration the new Package Center wanted to have 3 installed packages upgraded which I did. (Old Pkgs not compatible w he newer DSM 6). One of the reasons needed to upgrade to a newer DSM was that my Windows 10 pcs can now see the server since the old one DSM 5.x was not compatible due to no support for the SMB3 which W10 only now supports: this make it much easier to see in Network Neighborhood. As this is a PLEX server I also updated the PLEX software! Thanks to all the dev's and others that worked on this project. Your work is appreciated.
  3. Mike 54 Here are some posts I found: and I also believe that this card will work as some have reported that it does. Syba SI-PEX40062 SATA III 4 Port PCI-e
  4. Ok some more on this chipset ... currently this card - Rosewill RC-218 PCI Express SATA II Controller Card w/ 4 internal SATA with 2 external eSATA ports (which is a 4x PCIe card). Was also listed by this name as well "StarTech PEXSATA24E 2 Port eSATA + 4 Port SATA II PCI Express x4 SATA Controller" Both cards look and behave the same w the exception of the name of the device. As mentioned I tested this in two systems the above one w the Z68 motherboard and used a 4x PCIe slot which the card will use. And it worked very well. Since then I have purchased an MSI B170 motherboard which has only a 16/8 bit PCIe lot and a lot of the PCIe 1X slots (4). Tested this again w two cpus a celeron and an I5 Skylake w/o problems. In both builds used Jun's loader w the B150 Bazooka MB using the DS3615xs 6.1.2 Jun's Mod V1.03b loader and no problem w the Marvell Chipset driver. Did have issues w his latest Loader (not 1.03b) which would not provide a network connection ... I believe this was due to the manufacture using a Realtek 8111H chipset for the onboard NIC . I have not used an Intel PCIe1x GB nic to test this which could be done. So if you need to have more SATA ports these cards will work there is no RAID BIOS on the Rosewill or the StarTech now we have another card that you may find - IBM Marvell Controller Card DB-MV88SX7042-PEX SLM-566-V1 this has the chipset but it appears to have a BIOS chip on it so this needs to be known. You need to know that if you using older computer motherboards that these SATA 2 spec cards will work w the onboard SATA 2 ports or even some of the mixed versions motherboards that have both SATA 2 and SATA 3 ports. IN my case I have a bunch of SATA 2 HDD 2TB that will work on all ports. So having this card in a system like the MSI B150 with all 6 sata 6gb ports is not a problem. As the Drives will downgrade the speed due to there limits. So if you have a main board w all SATA 3 (6GB speed) then using this card w SATA 2 PORTS adds some slowness to your RAID or SHR pool of drives, its better to keep it as close to the same speed as you can.
  5. Greetings All... Just a Note to let you know of some hardware I came across some time ago that I placed into a Xpenology system I am building. Currently had a old Gigabyte GA-Z68MA-D2H-B3 motherboard w an Intel I3 Cpu. W 8 gig ram. and 6 Seagate ST4000DM005's. All connected to the onboard SATA ports. I also have a "Rosewill RC-218 PCI Express SATA II Controller Card w/ 4 internal SATA with 2 external eSATA Design" which is no longer in production but I wanted to comment on it due to the Marvell no raid chip. It has a Marvell 88SX7042 chipset on it .. this is a NON raid card but was not sure if It would work. As info on this chipset was rather limited in my GOOGLE search for compatibility w Xpenology and or Synology. There are other PCIe cards that are SATA 3 and have been tested "I/O Crest 4 Port SATA III PCI-e 2.0 x1 Controller Card Marvell 9215 Non-Raid with Low Profile Bracket SI-PEX40064" which is available on Amazon. But as this system is mostly all SATA 2 even w SATA 3 drives It was not a concern, Since we are doing a proof of concept here. The Onboard jumpers are set up for 4 internal HDD and no eSATA connection. And when it was plugged into the MB and booted up, the Synology System saw the controller and its one attached HDD in the DSM Storage Manager . So it is looking good . My intention is to add two SSD's and two more 4 GIG HDD to this and use this in this NAS and evaluate SSD caching. Current configuration was created Bare Metal using Juns Bootloader DS3615xs 6.1.2 Jun's Mod V1.02b and the associated DSM. It w DSM_DS3615xs_15284.pat file and then updated via DSM manual updates (update 2) - DSM 6.1.7-15284 Update 2 is current. DSM update tells me that we have an update 3 available. Holding off on that for now. SO just wanted to post that the Marvel 88SX7042 chipset appears to work w DSM and Xpenology. Also I did not do any editing of the conf files to configure this system for more that the current 12 ports that it sees. ( which I believe is default for this model of Synology) When all the ports have been added It will have 10 physical Drives 8 mechanical and 2 SSD's. Controller was added and was seen by the OS. Like it was Plug and PLay..... Thanks Update this was not tested in a 5.0 or 5.2 Xpenology system only the 6.1.x as listed .....Not sure if this Marvell chipset has been set up in the older Xpenology OS's. As my Google search didnt get many hits on these values it subject to testing or trial and error ... your mileage may vary!
  6. jstancil I have the exact same board and I also had issues w post install - namely the find function using the web method. I also use the Synology Assistant App to locate my xpen's of which I have two. I Had installed a variant of 6.1.x on this computer and was testing it and wanted to test the new release of Juns 6.2. To which I had the same problems as you. System showed the screen loader message but would not be seen by the APP or from a browser. As this hardware I am testing on is a closer match to the DS3615 and not a DS918+ which has newer cpu microcode I believe this is the problem. Since this didn't work I went back to the earlier Jun release of 6.2 - since the system had a "working test" system I use the update function of the boot loader - of which there are 3 selection points on screen at boot up. To see these options you need to edit the GRUP.cnf file and increase the timeout to something like 10 from its original value which is in seconds to see this on the monitor and then press the spacebar to stop the auto boot and choose the boot method you want to use. In these scenarios I suggest you use the program Synology Assistant App to proceed with the install of the DSM and not the Web "find" function. Of course they both should work! Its just my experience to use the stand alone program. I also had some other strange issues that could have been related to doing the migrate option instead of bare metal install. You can reformat the USB drive you created by using the command prompt and use the diskpart program in WINDOWS. BE VERY CAREFUL using this program is LETHAL if you make a mistake. If you have VM systems would suggest using a VM windows computer to do this. DO a GOOGLE search on diskpart to format USB or if you have a Mac you can format the USB stick back to FAT32. Currently I am in the process of downgrading to 6.1.3 which is what was on the box. Doing research, and preparing you hardware and editing the CONF file helps w a smooth install. Good Luck. Oh and HAPPY NEW YEAR...
  7. aol Sorry to hear of the troubles but I wanted to comment on your problem. Trust me you'r not alone with these types of problems. WD drives come in many flavors. BLACK, BLUE, RED, GOLD, GREEN etc each one serves a purpose. In your case the Reds are defined as NAS drives whereas the GOLD are for Data Center use. What's the diff well not much but that's not the question. As the issues you are seeing relating to the problem requires questions to be asked. Such as in the SMART tables that each drive has recorded what are some of the pertinent information outside of power on hours. When I look at SMART tables I look for the several things; start /stop, spin up time, raw read error rate, reallocated sector count, drive power cycle count, and the most important is Load Cycle Count ; these are a few of the data values that I look at when evaluating issues w HDD. As you may know almost all HDD manufactures have a set up in the firmware the ability of the HDD to power down at its discretion. This is ok sometimes but may be problematic in situations like your have or in conditions of use like the use of btrfs, So if your start / stop count is very high this could mean the the firmware in the HDD is stopping the motor or parking heads in these cases the drive needs more time to get ready - now server controllers have abilities to regulate this action. But PC's do not. Unrelated to this function, several years ago WD created a feature called "IntelliPark" on its new line of GREEN HDD. This feature was carried over into the RED line as well. That feature was called IntelliPark! "With IntelliPark, the disks can position the read/write heads in a parked position, unloaded. This was meant to reduce power consumption, however it was originally set in a very aggressive way (with a timeout of just 8 seconds), and under certain circumstances the disks would constantly switch in and out of that idle state. That is not uncommon on a NAS, especially if based on Linux, where the system wakes the disks every 10-20 seconds to write logs, to collect offline SMART status (which triggers the heads out of their parked position) or for other reasons." The above paragraph was taken from this site which deals about your problem (potentially) https://withblue.ink/2016/07/15/what-i-learnt-from-using-wd-red-disks-to-build-a-home-nas.html That above link also deals with how to stretch out the IntelliPark timeout to lessen this occurrence of head parking. Be advised that the above site also mentions another function that I would stay clear of. As I am not sure if the Synology OS supports the feature and we don't want to induce more problems than what we already have. Since the HDD you have have been in service for a while now (years), it very well may be due for replacement due to this situation and that these drives are on the fringe of needing replacement. (excessive Load Cycle count) But only an extensive test procedure done offline (another computer) can determine this situation, IE running WD diagnostics or other long term testing software, plus looking at the SMART tables for info on the condition of the HDD at start of test during and at end. Hope this helps/
  8. Bwesson... Not sure of all the steps you have done outside of what you listed. And what version of the Boot loader you on ..doing a search in the forum suggest its some variant of 6.XX. Also have you done the Serial number change and its MAC address. But if you have the blinking cursor on the screen you should do some tests to see if the box is live. Hitting the return key on the keyboard and attempting to login to see if the kernel is alive is a good test too. Do a PING test to the computer and look at Your routers ADMIN screens for connected devices to see if your computer has an IP address (check by your real MAC address on motherboard or NIC. You will need to install Synology Assistant on a computer to load the DSM to the XPEnology box. Launch this program and see if your XPEnology box is detected. Another tool I like to use is ...Advanced IP Scanner which will scan your subnet and list your IP Mac and Host information. http://www.advanced-ip-scanner.com I found some links you should look at for some help. viewtopic.php?f=2&t=32987&p=100900&hilit=DSM_DS3615xs_7393.iso#p100900 and viewtopic.php?f=2&t=32987&p=100900&hilit=DSM_DS3615xs_7393.iso#p101018 which has 2 sub links to review. Getting this running is not for the faint of heart and is not like installing Windows ...
  • Create New...