AllGamer

Good news confirmed this 16 port works like a dream I was able to migrate my 2 existing SUPERMICRO AOC-SAS2LP-MV8, into 1 ATTO ExpressSAS H60F Just plug and play. Disk Groups and RAIDs volumes remained intact.

hmm... Hybrid mode is messy. with that many HDDs, I'd have gone RAID10, then it would have been safe to do a repair without worry of losing data. is the Crashed disk, from the new ones that you added, or it is from the existing disk in the hybrid RAID ?

indeed... i've been using 5.2-5644 for the longest time just recently I upgraded to XPEnoboot 5.2-5967 upgrading is not a trivial matter, there are a few Gotchas you need to take care of before an upgrade. I wrote this after the upgrade for fellow XPEnology users viewtopic.php?f=2&t=18157

every forum has spam issues version 6 is stickies above and we are always around chatting and helping new people joining... how it is not active?

This one viewtopic.php?f=2&t=18349 I've never seen a cheap SATA3 with 16 ports, it would be nice if they did maybe soon, now the SATA Express is becoming the new "normal" they should have simply called it SATA4 instead to make it less confusing

Thanks! Good to know it's great to have these type of feedback I also ordered a new 16 port SATA3 card, I'm hoping it works without problems. I'll update once It arrives and get it installed

Good info from this round of diagnostic. With these results you can figure things out, or at least plan around the bug, if there are no better drivers available. One thing I forgot to ask before. Did you enable Jumbo Frames? I noticed things can get a little weird at times when Jumbo frames are enabled. Overall it's great when used with the same type of NIC and switches that supports the same frame size, but as in your example a mix of Intel and Realtek, then Jumbo Frames usually becomes a mess. just something to keep in mind, in case you do have Jumbo enabled.

Very interesting... so, we are suspecting the system 1 (source) both machines are running Intel 1GB NIC but in the middle is NetGear switch, with SNMP enable, and PRTG. Do you happen to have a dumb GB switch around so you can test the same restore between target to source, without the NetGear + SNMP + PRTG ? just my hunch but I might be your switch, sometimes just by disabling the SNMP it will improve the performance. I've noticed that in some networks. From personal experience, Smart Switches are not always the best when you want full speed, many times when I had similar odd throughput issues, it always ends up being the SmartSwitch causing problem, and I was using the Cisco Smart Switches but the cheap business model ones, not the High End server class type. As soon as I used a dumb switch (un-managed switch from any brand) then full speed returns. Now, the reason why most retail edition of Managed Switches acts so crappy, I'll have to attribute it to the low amount of RAM, CPU and chipsets used to handle the traffic. The reason why un-managed switches works without a problem is precisely that, they have nothing to process, no middle-ware to slow down the traffic after the queue fills up. Yet another reference, I've built my own custom switch with pFsense firewall, plenty of RAM 4GB (or 8GB, i forgot), Dual Core intel, all Intel NIC GB cards, and it works like a charm even with all the fancy network filter / tracing / logging /management features enabled, because it got plenty of power and RAM to handle it all. So that is yet another thing you can try, if you have a spare computer, and some 3 spare NIC cards, then you can build a home made switch to verify if it's actually something in the System1 causing the issue, or if it's just the Netgear under performing.

you should read this viewtopic.php?f=2&t=18157

This is VERY interesting, I know PSU can affect other stuff, but never thought HDDs / RAID could be affected due a poor quality PSU. Very nice observation, Sleuth

Thanks! for the feedback. well, if it doesn't work, I can always use it on another project.

Does anyone know if this card is supported by XPEnology? ExpressSAS H60F Low-Profile 16-Internal Port 6Gb/s SAS/SATA PCIe 2.0 Host Bus Adapter Model No. ESAS-H60F-000 https://www.attotech.com/products/adapt ... S-H60F-000

yes, i meant Marvell thanks

yup, I'm not too surprised with the results, as it's you could say "widely known" that's why Intel NIC cards are so much more expensive even on resale on ebay vs. Realtek cards Realtek is usually a no frills low cost solution, performance is usually half of the intel counterpart. Maxwell NIC (or chipset) seems to perform a fair bit better than Realtek, it fits right in between Intel and Realtek but for compatibility sake, usually Intel and Realtek are the safest choices, but go for Intel if you want better performance.

I have a similar Intel® Desktop Board D945GNT the on-board network card is only 100 Mbps I know some models of the D945G series boards are supposed to come with 1000 Mbps, but most are 100 Mbps. Did that motherboard work fine at 1000 Mbps when run in a Windows OS ? or linux OS ?

the synoinfo.conf is the file that contains the information about the amount of SATA drives, eSATA drives, USB ports, and Max number of disks. the synoinfo.conf is inside the .PAT file, I don't know how to edit the .PAT file before upgrading the system. technically speaking that would be the best option, and would save us a lot of trouble if we can pre-edit the synoinfo.conf before it gets deployed. the USB boot doesn't contain this information, it's only used to boot up the kernel to run DSM

I pretty much did the same thing on the first try, only to find out it didn't like it, because when the .pat file was installed, it was only applied to some drives (12 default), but not all drives. so, after the reboot, the DSM will go insane as it detects the old version is still in the remaining drives, and it will automatically boot into factory default mode, with no option for you to repair or recover until you complete the "migration" which basically repeats the same thing over and over, unless i swapped the upgraded drives out, and replaced them with the drives that did not have the update, to get all the drives with the correct version of the update, and then it will boot properly when all the drives are running the proper version. I was hoping that by installing the .pat file, while My version of the synoinfo.conf file was there, it would read and write to all drives, but seems like it gets ignored and uses the version from the .pat file, and the "easy" way didn't work out. next time I upgrade, I'll just eject all drives over #13, let the system do the default 12, then repeat the upgrade again, after ejecting the updating ones, and inserting the remaining 12 drives (13 to 24), since I only have 24 drives, that means only need to 1 swap once, and do the upgrade for each set. It was a good learning experience.

OK... after spending few hours Saving / Recovering from a BAD upgrade, here are a few notes to keep in mind. [Less than 12 HDDs] If you have less than 12 Disk or less in your XPEnology DSM server, it's very safe to upgrade and completely painless. That being said, even if it's "safe" Make sure to Backup Your Data before you even attempt to upgrade, you never know when the universe will throw you a curve ball. [More than 12 HDDs] However! if you have more than 12 Disk in your DSM server... well get ready for some long work. There is no easy way around this, only Safety measure and best practices. 0. Make sure you have the new 5.2-5967.1 USB boot prepared and ready. (I had to create the USB twice, the first time didn't boot from the USB for whatever reason.) 1. Hot Swap eject all your HDD that are above Disk #12, so in my case I have from Disk # 13 to Disk # 24. (I should have ejected them to save myself some trouble) 2. Install or upgrade DSM 5.2-5644.5 to 5.2-5967.1 using the .pat file. 3. After you first boot back into the DSM, it'll be version 5.2-5967.1, you will have lost the settings from your synoinfo.conf, You'll be asked to also configure a few missing settings. (if you have a backup of the Synology settings file, you can restore after you bypass the menus) 5. Before you even bother editing the synoinfo.conf, it is HIGHLY recommended to upgrade the remaining disks 13 to 24 or whatever extras you have, to use the new DSM system partitions. You can use a cloning tool to only copy the system partitions from the existing upgraded volumes (any disk from 1 to 12) or You can go CYCLE your additional volumes located on Disk #13 and above. Both methods are tedious, as it require you to eject physical HDDs in volume groups to work with. I went with the Disk Cycling option, as it was a little more straightforward, but still annoying. From my disks 1 to 12, I had 2 separate volumes there, which made the job a little bit easier. When I created this server I knew and I expected this kind of trouble, so I intentionally created 1 large volume with 8 disks and a smaller volume with 4 disks, this let me easily swap the volumes in and out of the server via Hot Swap. So, I removed a full volume set of 8 disks then I proceeded to swap in the remaining Volumes that are still with the old DSM 5.2-5644.5 system partitions when you plug them in, it will be detected as Crashed, and It will ask you to Repair Repair is safe, by selecting Repair, it will update the DSM partitions to the new 5.2-5967.1 system partitions, your data will not be touched. So repeat this process a few time, until all your additional disks and volumes from Disk 13 and above are upgraded to the new DSM version. Once that is done, it'll be safe to update the synoinfo.conf to enable the additional drives. [Why?] Now, You'll probably ask WHY? not update synoinfo.conf first, and then not have to do the Hot Swap music chair? Because I tried the lazy way frst and it doesn't work, as soon as the new DSM 5.2-5967.1 boots up and detects some disks partitions are still running the old 5.2-5644.5, the DAMN thing will automatically reboot your machine to force it into Factory Default mode, then you'll be forced to do the steps 1 to 4 again, and all the hard work is gone and you need to start from scratch again. This is how I lost a few hours, when it could have been done in less than 30 min. I tried the other lazy way by adding the HDD after the upgrade, hoping it will offer you the option to "Repair" ... but nope, they will be detected as Brand NEW HDDs ("not initialized"), and you WILL lose your data if you select the option to create volume or initialize the disk. If you leave the HDDs pluged-in then it causes the endless reboot, because it keeps going into Factory Default mode. So, the only Safeway, and trouble free way, is by doing the Music Chair upgrade with the volume sets, or cloning the 5.2-5967.1 system partitions to the remaining drives.

Just make sure it's not using a SATA multiplier chip. otherwise it'll only read 4 devices, instead of 8, or 16, or whatever it is supposed to be.

If you can boot from YUMI, it should be able to boot just the same with the XPEnology boot. maybe the.img file is corrupted, or not closed / saved properly if you made changes to it. try downloading a fresh copy of the .img file, and then Win32 disk image the USB stick again. the contents inside the .img is basically the same thing you'll find in YUMI, it's just 1 OS, instead of multiple OS / utilities. As a work around, if it still fails, you can try to create a YUMI usb stick out of the ISO for XPEnology, and have YUMI automatically boot to XPEnology every time, you'll have to modify YUMI default boot choice. Additional thing you can check, maybe your BIOS requires to turn on all USB to run either in legacy mode, or some other features related to USB options provided by the motherboard manufacture.

without doing anything special, I am able to login as root, with the password of the 1st created account, by default it becomes your admin account. for example my very first user created was Sam, then whenever I try to login as Root, I type in Sam's password and it works.

I personally believe otherwise, compared QNAP vs. Synology, DSM always end up being the most feature complete for everything you need. QNAP is more geared towards Media Player / streaming, DSM works better as a full featured server, which includes Media Play and Streaming, DSM also have more 3rd party Non Synology plug-ins and support, while for QNAP there isn't much to see outside official channels.

maybe a screenshot might help i've never seen an error saying " - "

yes, it is quite easy actually. unplug your USB stick from the XPE DSM, then plug it to any windows computer use Notepad++ open the syslinux file, and change the Serial # + MAC # inside the file. You might also want to hide the USB from XPE DSM, and optionally hide PATA ATA IDE devices if you only plan to use SATA ports. Link for serial / mac generator http://quickconnector.orgfree.com/index.php About hiding IDE devices: edit syslinux.cfg to remove mod for IDE support, add rmmod=ata_piix to the end of every lines that start with “kernel /ZImage” Link to hide USB boot drive: viewtopic.php?f=2&t=17066

yeah, technically speaking it is possible. When you setup a Web Site App, or your own custom website, just make sure to request SQL queries to the full DNS name of the MySQL server instead of using "localhost" just replace any default "localhost" parameters for SQL query to say the DNS name or IP address where the SQL server is located. if it's on the same side of the firewall, you can use internal IP, if it's else in the world, you can use the the external IP address or FQDN For example when you setup a LAMP server (not the Synology built-in stuff) you can customize where is the Linux server IP, the Apache server IP, the MySQL server IP, and the PHP server IP