• Content Count

  • Joined

  • Last visited

  • Days Won


Rhubarb last won the day on December 1 2018

Rhubarb had the most liked content!

Community Reputation

4 Neutral

About Rhubarb

  • Rank
    Junior Member

Recent Profile Visitors

1,431 profile views
  1. Thanks @Aigor, I've read that article. Main priority at present is upgrading my xPenology based platform (Kaby Lake, Xeon E31240v6, 32GB ECC, SAS controller, to DSM7. I'm getting old and not as agile (physically & mentally), to deal with multiple issues concurrently.
  2. No way I'll be upgrading to the specified models - but deduplication of my btrfs volume (8x16TB SHR2) is something I've been looking for for years. Just need to upgrade to 7.0.1 and resolve the dedupe implementation, I guess!
  3. Hi Katana, My Supermicro mbrd (X11SSL-CF) has a Dual GbE LAN with Intel® i210-AT. I know that it has always worked with Jun's DS3617xs loader 103b.
  4. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 U4 - Loader version and model: Jun's Loader v1.03b DS3617xs - Using custom extra.lzma: Yes - Installation type: Baremetal on Supermicro X11SSL-CF, 16GB ECC mem., 6 SATA drives attached to LSI3008 SAS controller. - Additional comments: Used the existing (unmodified) bootloader that was previously carried over and operating for DSM 6.2.2-24922. The upgrade completed normally
  5. - this is specific about skipping unused drive positions - i guess exactly what you are looking for https://xpenology.com/forum/topic/14224-tutorial-fix-skipped-hdd-numbers/ - you can try to disable the ports in bios - change synoinfo.conf in /etc.defaults/ to support more drives then 12 (up to 24 can be done without problems) https://www.youtube.com/watch?v=2PSGAZy7LVQ this manual modding will be lost when installing a new "complete" pat file (~300MB, containing a hda1.tgz), as this completely overwrites the files on the system partition and sets it back
  6. imho the lsi3008 is not supported on 3615 (you did not write about the loader and dsm version you tried) you should be successful when using loader 1.03b for ds3617, latest extra.lzma (matching 3617 and dsm 6.2.2) and dsm 6.2.2 6.2.2 contains a newer mpt3sas driver then the older versions of dsm read the section about ds3615xs and ds3617xs Many thanks IG-88 for your considered advice. We (my son particularly), followed your advice with regard to the extra.lzma, zImage, and rd.gz included in DSM_DS3617xs_24922.pat and we got my X11SSL-CF system to boot with Jun's
  7. Trying to install DS3615xs loader on Supermicro X11SSL-CF which has 6xSata3 and Two (2) Mini-SAS HD Ports, each allowing connection of 4 SATA HDDs with 12 Gb/s throughput for each hard disk drive. Problem I'm having is to get the DSM to actually address the SATA drives attached on the SAS controller. I would prefer to hook up 8 SATA disks on the SAS ports first, leaving the SATA ports unused, because of the convenience of the miniSAS cable routing. Whilst trying to install DSM, I'm getting an Server.(Error Code: 38). Looking for advice on changes necessary in the following lines in
  8. I notice that several users claim to be using the Supermicro X11SSL-CF mbrd with Xpenology and Jun's loaders, I can't seem to get it to work. Whilst I had success creating a DS3615_6.2 boot loader for the Supermicro X10SL7-F mbrd (which has the same i210-AT network controller as the X11SLL-CF (X10SL7-F has 6 x SATA (2xSATA3 & 4xSATA2), 8xSAS 6Gb/s, 1xSATADOM; X11SSL-CF has 6xSATA3, 8xSAS 12Gb/s, 2xSuperDOM), I have not been successful in creating a suitable DS3615_6.2 bootloader for the new board. With Jun's loader 1.03b, the system displays the boot message from the bootloader, but S
  9. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922-2 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - Supermicro X10SL7-F; Xeon E3-1241 v3 CPU; 16 GB ECC (2 x 8 GB DDR3); 2xGBE +1IPMI_LAN port; 6 SATA (2xSATA3 (6GB/s) & 4xSATA2 (3GB/s); 8 SAS (L-SAS 0-7 supported by LSI2308 SAS controller) connected to a total of 10x8TB WD SATA HDDs (8xWD-80EFZX; 2xWD80-EFAX) via standard SATA cables. - Additional Comment: Reboot required
  10. Synology's Drive, Moments, Photo Station and Deduplication? Background: Originally built and operating flawlessly for over 2 years since April, 2016, my Xpenology DS3615xs compatible (Supermicro X10SL7-F-0; Intel Xeon E3-1241-V3 (3.5 GHz 4 core/8 thread Haswell); 16 GB ECC RAM; began exhibitting regular hard disk disconnections/RAID 6 failures between July 2018 and late February, 2019. It was only after I replaced the Corsair VS450 450W power supply with a brand new 650W Coolermaster Gold 80+ unit on 1 March, 2019, that all of the disk error problems disappeared. The unit has now been o
  11. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.1-23824 update 6 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - Supermicro X10SL7-F-0 with both SATA (6 ports) and SAS (8 ports - LSI2308) and dual onboard Intel (i210AT) NICs. - Additional comments: fastest System update ever; seems to be operating normally; also updated several of the apps that were showing as outdated.
  12. Seemed to be the only way bearcat - but not good to have to disable the whole 6 port SATA controller (2x6Gbps & 4x3Gbps) to disable only 2 ports. I have now arranged purchase of a new LSI2308 8 port SAS PCI-E and a SFF-8087 SAS to 4 port SATA cable to make up for the lost ports. System is now running with 8 disks (RAID 6) until I get/add the new hardware.
  13. Thanks again for your advice, flyride. However, no luck yet with DiskIdxMap=080A00 and SataPortMap=228. Also tried 208. Neither removes the 4 vacant slots for SATA2 (positions 3 to 6 of the Storage Manager drive listing). Have just noticed, however, that the 6 drive RAID 6 group has now entered degraded mode 5/6. One of the drives that was previously not visible is now included in the array, replacing one of the other disks. Will allow the RAID to recover before further changes. Will probably take at least 24hrs to get the RAID normalised.
  14. Had no success mapping out SATA2 controller in two attempts. 1st attempt was to set "set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=208 SasIdxMap=0'" 2nd attempt was to set "set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=20 SasIdxMap=8'" On both occasions, the blank SATA2(x4) still show as vacant slots in (3 to 6) in the Storage Manager Overview and DSM is unable to access the 7th & 8th disk on the LSI2308 (SAS) ports. I do want to retain max disks set to 12 as suggested by haydibe: "The "12
  15. Thanks to you to too haydibe. Much appreciated! Desirably, my SAS controller should be switched to become the first device, then SATA1(x2), and finally SATA2(x4), without increasing/changing the MAXDRIVES limit of 12. Will post again to confirm when I've got system configured correctly as I want.