mgrobins

Members
  • Content Count

    66
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mgrobins

  • Rank
    Regular Member

Recent Profile Visitors

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

  1. mgrobins

    DSM 6.2 Loader

    Hmmm..... I'm sensing from replies or lack of replies that for Bare metal with a Xeon based board I need to stay on 6.1 for now if I am using the DS3617xs DSM setup. I don't do transcoding but outside of that am uncertain if anything else is lacking on the DS3615xs file and if that works with all current updates for 6.2.x?
  2. mgrobins

    DSM 6.2 Loader

    That's interesting feedback. I read the FAQ which suggests the 3615 is the 'optimal" choice due to no real difference with the 3617. The core difference in them as Synology units is that the 3615 was an i3 unit and 3617 was a xeon. The rest was ram speed/quantity. Could the transcoding be the i3 does not manage some instructions the Xeon can? I don't do transcoding so am not sure. I think you are also implying that the loader may be impacting the performance of your CPU? Am I correct in that? I wonder if there is something in the Grub file that needs altering to tell DSM what CPU is present and how many cores etc? Not just for aesthetics (reporting in the info screen) but for function?
  3. mgrobins

    DSM 6.2 Loader

    Good day. I note the update of 1.04b on post 1 by Jun. 3615xs seems to work with the latest 6.2 update for people on bare metal - some on 1.03b and some on 1.04b (which I thought was only for the DS918 NAS?) I use 3617xs (same hardware) and am stuck at the 6.2 first major update as the later ones brick the system. 2 questions 1. Has there been any movement or progress with the loader to enable 3617xs to work with the latest DSM (update 6?)? 2. What is the difference between 3615 and 3617? I've never found a satisfactory answer as to how the loader differences (sometimes just telling different CPU for example) may influence the real performance of my NAS.
  4. mgrobins

    DSM 6.2 Loader

    Hi, just after clarification. Im on BM install with hardware listed in my sig. Loader 1.03b 3617xs and DSM 6.2-23739 6.2-23824 is the next offered update but this will NOT run on the 3617xs with 1.03b. Some are commenting that minor updates to 2379 are operable on the 3615xs. Is this the case? I don't think there are any landmark changes between 23739 and 23824 for a general home NAS (any disagreement?) so will just sit on my current version for now.
  5. mgrobins

    DSM 6.2 Loader

    Sounds like you need to downgrade to a compatible version of DSM yes? Barnie, when I had an issue with an update not suitable for my system I followed the advice of a fellow member here to allow me to downgrade my DSM version. 1. I made a USB for an alternate model and did a migration keeping data (I have DS3617xs hardware so made a DS3615xs USB), that forced some of the core files changed in the unsuccessful upgrade to be rewritten and allow me to do a proper downgrade of the DSM OS. Manually select DSM (not online) and use the version that is correct for the loader (15 vs 17 for example) 2. Once I had things running properly again on the older version I then (with a new DS3617XS USB) did a second migration back to the loader I wanted with the appropriate DSM version for my hardware. I hope that makes sense and is successful for you as well. Hopefully someone else will chime in if my advice is not correct for Barnie.
  6. Thanks. It's 1.03b for me then and the DS3617xs setup :). Tried replying to your other post on Root access but sometimes the web page is not allowing me to reply to topics.... I'll work it out :P.
  7. Hi, just as preparation for my upgrade from DSM 6.1.x bare metal to DSM 6.2.x using Jun 1.03b I have some queries. 1. I'm going to build a new USB from scratch for 1.03b and keep my DSM 6.1 USB. If my upgrade goes pear shaped can I just reinsert my 6.1 USB and use that to get running again? 2. The loader is just to fool DSM into thinking it's a legit Synology NAS.... so placing the new USB with 1.03b on it should the system just boot and be ready to update DSM from 6.1 to 6.2 online (or using the downloaded .pat file)?
  8. Hi, I have a xeon build similar to the DS3617 in all respects (hardware in sig). Looking at the table I am uncertain what "DSM /dev/dri support" means. I currently run Jun's loader 1.02b with the last version of DS 6.1. I do have it backed up but am hoping to build a new USB with the best loader to run the latest DSM6.2 that is compatible. I'd be grateful for assistance or clarification :).
  9. This is how I enabled it but I'm not on the latest firmware. Mod DSM to enable Root access: From https://emby.media/community/index.php?/topic/33197-root-access-by-changing-sudoers-file-failed/ 1) SSH as admin sudo -i to go to root. 2) synouser --setpw root [CURRENT – ADMIN – PASSWORD] 3) and then log out, 4) SSH as root ..
  10. Hi, Main Question: should I upgrade from DSM 6.1 to 6.2. I have read patch notes and don't see a lot that I think affects me but a lot never really gets mentioned - SMB/NFS performance changes etc. So I thought I'd ask before investing the time and risk :). I gather I'll have to build a new USB with loader, but am unsure if I can then just update the DSM and retain settings/data or if the entire system has to be reconstructed? Is a full backup of data advised or essential? it's been a while since I've been on the forum - about a year.... with many months in hospital and I feel a lot dumber for the drugs I've been on :/. So go easy with the answers for my undoubtedly dumb questions to follow 😝 The MVP's here gave me huge assistance with my first build and it's been running nicely with Jun's Loader ver 1.02b (DSD3617xs) and . I'm on Bare Metal and all working well. I had to do some messing around to get root access and a few things..... but otherwise it was reasonably straight forward. Usage: media storage, backup of devices at home performed daily. General files for access across all devices in home Local backup of this NAS to DS1812+ using Hyperbackup (key data but not all) performed weekly Hardware: Jun 1.02b loader and DSM 6.1.4-23824 Update 5 Supermicro X10SDV-4C-TLN2F; 8GB 2133 ECC; LSI 9211 HBA; Corsair XFS 450W 7x 4TB HDD (Raid 6) 10GBe Link to Desktop; 1GBe Link to Backup NAS (DS1812+) using Hyperlink; 1GBe link to remaining LAN
  11. I used hdparm to view device info ..... where or how would I enter the info to replace /dev/sdX with a-H for my drives and what if any difference would it make? hdparm -Tt /dev/md1 /dev/md1: Timing cached reads: 18298 MB in 2.00 seconds = 9158.76 MB/sec Timing buffered disk reads: 632 MB in 3.01 seconds = 209.96 MB/sec That's 7 disks in RAID6 with 8GB RAM and a Zeon-D proc. time dd if=/dev/zero of=/volume1/test/test.file bs=1M count=1000 Can I just use any file for this? I just used a 25GB mkv file time dd if=/dev/zero of=/volume1/test/test.mkv bs=1M count=1000 1000+0 records in 1000+0 records out 1048576000 bytes (1.0 GB) copied, 0.486166 s, 2.2 GB/s real 0m0.489s user 0m0.000s sys 0m0.489s I ran with a count of 10,000 instead as I thought this might overcome any RAM caching and give me a proper result. time dd if=/dev/zero of=/volume1/test/test.mkv bs=1M count=10000 10000+0 records in 10000+0 records out 10485760000 bytes (10 GB) copied, 14.5246 s, 722 MB/s real 0m15.674s user 0m0.012s sys 0m5.167s I think the write caching is active. hdparm suggests it is at least at the drive level. My figures look a bit different to yours.... not sure if they are good or bad! I have one HGST 4TB and the rest are Seagate Ironwolf 4TB NAS drvies.
  12. I'm on update 2 and keeping a close eye on mine. Still tweaking a few things and looking at the hardware side - disk write caching etc so I can work out if I need to change any hardware (Mine is bare metal).
  13. During installation of DSM it will ask you if you wish to do an install for only one volume, or to select an option allowing multiple volumes to be used. It's during the early steps just after you have completed the basic install and gone back into DSM and selected you username if I recall.
  14. I had this issue on my board and it was the bootloader grub file causing issues for me - I had not entered each NIC properly. enter MAC for each NIC, and also tell the loader to use 2 NICs set mac1=yourmac1 set mac2= yourmac2 set netif_num=2
  15. Thank you so much for the advice and direction . Just a quick follow up. I could not get the first command to work - said it did not exist so I just did the dmesg. From the text I have a couple of queries if you are able to help.... I'm not much of a Linux person I'm afraid though I do know PC design quite well. what is this conflict? I think this is the chipset on my motherboard (model is in my sig). I am using the DS3617xs boot loader which is for a Xeon-D so I assumed it would be very similar. [ 13.640583] ACPI Warning: 0x0000000000000428-0x000000000000042F SystemIO conflicts with Region \GPE0 1 (20130328/utaddress-249) [ 13.640626] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 13.640636] ACPI Warning: 0x0000000000000500-0x000000000000052F SystemIO conflicts with Region \GPIV 1 (20130328/utaddress-249) [ 13.640670] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 13.641949] lpc_ich: Resource conflict(s) found affecting gpio_ich [ 13.654651] Loading iSCSI transport class v2.0-870. Does the text indicate write cache is actually enabled or that the Linux kernel enables it and then DSM has disabled it later following boot or some such (which I heard was the case). Aside from throughput improvement it does reduce disk thrashing a lot so I think it's worth pursuing if it is not working (even if I need to get a different raid card perhaps). From the section on write cache etc: [ 14.101669] ata1.00: ATA-9: HGST HDN726040ALE614, APGNW7JH, max UDMA/133 [ 14.101736] ata1.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 14.106561] ata3.00: ATA-10: ST4000VN008-2DR166, SC60, max UDMA/133 [ 14.106592] ata3.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 14.106721] ata1.00: configured for UDMA/133 [ 14.107809] scsi 0:0:0:0: Direct-Access HGST HDN726040ALE614 APGN PQ: 0 ANSI: 5 [ 14.107925] ata3.00: configured for UDMA/133 [ 14.108090] ata4.00: ATA-10: ST4000VN008-2DR166, SC60, max UDMA/133 [ 14.108096] ata4.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 14.108152] ata6.00: ATA-10: ST4000VN008-2DR166, SC60, max UDMA/133 [ 14.108183] ata6.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 14.109225] ata4.00: configured for UDMA/133 [ 14.109304] ata6.00: configured for UDMA/133 [ 14.109605] sd 0:0:0:0: [sda] 7814037168 512-byte logical blocks: (4.00 TB/3.63 TiB) [ 14.109614] sd 0:0:0:0: [sda] 4096-byte physical blocks [ 14.109826] sd 0:0:0:0: [sda] Write Protect is off [ 14.109858] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 14.109945] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 14.116396] ata2.00: ATA-10: ST4000VN008-2DR166, SC60, max UDMA/133 [ 14.116430] ata2.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 14.117590] ata2.00: configured for UDMA/133 [ 14.118852] scsi 1:0:0:0: Direct-Access ATA ST4000VN008-2DR166 SC60 PQ: 0 ANSI: 5 [ 14.119706] ata5.00: ATA-10: ST4000VN008-2DR166, SC60, max UDMA/133 [ 14.119739] ata5.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 14.123230] ata5.00: configured for UDMA/133 [ 14.125230] sd 1:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.63 TiB) [ 14.125239] sd 1:0:0:0: [sdb] 4096-byte physical blocks [ 14.125441] sd 1:0:0:0: [sdb] Write Protect is off [ 14.125448] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [ 14.125532] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 14.158200] sda: sda1 sda2 sda3 [ 14.161110] sd 0:0:0:0: [sda] Attached SCSI disk [ 14.182204] sdb: sdb1 sdb2 sdb3 [ 14.195577] sd 1:0:0:0: [sdb] Attached SCSI disk [ 14.325330] scsi 2:0:0:0: Direct-Access ATA ST4000VN008-2DR166 SC60 PQ: 0 ANSI: 5 [ 14.327096] sd 2:0:0:0: [sdc] 7814037168 512-byte logical blocks: (4.00 TB/3.63 TiB) [ 14.327106] sd 2:0:0:0: [sdc] 4096-byte physical blocks [ 14.327314] sd 2:0:0:0: [sdc] Write Protect is off [ 14.327345] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 [ 14.327432] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 14.381884] sdc: sdc1 sdc2 sdc3 [ 14.384866] sd 2:0:0:0: [sdc] Attached SCSI disk [ 14.455142] scsi 3:0:0:0: Direct-Access ATA ST4000VN008-2DR166 SC60 PQ: 0 ANSI: 5 [ 14.457016] sd 3:0:0:0: [sdd] 7814037168 512-byte logical blocks: (4.00 TB/3.63 TiB) [ 14.457024] sd 3:0:0:0: [sdd] 4096-byte physical blocks [ 14.457224] sd 3:0:0:0: [sdd] Write Protect is off [ 14.457232] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00 [ 14.457445] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 14.477877] scsi 4:0:0:0: Direct-Access ATA ST4000VN008-2DR166 SC60 PQ: 0 ANSI: 5 [ 14.479456] sd 4:0:0:0: [sde] 7814037168 512-byte logical blocks: (4.00 TB/3.63 TiB) [ 14.479490] sd 4:0:0:0: [sde] 4096-byte physical blocks [ 14.479671] sd 4:0:0:0: [sde] Write Protect is off [ 14.479702] sd 4:0:0:0: [sde] Mode Sense: 00 3a 00 00 [ 14.479788] sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 14.496526] scsi 5:0:0:0: Direct-Access ATA ST4000VN008-2DR166 SC60 PQ: 0 ANSI: 5 [ 14.499313] sd 5:0:0:0: [sdf] 7814037168 512-byte logical blocks: (4.00 TB/3.63 TiB) [ 14.499346] sd 5:0:0:0: [sdf] 4096-byte physical blocks [ 14.499722] sd 5:0:0:0: [sdf] Write Protect is off [ 14.499730] sd 5:0:0:0: [sdf] Mode Sense: 00 3a 00 00 [ 14.499821] sd 5:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't suppo I have 6 drives on onbvoard sata and one on my SAS HBI currently.... is this one below the SAS connected drive? If so what are DPO and FUA as it supports them but the onboard does not.... [ 18.613845] scsi 6:0:0:0: Direct-Access ATA ST4000VN008-2DR166 SC60 PQ: 0 ANSI: 6 [ 18.618271] scsi 6:0:0:0: SATA: handle(0x0009), sas_addr(0x4433221103000000), phy(3), device_name(0x0000000000000000) [ 18.618306] scsi 6:0:0:0: SATA: enclosure_logical_id(0x500605b002c8adc5), slot(0) [ 18.618423] scsi 6:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) [ 18.622592] scsi 6:0:0:0: serial_number( ZDH16R1H) [ 18.622627] scsi 6:0:0:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1) [ 18.632140] sd 6:0:0:0: [sdg] 7814037168 512-byte logical blocks: (4.00 TB/3.63 TiB) [ 18.632151] sd 6:0:0:0: [sdg] 4096-byte physical blocks [ 18.939881] sd 6:0:0:0: [sdg] Write Protect is off [ 18.939890] sd 6:0:0:0: [sdg] Mode Sense: 7f 00 10 08 [ 18.941917] sd 6:0:0:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA Some other errors or things I don't understand that may be explainable by others here : [ 24.440607] broadwell_synobios: module license 'Synology Inc.' taints kernel. [ 24.440637] Disabling lock debugging due to kernel taint [ 24.522223] md: Autodetecting RAID arrays. [ 24.592601] md: invalid raid superblock magic on sda3 [ 24.597744] md: sda3 does not have a valid v0.90 superblock, not importing! [ 24.677080] md: invalid raid superblock magic on sdb3 [ 24.682189] md: sdb3 does not have a valid v0.90 superblock, not importing! [ 24.756138] md: invalid raid superblock magic on sdc3 [ 24.761250] md: sdc3 does not have a valid v0.90 superblock, not importing! [ 24.821471] md: invalid raid superblock magic on sdd3 [ 24.826583] md: sdd3 does not have a valid v0.90 superblock, not importing! [ 24.888822] md: invalid raid superblock magic on sde3 [ 24.893907] md: sde3 does not have a valid v0.90 superblock, not importing! [ 24.980498] md: invalid raid superblock magic on sdf3 [ 24.985586] md: sdf3 does not have a valid v0.90 superblock, not importing! [ 25.072161] md: invalid raid superblock magic on sdg3 [ 25.077275] md: sdg3 does not have a valid v0.90 superblock, not importing! [ 25.077290] md: Scanned 21 and added 14 devices.