mgrobins

Members
  • Content count

    56
  • 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

    Write Cache Not Functioning - not good

    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.
  2. mgrobins

    DSM 6.1.1-15101 Update 4

    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).
  3. 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.
  4. 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
  5. mgrobins

    Write Cache Not Functioning - not good

    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.
  6. Hi, I have noticed with my xpenology build that I cannot enable Disk Write Cache which is a pretty major problem for maintaining optimum speed and reducing HDD strain. I am using a mixture of onboard SATA ports for my Supermicro motherboard (Xeon-D) and an LSWI 9211-8i HBA flashed in IT mode. HDD - 6x Seagate 4TB Ironwolf NAS, 1x HGST 4TB NAS. DSM version 6.1.1.15101 Update 2. Anyone able to shed light on why this is an issue and how to work around it? When I attempt to enable it I get a red text message below stating that "The Operation failed - please log into DSM and try again".
  7. Hi, I have been running a batch command on my PC to power off my NAS after some actions on the PC are complete. Upgrading to DSM 6 has broken this as I can no longer use root access through plink.exe. The commands I have been using are: C:\SSH_stuff\plink 192.168.1.2 -l admin -pw XXXXXX poweroff or echo n | C:\SSH_stuff\plink.exe -P 22 -ssh -pw XXXXX admin@192.168.1.2 "shutdown -h now" Both come back as "root access denied". Synology knowledge base advices for SSH to use "Sudo -I" to gain root access however I am not certain how to structure my plink.exe commands to achieve this as well as run the power off command. I tried the following and some derivatives with the -t which cleared up the ttl errors associated with sudo but could not get it to accept a password. echo n | C:\SSH_stuff\plink.exe -P 22 -t -ssh -pw XXXXX admin@192.168.1.2 "sudo -I" "poweroff" Hopefully someone can assist . Another potential method would be to have a script on my NAS I can run that enables root access or runs the poweroff command? If so ... advice on that would be helpful too - I'm pretty much a non Linux user after so many years absence from it I thnk this will be useful for anyone who needs root access and wants to run commands.
  8. mgrobins

    WOL on DSM6 - Jun loader

    ok... "etherwake" no longer works. the command "Synonet" is what you want to be using now to have the NAS wake other devices. it got broken in an earlier patch but seems ok again now. In task scheduler you set up a use script and the format would be: synonet --wake XX:XX:XX:XX:XX eth0 where eth0 is the Ethernet port being used (I don't think it's the target Ethernet port but the one on the nas) if you have bonded NIC ports use "Bond 0" instead. synonet --wake [MAC address] eth0 or if you have a bond: synonet --wake [MAC address] bond0
  9. mgrobins

    DSM 6.1.x Loader

    Do you have a data backup? I had this when I was building my server and ended up doing a forced re-install. I had no data on there then so did noit pay attention to what impact it will have on your data sorry. Still quite new to xpenology. What I can say is that a fresh install on blank drives works just fine bare metal and will update perfectly to 6.1.1 update 2. I have mine operating and have copied all of my data from my production NAS across to it and it seems stable and is past the 24hr timeframe. Pretty sure some comments in thread suggest that you cannot upgrade yet you have to do it as a fresh install.
  10. Hey, after all of the assistance I had from people here testing out aspects of xpenology and tooling around with a bunch of different hardware I thought I would post up the worklog I have for my current NAS. I built this as a comparable performer to the Synology DS3617xs as I wanted a decent CPU, ECC RAM and 10GBase-T plus 10-12 disk bays. It cost me Au$1400 vs Au$3100 for the Synology .... plus disks. http://www.quasinerdo.weebly.com
  11. mgrobins

    Jun's Alpha Loader for DSM 6.1

    I'm running on bare metal with a stable Xeon-D build as well with the alpha loader from Jun, and the 2nd most recent update of DSM (not the one released 3 May). I have done my install from scratch using online installation not manual or as an upgrade. I have no odd hardware either - straight Xeon-D SOC using integrated 10G NIC, integrated SATA and an LSI HBA in IT mode. so, it works well with hardware very similar to Synology (DS3617xs). I'll steer clear of the latest 6.1.1 update. Interested to note the SAMBA version is updated. wonder if it includes SMB multichannel now (not that I need it having just shelled out for 10GBe )
  12. mgrobins

    DSM 6.1.x Loader

    I did a fresh install using the 1.0.a2 loader with DS3617xs config on Bare-metal. I used the online install of the latest version of DSM and then updated to Update 2 online. All worked fine. *I do not select any of the connections to synology such as feedback or QC so cannot comment on them. My hardware is in my sig. Note this is a Xeon-D Board I am using which is what is in the 3617xs so I would anticipate good compatibility. NIC is integrated into the CPU SOC on my board (some variants have the i350 chip as well for 1GBe NIC which may be different). I can see packages, have installed the power-off package so manual install is functional and package updates are working. I'll edit and post more here as I examine other deeper features but so far from the last 2 weeks of playing around and rebuilding this a couple of times tweaking stuff I am confident this is a stable build at least on bare metal and generic hardware like I have.
  13. mgrobins

    Power button package

    Perhaps we should look at how to get your WoL going .... Have you checked all of the basics in your mb bios first and confirmed you can wake other devices on your LAN? - WOL enabled for NIC, - PCI-E power state correct - some boards require power management for the PCI-e bus to be set a particular way for the NIC to remain functional in a "power off" state. Perhaps search for WoL for your motherboard and see if there's anything to set there specifically then look to DSM.
  14. mgrobins

    Jun's Alpha Loader for DSM 6.1

    How are people finding the current latest DSP update on this loader in Bare metal installs? Most of the concerns I have seen in this thread have related to VM's. I've only been using basics while building my server but will now start pushing things a bit more. So far I think the basics of networking, shares, smb etc all seem fine. As an aside - DSM suggests using 4k sector size for a windows environment. What gives best performance as I get a message indicating some of my drives are not native 4k? (I'm using Seagate Ironwolf 4TB NAS Drives). My file transfer is generally across SMB to windows machines or to another NAS (RSYNC).
  15. mgrobins

    DSM 6.1.x Loader

    Confirmed this only happens on the 3617xs image. I reverted to a 3615xs Image and it doesn't have this same issue. I am running the DS3617xs loader and have not had issues as of yet. I have a bare metal install. Very little data written to it at this time though as it's a learning setup for me while I build my server. I'm about to put together my proper build and dumnp a lot more on it though. I have not had any issues building a raid 5 array though so far.