• Content Count

  • Joined

  • Last visited

Everything posted by TomS.

  1. Intel's AHCI 1.3 specification [1] states that an AHCI controller must support 32 devices. The Supermicro support page for the AOC-SAS2LP-MV8 Linux driver source link [2] references a mv94xx. On my installation, "find / -iname mv*" returns a listing for an mvsas.ko, but no mv94xx. I don't how to determine version info for kernel modules to see if that module has proper support for your card. Looking at your mainboard, out of the 4 PCI-E slots, only 1 & 2 are x8 link capable even though the slots are full x16 length. You state " the 3rd controller is basically not recognized by th
  2. The first two lines "UDP failed to set…" appear related to an installed program, "Transmission". I'm inclined to agree with your judgment on the kernel lines starting @ 09:31. I'm definitely not a developer or hardware debugger, so don't put too much faith in that agreement. Perhaps you could do a little research on the Intel mainboard you have and the chipset, particularly the southbridge. Compare that with your dmesg output. See if there are more recent drivers than what shipped with the last boot update. //TS
  3. Wonderful, glad it worked. I suspect you'll experience much improved disk performance. I've verified that you do have the latest BIOS for that board. Don't see anything else to change in that regard. With no add in cards, I wonder why those 3ware lines were in the messages log? Doesn't seem relevant now. Best of luck on your new system. //TomS.
  4. Same with me. I'm at my very beginning starting with
  5. I see a couple of potential investigation points: Starting with the Linux ATA wiki [1], ata-piix is for an Intel ICH in IDE emulation mode. ata_qc_issue, from your 1st message log, is preparing a command to issue to a device from [2] I'd address the IDE emulation issue first. Verify that the BIOS is set to SATA native (AHCI) for all storage controllers and not any of the legacy or compatibility modes. * * Caution: changing controller modes is a _destructive_ action. It will invalidate all disk contents. You _must_ repartition / reformat / reinstall DSM. If indeed the storage c
  6. I don't know enough about Samba to tell whether the options are "right" or not. In the extensive output from smbd -b, I see --with Options: […] WITH_ADS […] WITH_DNS_UPDATES It looks like Synology kept Samba 4.x's internal DNS server as well as the option to use external BIND dynamic loading zones. > samba_upgradedns --help Usage: upgradedns [options] Options: -h, --help show this help message and exit --dns-backend= The DNS server backend, default SAMBA_INTERNAL I like the Docker container for the AD DC for three reasons: The ability
  7. Greetings all, DSM 5.2.5967 Update 2 ships with Samba 4.1.18. >smbd -V Version 4.1.18 Synology Build 5967, Apr 26 2016 17:22:47 Samba 4.x is capable of acting as a standalone Active Directory Domain Controller, AD Directory Services in Windows Server Role terms. Build option indicate AD_DC is enabled >smmd -b Build environment: Built by: root@build1 Built on: Tue Apr 26 17:22:21 CST 2016 Built using: /usr/local/i686-pc-linux-gnu/bin/i686-pc-linux-gnu-ccache-gcc Build host: Linux build1 3.14.30-1-lts #1 SMP Fri Jan 30 13:27:48 CST 2015 x86_64 GNU/Linux SRC
  8. @holybabel, Thank you. Perfect information. Big difference in your Supports Wake-on: results: Supports Wake-on: pumbg I'm curious to see reports from Realtek and Broadcomm Nic's now. Look's like a NIC upgrade is in the future.
  9. Greetings all, For those with working Wake-On-LAN (WOL), has anyone configured their NAS to wake on a unicast packet instead of the default magic packet? ethtool -s eth0 wol u The above command returns to the prompt with no feedback for my nForce 430. A look at the adapter status shows that wol is unchanged at Ma"g"ic Packet. nas-ftw> ethtool eth0 Settings for eth0: Supports Wake-on: g Wake-on: g Link detected: yes I suspect other wake modes have not been implemented in forcedeth, Nvidia's nForce 4 driver for Linux because of the "Supports.. line.
  10. @berwhale +1 for IBM article.
  11. Wow, how right you were! I did as you suggested: Thanks, luck sure helps. What does parted's "align opt "n"" where n is each of the labels on the disk report? In particular does it agree that the partitions is aligned? @berwhale, do you know why parted reports sector sizes of 512 bytes physical / 512 bytes logical for the HGST NAS drives when they are Advanced Format Disks, 4096 bytes physical / 512 logical? A pure guess is all I can offer. A quick search indicates that it was a past practice for drivers to allocate /dev/hd(x) to parallel ATA drives and /dev/sd(x) to S
  12. Ilciumba, On my XPE box, uname -rs returns "Linux 3.10.35" and parted returns "GNU Parted v3.1". Both values are more than sufficient for Advanced Format Drive support. I'm not up to par on *nix and *nix like OS, but have a fair amount of experience on other platforms. There are a number of posts on askubuntu about Gparted bugs and AFD disks, no real good answers too much blame. I just started searching the gnu bug-parted mailing list @ Maybe you'll have better luck finding an answer than I have so far. I belive one key answer from
  13. Absolutely agree. The datasheet for the HGST drives in question are silent on the topic though. There is an HGST Advanced Format Technology Brief that discusses HGST drives and relevant operating system support. It emphasizes that Gparted 2.1 or later be used. I must gently disagree. For all operating systems and disk arrangements, sector size matters. For single disks, the minimum file system allocation unit must be a multiple of the sector size. Otherwis