Rhubarb

Members
  • Content Count

    39
  • Joined

  • Last visited

  • Days Won

    3

Rhubarb last won the day on December 1 2018

Rhubarb had the most liked content!

Community Reputation

3 Neutral

About Rhubarb

  • Rank
    Junior Member

Recent Profile Visitors

844 profile views
  1. - 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 to defaults, the raid usually fails in this case and you have to redo the change, i'm not sure about the state after "re-adding" the missing disks on next reboot, if the disks where redundant disks they will be rebuild (as the raid came up without the redundant disk writable), in case of being unusable at 1st boot (no write) it might just come up ok after re-adding the mod and booting up again (never tried that myself) updates are usually ok (smaller pat files)....... Many thanks IG-88: Soon as I read your msg about BIOS!!!! I realised that I couldn't see the wood for the trees; DOH! Just modified the BIOS and rebooted. Everything's sweet - no SATA ports - system is only using the SAS ports. No wonder your title is Guru Master! Thanks for all your valuable assistance.
  2. 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 loader 1.03b and DSM6.2.2-24922. System went through a recovery and now appears to be operating correctly. Only issue now is that we have not managed to map out the 6 SATA ports which are showing as vacant in Storage Manager. Bearing in mind that this system has 6 SATA and 8 SAS ports (2 more than the twelve disk limit for DS3617xs) , do you have any advice on how to modify the set sata_args line in the grub.cfg to cause the system to recognise all 8 SAS ports and only 4 of the 6 SATA ports. The current sata_args line in the current grub.cfg is: set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=08 SasIdxMap=1' In the meantime I'll have a play around with the grub.cfg to see if I can manage to achieve the desired result. Thanks again.
  3. 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 the Grub.cfg: to accomplish this: set extra_args_3615='' #set extra_args_3615='earlycon=uart8250,io,0x3f8,115200n8 earlyprintk loglevel=15' set common_args_3615='syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet syno_port_thaw=1' set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=0 SasIdxMap=1'
  4. 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 Synology Assistant is not finding any evidence of the system on the network. Both the X10SL7-F and the X11SSL-CF boards use the Intel i210-AT dual Gigabit LAN. Specs for the two boards are as follows: X10SL7-F Mbrd Single socket H3 (LGA 1150) supports Intel® Xeon® E3-1200 v3/v4, 4th gen. Core i3, Pentium, Celeron processors 2. Intel® C222 Express PCH 3. Up to 32GB DDR3 ECC 1600MHz UDIMMs in 4 sockets 4. Dual Gigabit Ethernet LAN ports via Intel® i210AT 5. 2x SATA (6Gbps), 4x SATA (3Gbps) 6. 8x SAS2 (6Gbps) via Broadcom 2308 7. Expansion slots: 1x PCI-E 3.0 x8 (in x16), 1x PCI-E 2.0 x4 (in x8) 8. 2x USB 3.0 (1 Type-A + 1 via header) 6x USB 2.0 (4 rear + 2 via header) 9. Integrated IPMI 2.0 with KVM and Dedicated LAN 10. SATA DOM power connector support 11. VGA D-sub connector, TPM header X11SSL-CF Single socket H4 (LGA 1151) supports Intel® Xeon® processor E3-1200 v6/v5, Intel® 7th/6th Gen. Core i3 series, Intel® Celeron® and Intel® Pentium® Intel® C232 chipset Up to 64GB Unbuffered ECC UDIMM DDR4 2400MHz; 4 DIMM slots Expansion slots: 1 PCI-E 3.0 x8 (in x16), 1 PCI-E 3.0 x4 (in x8), 1 PCI-E 3.0 x1 Dual GbE LAN with Intel® i210-AT 6 SATA3 (6Gbps) via C232; RAID 0, 1, 5, 10 8 SAS3 (12Gbps) via Broadcom® 3008 SW controller; RAID 0, 1, 10 I/O: 1 VGA, 2 COM, TPM header 2 SuperDOM with built-in power 5 USB 3.0 (2 rear, 2 via header(s), 1 Type A), 6 USB 2.0 (2 rear, 4 via header(s)) Any advice anyone can provide on this subject would be much appreciated. I am particularly interested in the following issues: 1. How the 2xSuperDOMs on the X11SSL-CF need to be addressed in the Grub.cfg (if at all relevant); 2. Necessary modifications in the following lines in Grub.cfg: set extra_args_3615='' #set extra_args_3615='earlycon=uart8250,io,0x3f8,115200n8 earlyprintk loglevel=15' set common_args_3615='syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet syno_port_thaw=1' set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=1 SasIdxMap=0' I would very much appreciate any advice/guidance from those with more experience and success in this matter. All my efforts to date with the new board have proven fruitless. Thanks.
  5. - 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
  6. 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 operating flawlessly again since then, with performance far superior to consumer grade Synology products. I am a long time user of Photo Station and I like it very much. During this time I have been concerned about disk wastage due to data duplication caused by Photo Station in particular, as it places photo files in the volume's photo folder in those cases where original photo files reside in my "/home" directory on the NAS. When these photos are uploaded from other storage areas on the NAS, such as in homes/user directories (as a result of PC backups to the NAS) the /photo storage folder is holding duplicate copies of those files. I have for some time been running Synology's Drive and Moments applications on my DS3615xs based platform which is running DSM 6.2.2-24922. The system is also running btrfs (for it's Copy on Write features; bitrot protection, etc) which I have found to be very reliable. Other applications installed include Active Backup for Business and Synology's Hyper Backup suite (both applications not currently being used). Drive is enabled (with Intelliversion=32) against my /home (My Drive) folder, and; the /photo, /music folders on the volume. Observations: When I copied approx. 1 TB (actually 971.95 GB in 29320 files/70 folders) of RAW image files from my /homes folder to a /homes/Drive sub-folder (virtually duplicating the files in the homes directory), the homes folder storage increased from 9.71 TB to 10.66 TB; this was accompanied by a rise in CPU resources dedicated to the Drive service (initially in order of 30+%, then reducing to 8-20%, and finally when CPU resources allocated to “Drive” were 0 (when checked in the morning after rising), total storage of the /homes folder was then shown as 10.66 TB (443,891 files, 44885 folders), but total storage on the volume remained at 27% (15.31 TB of 55.86 TB). (Note: this system also functions as a Plex server on my home network. Plex continued to serve my Samsung smart TV Plex client and a remote Plex client, without playback issues during the copy process). Finally, when I deleted all of the 971.95 GB of files copied (duplicated) to the “Drives” sub-folder (next morning), volume usage still remained at 27% and storage in the /homes folder again reduced back to 9.71 TB (414571 files, 44814 folders). I am wondering if anyone else has observed similar circumstances. Is this some indication of deduplication of redundant data files by the Synology Drive app? System data: 10 x 8 TB WD-Red hard disks in RAID 6 configuration (not SHR2). Storage Manager: Volume1 (Normal) 27% Storage Pool 1; 15.3 TB/55.9 TB Volume 1 - Normal: RAID 6 (with 2 disk data redundancy); Total capacity: 55.86 TB; Used Capacity: 15.32 TB Shared Folder storage: Shared folder1: 292.5 GB (314,067,717,955 Bytes), 87013 file(s), 838 folder(s) homes folder: 9.71 TB (10,676,301,073,915 Bytes), 414571 file(s), 44814 folder(s) music folder: 7.67 GB (8,234,597,498 Bytes) 2416 file(s), 52 folder(s) photo folder: 476.23 GB (511,352,024,764 Bytes), 72262 file(s), 698 folder(s) Rod 220.73 GB (37502 files, 459 folders) Rail 6.43 GB (402 files, 3 folders) Moments 1014.7 KB (1 file, 2 folders) Holidays 249.07 GB (34,357 files, 230 folders) video folder: 4.54 TB (4,996,187,380,629 Bytes), 2964 file(s), 479 folder(s) web folder: 452.6 KB (463,478 Bytes), 62 file(s), 7 folder(s) Rhubarb
  7. - 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.
  8. 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.
  9. 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.
  10. 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 drives" limit is the default-configuration. If you change it, be prepared that updates sometimes reset your settings to the default value." I'm still struggling with how to go about offsetting the location of the 8xSAS ports to mask over the empty SATA2 ports.
  11. 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.
  12. Thanks for your advice flyride. I have seen some material on this topic on the net and have previously (some months ago) read the tutorial when I was not aware of the need to map out a device (SATA2x4), because my system appeared to be functioning flawlessly with all drives connected across the available controllers (incl. SATA2). Will investigate further today. Thanks again for your advice and pointing me in the right direction.
  13. My Supermicro m'brd system (X10SL7F as DS3615xs) has lately had occasional disk issues which Supermicro has advised me could be due to RAIDing 6Gb/s (SATA1x2), 3Gb/s (SATA2x4), and 6Gb/s SAS(4of8) as a 10 Disk RAID 6 array. I was generally advised that RAID groups should be confined to each controller. My m'brd has 2xSATA3 RAID0,1 ports; 4xSATA2 RAID0,1,5,10 ports; and 8xSAS2 (LSI2308) ports. To resolve my problems, I placed 4 of my HDDs on the slower SATA2 ports as RAID5, and 6 drives on 6 of the 8 available SAS2 ports. Because of the 12 disk limit for DS3615 I can't use more than 6 of the 8xSAS2 ports. I guess my options are to: a: Change the MaxDrives limit to 14 and place two of my HDDs on to the 2xSATA1 ports and the balance on the 8 SAS ports; (this gives problem that the 4 vacant SATA2 ports show as "blanks" in the Storage Manager, Overview page); or, b: modify my systems config to remove all the SATA2 ports from being visible to the DS3615xs so that the 4 vacant ports don't show as "blanks" in the Storage Manager Overview and I can see all 8 SAS ports as available for usage. Any ideas how I can achieve either of a/b above? Suggestions welcome.
  14. - Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.1-7-15284 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - Supermicro X10SL7-F with Xeon E3-1241 V3 cpu and 16 GB (2 x 8 GB) ECC / NIC: Onboard Dual Gigabit Ethernet LAN ports via Intel® i210AT - Additional comments: Rebuilt RAID as part of the upgrade from: 10 x 8 TB WD Reds Volume 1 (RAID 6) (btrfs) to: 6(attached to SATA controller) x 8 TB WD Reds in Volume 1 (RAID 6) and 4(attached to 4 of 8 x SAS2 (6Gbps) via Broadcom 2308) x 8 TB WD Reds in RAID 5 (Volume 2). Retained btrfs for both RAID volumes. Primary purpose was to create smaller arrays to minimise stress from rechecking/rebuilding after about 3 or 4 intermittent disk disconnections over the past 6~8 months. Cause of this was never identified. All SATA cables were connected and no entries in logs indicating cause of these disconnections. It should also be noted that it was intended to do the upgrade using Jun's 1.03b and the 6.2.23739.pat. The system refused the use of 6.2.23739 and demanded 6.2.23824.
  15. Hi, Out of curiosity, what do you have you system configured as: DS918+, 916,3615xs, 3617xs? I'm very happy with my Supermicro X10SL7-F mbrd with E3-1241v3: it's rock solid (configured as a DS3615xs) with 9x8TB (WD80EFZX)in RAID 6 config; 6 of the drives are connected on the SATA ports and remainder on 3 of the 8 LSI2308 SAS ports. I did recently experience connection errors with one of the drives which has now been RMA'd back to WD, Vietnam, for replacement under warranty. Am using the box mainly media storage (photo collections; Plex server for my smart tv; and media downloads via Sonar, SABnzbd, etc). Using my old DS1513+ (5x4TB WD40EFRX) to back up important data via Hyperbackup. Have additional off-site backup of important data via a 4 mile wi-fi connection across the valley to my son's house. Use that same connection to access his video library and for his family to access mine. While I have both the X10SL7-F LAN ports bonded, I'm getting transfer rates of averaging 90 MB/s to my desktop PC whilst simultaneously transferring at about 30 MB/s to a notebook PC (also via a hardwired ethernet connection). This is with multiple (15~20 Mb) photo jpgs and the occasional video files ranging in size from 70 Mb to upwards of 500 Mb). I am getting read/write speeds on the Xpenology box maxing out my PCs single ethernet connection at 107~114 MB/s (mainly about 110~112 MB/s). No problems running Photostation for displaying photo library; but original media is stored separately on the disks. No problems running the DSM 6.1.7-15284-1 using Jun's 1.02b, I'm not game to try moving to DSM 6.2 with Jun's 1.03a, just yet.