Search the Community

Same here on a SuperMicro motherboard. I'm not using onboard SATA though -- have disks hooked up to LSI SAS HBAs. scemd segfaults and system shuts off.

Hi, Router is not working as i'm using a dsr-1000n which doesn't support WoL sending. Also it's good to know that i'm not the only one with this issue occuring I currently TRY to check if the bios internal Wake on Event is working. There i can at least define one time (in UTC format) where the device should start. [i'll report about that later..] also i checked the "rtcwake" but it's not working as there is no /dev/rtc0. MAYBE on of the developers (like Trantor) could have a look how exactely the integrated scheduler works, also see if we maybe could get the "rtcwake" up and running. Additionally i wrote the Supermicro support, let's see how they react and if they're willing to help me.. BR snoopy78

Hello, currently i'm facing an issue with DSM 4.3180 Beta 5 HBA. Mainboard: Supermicro X8SIL-F CP: Quad Xeon X3430 RAM: 8 GB HBA: LSI 9201-16i NIC: HP NC523SFP (10Gbe) Boot = USB onboard DATA 5 = Sandisk SSD 128 GB (Volume 1, System) 13x HDD connected to HBA As soon as i create & enable automatic startup schedule [control pannel => hardware => power schedule] of my new Sytem i'll get every time when i boot the "CMOS CHECKSUM ERROR" which causes the system to hold and wait for F1=setup or F2=def. settings When i continue with default settings (press F2) the system wil boot up fine, however after next reboot the same error comes again. Did you guys saw this issue too? How to solve it? I really would love to use that feature for energy/noise saving.. BR snoopy78

I think I successfully used passthrough in Ubuntu 13.10. I didn't see the disks attacked but think I was able to see the controller (also no crash at OS boot). lshw -class disk -class storage *-ide description: IDE interface product: 82371AB/EB/MB PIIX4 IDE vendor: Intel Corporation physical id: 7.1 bus info: pci@0000:00:07.1 version: 01 width: 32 bits clock: 33MHz capabilities: ide bus_master configuration: driver=ata_piix latency=64 resources: irq:0 ioport:1f0(size=8) ioport:3f6 ioport:170(size=8) ioport:376 ioport:1060(size=16) *-scsi description: SCSI storage controller product: 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI vendor: LSI Logic / Symbios Logic physical id: 10 bus info: pci@0000:00:10.0 logical name: scsi2 version: 01 width: 64 bits clock: 33MHz capabilities: scsi bus_master rom scsi-host configuration: driver=mptspi latency=64 maxlatency=255 mingnt=6 resources: irq:17 ioport:1400(size=256) memory:feba0000-febbffff memory:febc0000-febdffff memory:40008000-4000bfff *-disk description: SCSI Disk physical id: 0.0.0 bus info: scsi@2:0.0.0 logical name: /dev/sda size: 8GiB (8589MB) capabilities: partitioned partitioned:dos configuration: sectorsize=512 signature=0004e196 *-storage description: SATA controller product: 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] vendor: Intel Corporation physical id: 0 bus info: pci@0000:0b:00.0 version: 04 width: 32 bits clock: 66MHz capabilities: storage msi pm ahci_1.0 cap_list configuration: driver=ahci latency=64 resources: irq:72 ioport:5038(size=8) ioport:5030(size=4) ioport:5028(size=8) ioport:5024(size=4) ioport:5000(size=32) memory:fd4fe800-fd4fefff *-scsi physical id: 1 logical name: scsi1 capabilities: emulated *-cdrom description: DVD-RAM writer physical id: 0.0.0 bus info: scsi@1:0.0.0 logical name: /dev/cdrom logical name: /dev/sr0 capabilities: audio cd-r cd-rw dvd dvd-r dvd-ram configuration: status=open edit: @gnoboot would this card work http://www.supermicro.com/products/acce ... LP-MV8.cfm ? I see in your supported drivers list you have Marvell 88SE6440 SAS/SATA controller, but this card is 88SE6480 (8 ports).

My experience tells me funny thing. We have a dangerous server, if you say reboot - the machine is switched off. Not much fun when the server is in another city. And all thanks to Supermicro.

I'm installing in a 24bay SuperMicro Chassis. Server has Xeon 5650 CPU, 24GB RAM, 10gig Ethernet, and 3 LSI HBAs. I haven't had much luck with the DS3612 codebase. I can get all the drives to show up after editing synoinfo.con but things always end up breaking Have you tried this guide - viewtopic.php?f=2&t=2028? No, it only happens when you passthrough. So your controller is ASM1061, I suggest you install latest Ubuntu/CentOS and try it again. If it doesn't break then its Synology kernel bug, will try to find the patch from kernel.org. Edit: @Diverge, found a possible patch.

I'm installing in a 24bay SuperMicro Chassis. Server has Xeon 5650 CPU, 24GB RAM, 10gig Ethernet, and 3 LSI HBAs. I haven't had much luck with the DS3612 codebase. I can get all the drives to show up after editing synoinfo.con but things always end up breaking

Hallo, ich habe das gleiche Problem mit einem Supermicro X8SIL-F Mainboard und DSM 4.3 Beta5 HBA. Ich habe bei mir festgestellt, dass der Fehler immer dann auftritt, wenn das automatische EINschalten aktivirt ist. autom. Ausschalten scheint den Fehler nicht zu verursachen. Wie habt Ihr das gelöst? Wenn überhaupt? Danke

I just bought parts to build a server, will I be able to install XPEnology's DSM on it? The major parts are: SUPERMICRO MBD-X9SCL-F-O LGA 1155 Intel C202 Micro ATX Intel Xeon E3 Server Motherboard Intel Xeon E3-1230 V2 Ivy Bridge 3.3GHz (3.7GHz Turbo) 4 x 256KB L2 Cache 8MB L3 Cache LGA 1155 69W Quad-Core Server Processor BX80637E31230V2 Kingston 32GB (4 x 8GB) 240-Pin DDR3 SDRAM ECC Unbuffered DDR3 1600 Server Memory w/TS Model KVR16E11K4/32 WD 3TB RED I bought that stuff particularly with FreeNAS in mind, but than found out I might be able to use this modified Synology DSM instead. I've got two Synology NAS's already, so I'm more comfotable with DSM than learning FreeNAS/FreeBSD from scratch. My other questions are: How safe if your data compared to an original Synology NAS? One of things making me a little nervous about FreeNAS, is that as safe as it's supposed to keep your data, it seems relatively easy to lose it because of hardware screwups. For instance, a power failure (although I do have a UPS I will hook up), booting up with a hard drive unplugged can corrupt your data permanently. Are these problems possible with this modified DSM as well? (They probably are present in an original Synology NAS also, but the hands off approach of the official NAS, minimizes some of those problems.) Along those same lines, how easy is it to add drives and expand the RAID volume? My original plan was to build a server, than save money on storage and upgrade as I continually filled it up. FreeNAS doesn't really allow that to happen. Official Synology NAS's do. Can I gradually add more (3TB) hard drives and will this modified DSM expand correctly? Is your data at risk of loss during this whole process? Thanks, and I guess the first question might make the rest of them null and void, but I'd still be interested to know.

i'm just consolidating my storages.. currently i'm running 1x TS-509Pro (5x1,5 TB Raid5), 1x TS-412 (4x2 TB Raid 5) and 1x DS-1812+ (8x3 TB Raid 6). So my new system is a Supermicro SC836 chassis and an X8SIL-F mb with x3550 cpu and 8 gb ram & 10G NIC. All HDDs from the QNAPs are moving into that chassis (including 3x WD Red 4 TB) and i'm setting up SHR for 5x 1,5 , 5x 2 and 3x4 TB (so having 3 volumes so far) Both of my Qnaps are going to retire and move into my familys use. My DS-1812+ will become my backup while the new SC836 is becomming main storgage. How to say, for now i've got it stable up and running using Trantors 4.3 v5 HBA version. But as we all know, RAID is NOT a Backup! So i will surely keep a backup on my real DS-1812+. But what do you mean with production enviroment? If you're a company you should by the real thing, but for us private users that's a cheap and good way to get a lovely performant diskstation.. p.s. before i upgrade or migrate the "live" system of course i do have a small HP-ML310 server for testing, that's what you pay for when you buy the real thing.. support & testing..

Trantor, I've finally got a chance to turn on my AMD server again. Using XPEnology DS3612xs DSM 4.3 build 3810++ (repack v1.0)... I'm happy to report that the Marvell SATA driver is working beautifully now that's it's a built-in module. I'm also happy to report powernow-k8.ko is working great as well. My AMD Opteron 8384 shows all four P-States after insmod powernow-k8.ko and I can change the frequency governor to on demand with cpufreq-set. I've 12 drives so far in the system and will be adding 12 more soon to max out my Supermicro server. Thanks for incorporating these in the last several releases, and please do continue to have them in future releases.

My GA-E350N WIN8 was $70, and I thought I saw the Supermicro for $500. Good to know it cost much less. Yeah 5 years would be a good run for a mobo, especially for my server. I seem to upgrade way too often. I probably wouldn't do that if I spent $350 instead of $70 for a mobo. It would save me money in the long run, if I factor in my time. Plus I hate AMD boards and I can imagine having to spend extra time getting a new NIC to work because I didn't buy an intel chipped mobo.

After a long and sometimes painful journey I have a nearly working system Still not sure whats going on with getting the later SAS cards working properly. But using 2 of the older 1068e cards I have 8 drives of SAS controllers and 6 off of the Motherboard all nicely working Lessons learned along the way Using INTEL 6 Bay SAS Expander cages, with either 1068e or 2008 based LSI cards was not working with SATA drives at all. Worked perfectly with any SAS drive I installed in them Spend a good while working out how to update the backplane firmware on them...making special cables up and having to ONLY use a genuine intel server board to peform the updates... My backplanes were firmware 2.05 and 2.06.....managed to get them both updated to 2.14 finally......didn't bother updating them to 2.18 as from the readme files...there is no change in the firmware. Just version number changes to suit certain INTEL server boards. Still even after all the updating, SATA drives were not recognised properly.... came up as SSD's and smart temperature monitoring was @ -1c....no way around it sadly. Direct connecting them to the controllers worked fine So back to the Supermicro Chassis and the Gigabyte P55-UD3R Motherboard (which is a real painful motherboard by the way) The only way I could get it working was to dissable everything except the 6 onboard Intel SATA ports (dissable the G-SATA and the E-SATA ports) Even then it didn't want to work at all in ACHI mode. It only likes IDE mode and that sucks. So Gigabyte P55-UD3R Motherboard Intel Xeon X3450 16 GB Ram HP SC44Ge card in 16x PCI-E Slot HP SC44Ge card in 8x PCI-E Slot Old Nvidia Geforce MX4400 card in PCI Slot Single port Intel Pro adapter in PCI slot Can boot and install to either just the SAS Ports Can boot and install to either just the SATA Ports Or any combination of the above Currently I have 8 drives off of the SAS cards and 6 off of the SATA ports and it's happy Reboots not a problem, even in the middle of a volume rebuild... it picks it back up and continues. Still not sure whats going on with the Later SAS cards.....some incompatibilty somewhere with the hardware I have at hand. This hardware is way overkill for what I will end up with... What I will end up with is something along the lines of an Intel S3200SH Socket 775 server board or similar Lower power Takes 8gig Ram (more than enough) has 3 x PCI-E Slots (for SAS HBA's and a quad port Lan Card) 2 x Onboard Intel Lan Ports Will pop in a Q8200 Quad core cpu That should be plenty powerful enough for all I currently need in a NAS. Ample RAM 6 x Lan ports for Bonding into 3 different subnets Serving VM's Media storage and serving etc Will still attack getting these H200 and H310 cards working properly though

G'day all, Just wondering what is the max number of drives I can use to setup a decent Xpenology box? Currently I have 2 Xpenology boxes up and running fine. (HP EX490's) But I have the following hardware and would like to combine it (either real or virtual) into a giant Xpenology NAS Supermicro 15 bay SAS/ SATA case Supermicro 8 bay SAS/SATA case Intel 6 bay case Looking to do the following Intel case with 6 internal SATA plus an external sas card, connected to both Supermicro cases via sas expanders So that would give me approx 30 drives Would the number be to high? Eg is the limit say 16drives max? Thanks .

I had a play with this today for testing 2 x Supermicro 1RU servers 20g ram 2 x 250g drives in each, setup as a mirror (High Availability doesnt allow SHR) 2 x Intel Lan ports setup 1st one with 4.3 3810 v1.0 from trantor once installed, I broke the SHR config and rebuilt as a mirror set RAID1 setup local time properly added a user made sure networking was setup properly edited grub.conf to reflect the propery mac address's in each server and both had different serial numbers Set static IP's Server 1 lan port 1 = 10.0.0.52, 255.255.255.0 < lan port 2 = 192.168.0.1 255.255.255.0 <<< which doesn't matter as HA software changes this later too 169.254.1.1 255.255.255.252 Server 2 lan port 1 = 10.0.0.53, 255.255.255.0 < lan port 2 = 192.168.0.2 255.255.255.0 <<< which doesn't matter as HA software changes this later too 169.254.1.1 255.255.255.252 Connected a cable direct from Server 1 to Server 2 both on Lan port 2 Double checked that all ports were running @ 1000Mbps......as 2 were not 1st off.....swap some cables around until all 4 ports were up @ Gigabit Then off to install HA package (which 1st need you to install the python package) Tested the setup, but yes it fails at the end Then I thought, as each server has two ip addresses on Lan port 1.....eg one that you setup, then I guess a virtual / bridged one that you type in in the setup.... it must need bridging enabled?? had a looksee and it seems the bridge module isn't loaded... /lib/module/bridge.ko is there so lets load it insmod /lib/module/bridge.ko fails as it need also /lib/module/stp.ko and /lib/module/llc.ko now with all three loaded lets try again...... now it fails with Jan 1 23:03:50 SUPER1 ha.cgi: write to uart2 error, error=(5)Input/output error Jan 1 23:03:50 SUPER1 ha.cgi: ha.cc:1712: SYNOHWExternalControl failed 8192 which I wonder is something to do with the serial port? which I will enable next.... tho I wonder if the REAL hardware has something attached to a serial port inside it? .

Whats that saying? Third time lucky? ok 3rd system Supermicro 1RU SUPERSERVER 6015V-MT Motherboard = X7DVL-3 Memory = 20Gb 4 x SATA Bays Flying blind, without a monitor or keyboard attached.... I thought what the heck. Added 1 x 1TB SATA drive to internal bay Booted and all looked good Added LSI 1068e card (HP SC44Ge with IT Mode Firmware) With nothing connected rebooted all seems good Added a HP MSA70 SAS Enclosure.... 25 x 2.5inch Bays SAS Array connected to the SC44Ge Took ages and ages for Synology assistant to find it But finally it was available to log in. Looks good A bit of a tweak here and there at some config files and we have But even tho it finds all drives in the MSA70 Enclosure [ 379.509990] scsi 2:0:25:0: Enclosure HP MSA70 2.18 PQ: 0 ANSI: 5 [ 379.751067] ses 2:0:25:0: Attached Enclosure device [ 385.623586] SCSI device (2:0:0:0) with disk name (sdc) plugged in SLOT01 of enclosure(2:0:25:0), HP -MSA70 [ 386.083136] SCSI device (2:0:1:0) with disk name (sdd) plugged in SLOT02 of enclosure(2:0:25:0), HP -MSA70 [ 386.542671] SCSI device (2:0:2:0) with disk name (sde) plugged in SLOT03 of enclosure(2:0:25:0), HP -MSA70 [ 386.984476] SCSI device (2:0:3:0) with disk name (sdf) plugged in SLOT04 of enclosure(2:0:25:0), HP -MSA70 [ 387.444420] SCSI device (2:0:4:0) with disk name (sdg) plugged in SLOT05 of enclosure(2:0:25:0), HP -MSA70 [ 387.885200] SCSI device (2:0:5:0) with disk name (sdh) plugged in SLOT06 of enclosure(2:0:25:0), HP -MSA70 [ 388.345190] SCSI device (2:0:6:0) with disk name (sdi) plugged in SLOT07 of enclosure(2:0:25:0), HP -MSA70 [ 388.784995] SCSI device (2:0:7:0) with disk name (sdj) plugged in SLOT08 of enclosure(2:0:25:0), HP -MSA70 [ 389.244861] SCSI device (2:0:8:0) with disk name (sdk) plugged in SLOT09 of enclosure(2:0:25:0), HP -MSA70 [ 389.702687] SCSI device (2:0:9:0) with disk name (sdl) plugged in SLOT10 of enclosure(2:0:25:0), HP -MSA70 [ 390.132529] SCSI device (2:0:10:0) with disk name (sdm) plugged in SLOT11 of enclosure(2:0:25:0), HP -MSA70 [ 390.585532] SCSI device (2:0:11:0) with disk name (sdn) plugged in SLOT12 of enclosure(2:0:25:0), HP -MSA70 [ 391.020461] SCSI device (2:0:12:0) with disk name (sdo) plugged in SLOT13 of enclosure(2:0:25:0), HP -MSA70 [ 391.476485] SCSI device (2:0:13:0) with disk name (sdp) plugged in SLOT14 of enclosure(2:0:25:0), HP -MSA70 [ 391.913268] SCSI device (2:0:14:0) with disk name (sdq) plugged in SLOT15 of enclosure(2:0:25:0), HP -MSA70 [ 392.370543] SCSI device (2:0:15:0) with disk name (sdr) plugged in SLOT16 of enclosure(2:0:25:0), HP -MSA70 [ 392.809047] SCSI device (2:0:16:0) with disk name (sds) plugged in SLOT17 of enclosure(2:0:25:0), HP -MSA70 [ 393.269492] SCSI device (2:0:17:0) with disk name (sdt) plugged in SLOT18 of enclosure(2:0:25:0), HP -MSA70 [ 393.730727] SCSI device (2:0:18:0) with disk name (sdu) plugged in SLOT19 of enclosure(2:0:25:0), HP -MSA70 [ 394.169666] SCSI device (2:0:19:0) with disk name (sdv) plugged in SLOT20 of enclosure(2:0:25:0), HP -MSA70 [ 394.793862] SCSI device (2:0:20:0) with disk name (sdw) plugged in SLOT21 of enclosure(2:0:25:0), HP -MSA70 [ 395.972340] SCSI device (2:0:21:0) with disk name (sdx) plugged in SLOT22 of enclosure(2:0:25:0), HP -MSA70 [ 397.013308] SCSI device (2:0:22:0) with disk name (sdy) plugged in SLOT23 of enclosure(2:0:25:0), HP -MSA70 [ 397.717502] SCSI device (2:0:23:0) with disk name (sdz) plugged in SLOT24 of enclosure(2:0:25:0), HP -MSA70 [ 398.158674] SCSI device (2:0:24:0) with disk name (sdaa) plugged in SLOT25 of enclosure(2:0:25:0), HP -MSA70 [ 408.352574] scsi 0:0:0:0: Attached scsi generic sg0 type 5 [ 408.352746] sd 1:0:0:0: Attached scsi generic sg1 type 0 [ 408.352926] sd 2:0:0:0: Attached scsi generic sg2 type 0 [ 408.353199] sd 2:0:1:0: Attached scsi generic sg3 type 0 [ 408.353368] sd 2:0:2:0: Attached scsi generic sg4 type 0 [ 408.353544] sd 2:0:3:0: Attached scsi generic sg5 type 0 [ 408.353715] sd 2:0:4:0: Attached scsi generic sg6 type 0 [ 408.353887] sd 2:0:5:0: Attached scsi generic sg7 type 0 [ 408.354161] sd 2:0:6:0: Attached scsi generic sg8 type 0 [ 408.354337] sd 2:0:7:0: Attached scsi generic sg9 type 0 [ 408.354827] sd 2:0:8:0: Attached scsi generic sg10 type 0 [ 408.355012] sd 2:0:9:0: Attached scsi generic sg11 type 0 [ 408.355186] sd 2:0:10:0: Attached scsi generic sg12 type 0 [ 408.355363] sd 2:0:11:0: Attached scsi generic sg13 type 0 [ 408.355535] sd 2:0:12:0: Attached scsi generic sg14 type 0 [ 408.355719] sd 2:0:13:0: Attached scsi generic sg15 type 0 [ 408.355895] sd 2:0:14:0: Attached scsi generic sg16 type 0 [ 408.356145] sd 2:0:15:0: Attached scsi generic sg17 type 0 [ 408.356311] sd 2:0:16:0: Attached scsi generic sg18 type 0 [ 408.356486] sd 2:0:17:0: Attached scsi generic sg19 type 0 [ 408.356662] sd 2:0:18:0: Attached scsi generic sg20 type 0 [ 408.357010] sd 2:0:19:0: Attached scsi generic sg21 type 0 [ 408.357188] sd 2:0:20:0: Attached scsi generic sg22 type 0 [ 408.357364] sd 2:0:21:0: Attached scsi generic sg23 type 0 [ 408.357537] sd 2:0:22:0: Attached scsi generic sg24 type 0 [ 408.357715] sd 2:0:23:0: Attached scsi generic sg25 type 0 [ 408.357891] sd 2:0:24:0: Attached scsi generic sg26 type 0 [ 408.358142] ses 2:0:25:0: Attached scsi generic sg27 type 13 Only 16 come up in the Storage Manager tho Can someone explain Binary to me, so I can configure my USB, E-SATA, INTERNALPORTS in the synoinfo.cfg files ? currently have E-SATA set to 0x00000 usbports set to 0x3f internalports set to 0xffff Thanks .

Another update Tried to make myself a LARGE Xpenology proxmox setup, but ran into some limitations Case = Supermicro sc933t-r760b (15 x 3.5inch bays) Motherboard = Gigabyte P55-UD3R CPU = Xeon X3450 Memory = 8Gb Dell H310 SAS Controller Installed ProxMox onto a 640G drive in bay 1 Made a new VM Other OS Type 4Gb Memory 1Gb IDE Drive Tried to assign 10 Drives to the Xpenology VM... but here is where the problem lies MAX SATA drives you can assign to a VM = 6 MAX IDE drives you can assign to a VM = 4 MAX SCSI drives you can assign to a VM = 16 Tried Trantors 3810 repack v1.0 http://xpenology.com/forum/viewtopic.php?f=14&t=1700#p7980 But it didn't like something. With 3 x 1TB IDE (can't use IDE0 as thats for the fake USB stick to boot) and 6 x 1TB SATA drives assigned, the install goes well... overwrites the synoboot-trantor-4.3-3810-v1.0.img naturally replace the synoboot-trantor-4.3-3810-v1.0.img / reboot and and it fires up Can see the drives, but complains about the volume being stuffed. (because it was made from initially 9 x 1TB and 1 x 1Gb (the boot .img) drives So off to storage manager and remake the lot again.... this time skipping the 1Gb boot .img Seems to go fine.... but you can see it having troubles in the console output Lots of want_idx 5 index 6 want_idx 6 index 7 errors and it's having trouble with choosing which mode to talk to the drives in some drives spit out configured for MWDMA2/100 other spit out configured for UDMA/133 some negotiate at 1.5Gbps, others 3.0Gbps once the volume is complete Shutdown restart CRASHES with major EXT4 errors that I can't seem to fix. doing a df on the VM show major weirdness going on eg before any files copied or anything done Volume = 7TB Used = 4.5TB Tried lots of different ways... Made the VM without IDE drives, no difference Made it with SCSI drives... can't boot Maybe we need to compile proper virtio drivers for it to work efficently? Example errors 29.442391] ata1.00: configured for UDMA/100 [ 29.442995] ata1: EH complete [ 29.443611] ata2.00: configured for UDMA/100 [ 29.444307] ata2: EH complete [ 29.445022] ata3.00: configured for UDMA/100 [ 29.445676] ata3: EH complete [ 29.446947] ata7.00: configured for MWDMA2 [ 29.447551] ata7: EH complete [ 29.477663] netlink: 12 bytes leftover after parsing attributes. [ 35.974383] loop: module loaded [ 36.222399] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [ 36.223222] ata1.00: irq_stat 0x40000001 [ 36.223774] ata1.00: failed command: FLUSH CACHE EXT [ 36.224452] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 [ 36.224453] res 41/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error) [ 36.226181] ata1.00: status: { DRDY ERR } [ 36.226905] ata1.00: configured for UDMA/100 [ 36.227500] ata1.00: retrying FLUSH 0xea Emask 0x1 [ 36.228200] ata1.00: device reported invalid CHS sector 0 [ 36.228872] ata1: EH complete [ 36.250525] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [ 36.251261] ata3.00: irq_stat 0x40000001 [ 36.251825] ata3.00: failed command: FLUSH CACHE EXT [ 36.252453] ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 [ 36.252453] res 41/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error) [ 36.254268] ata3.00: status: { DRDY ERR } [ 36.254975] ata3.00: configured for UDMA/100 [ 36.255570] ata3.00: retrying FLUSH 0xea Emask 0x1 [ 36.256249] ata3.00: device reported invalid CHS sector 0 [ 36.256947] ata3: EH complete [ 36.446143] findhostd uses obsolete (PF_INET,SOCK_PACKET) [ 59.517725] md: md0: resync done. [ 59.539980] md: resync of RAID array md1 Then later 205.264134] ata1.00: device reported invalid CHS sector 0 [ 205.264817] ata1: EH complete [ 205.265589] ata2.00: device reported invalid CHS sector 0 [ 205.266443] ata2: EH complete [ 205.267373] ata3.00: configured for UDMA/100 [ 205.267934] ata3.00: retrying FLUSH 0xea Emask 0x1 [ 205.268713] ata3.00: device reported invalid CHS sector 0 [ 205.269447] ata3: EH complete [ 209.244813] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [ 209.245621] ata2.00: irq_stat 0x40000001 [ 209.246175] ata2.00: failed command: FLUSH CACHE EXT [ 209.246824] ata2.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 [ 209.246824] res 41/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error) [ 209.248552] ata2.00: status: { DRDY ERR } [ 209.249259] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [ 209.249960] ata3.00: irq_stat 0x40000001 [ 209.250519] ata3.00: failed command: FLUSH CACHE EXT [ 209.251154] ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 [ 209.251155] res 41/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error) [ 209.252861] ata3.00: status: { DRDY ERR } [ 209.253810] ata2.00: configured for UDMA/100 [ 209.254448] ata2.00: retrying FLUSH 0xea Emask 0x1 [ 209.255185] ata2.00: device reported invalid CHS sector 0 [ 209.277912] ata2: EH complete [ 209.278876] ata3.00: configured for UDMA/100 [ 209.279454] ata3.00: retrying FLUSH 0xea Emask 0x1 [ 209.280139] ata3.00: device reported invalid CHS sector 0 No volume All drives recognised as SSD's with no SMART data (naturally) Later Speed drops even more 412.016564] ata3: EH complete [ 415.663388] ata3.00: limiting speed to UDMA/66:PIO4 [ 415.664168] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 [ 415.664966] ata3.00: irq_stat 0x40000001 [ 415.665625] ata3.00: failed command: FLUSH CACHE EXT [ 415.666432] ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 [ 415.666433] res 41/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error) [ 415.668452] ata3.00: status: { DRDY ERR } [ 415.669174] ata3: hard resetting link [ 415.974170] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [ 415.975031] ata3.00: configured for UDMA/66 [ 415.975575] ata3.00: retrying FLUSH 0xea Emask 0x1 [ 415.976282] ata3.00: device reported invalid CHS sector 0 [ 415.976964] ata3: EH complete [ 417.662362] ata1.00: limiting speed to UDMA/66:PIO4 [ 417.663221] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 [ 417.663932] ata1.00: irq_stat 0x40000001 [ 417.664552] ata1.00: failed command: FLUSH CACHE EXT [ 417.665152] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 [ 417.665153] res 41/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error) [ 417.666957] ata1.00: status: { DRDY ERR } [ 417.667567] ata1: hard resetting link [ 417.668175] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [ 417.668895] ata2.00: irq_stat 0x40000001 [ 417.669485] ata2.00: failed command: FLUSH CACHE EXT [ 417.670094] ata2.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 [ 417.670095] res 41/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error) [ 417.671893] ata2.00: status: { DRDY ERR } [ 417.672827] ata2.00: configured for UDMA/100 [ 417.673398] ata2.00: retrying FLUSH 0xea Emask 0x1 [ 417.674059] ata2.00: device reported invalid CHS sector 0 [ 417.674820] ata2: EH complete [ 417.975450] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [ 417.976267] ata1.00: configured for UDMA/66 [ 417.976933] ata1.00: retrying FLUSH 0xea Emask 0x1 [ 417.977705] ata1.00: device reported invalid CHS sector 0 [ 417.978377] ata1: EH complete [ 424.342755] EXT4-fs (dm-0): barriers disabled [ 424.453973] EXT4-fs (dm-0): mounted filesystem with writeback data mode. Opts: usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,synoacl,data=writeback,oldalloc [ 424.532457] EXT4-fs (dm-0): re-mounted. Opts: usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,synoacl [ 424.543915] EXT4-fs (dm-0): re-mounted. Opts: (null) [ 424.564745] EXT4-fs (dm-0): re-mounted. Opts: (null) [ 435.077838] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [ 435.078634] ata3.00: irq_stat 0x40000001 [ 435.079183] ata3.00: failed command: FLUSH CACHE EXT [ 435.079826] ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 [ 435.079827] res 41/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error) [ 435.082694] ata3.00: status: { DRDY ERR } [ 435.084111] ata3.00: configured for UDMA/66 [ 435.084785] ata3.00: retrying FLUSH 0xea Emask 0x1 [ 435.085699] ata3.00: device reported invalid CHS sector 0 [ 435.086535] ata3: EH complete Volume gets created again Output of DF before reboot DiskStation> df Filesystem 1K-blocks Used Available Use% Mounted on /dev/md0 2451064 490516 1858148 21% / /dev/md0 2451064 490516 1858148 21% /proc/bus/pci /tmp 2026972 324 2026648 0% /tmp /dev/vg1000/lv 1913539412 246400 1913190612 0% /volume1 Massive errors on reboot eg [ 26.178209] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14789 failed (2329!=0) [ 26.179321] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14790 failed (13801!=0) [ 26.180430] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14791 failed (57784!=0) [ 26.181539] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14792 failed (11912!=0) [ 26.182650] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14793 failed (64217!=0) [ 26.183770] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14794 failed (50729!=0) [ 26.185550] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14795 failed (4728!=0) [ 26.186748] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14796 failed (49097!=0) [ 26.187861] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14797 failed (27544!=0) [ 26.188973] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14798 failed (22376!=0) [ 26.190258] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14799 failed (33593!=0) [ 26.191380] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14800 failed (35083!=0) [ 26.192492] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14801 failed (23898!=0) [ 26.193606] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14802 failed (25002!=0) [ 26.194726] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14803 failed (46587!=0) [ 26.195809] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14804 failed (6218!=0) [ 26.196931] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14805 failed (52251!=0) [ 26.198052] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14806 failed (61675!=0) [ 26.199163] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14807 failed (9402!=0) [ 26.200273] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14808 failed (60298!=0) [ 26.201390] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14809 failed (16347!=0) [ 26.202499] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14810 failed (811!=0) [ 26.203601] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14811 failed (55162!=0) [ 26.204715] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14812 failed (31435!=0) [ 26.205833] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14813 failed (44698!=0) [ 26.206941] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14814 failed (37482!=0) [ 26.208076] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14815 failed (17979!=0) [ 26.209195] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14816 failed (34318!=0) [ 26.210315] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14817 failed (21087!=0) [ 26.211428] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14818 failed (28335!=0) [ 26.212533] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14819 failed (47870!=0) [ 26.213644] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14820 failed (5967!=0) [ 26.215430] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14821 failed (49950!=0) [ 26.216701] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14822 failed (65518!=0) [ 26.217816] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14823 failed (11199!=0) [ 26.218922] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14824 failed (58511!=0) [ 26.220044] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14825 failed (12510!=0) [ 26.221223] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14826 failed (3118!=0) [ 26.222335] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14827 failed (55423!=0) [ 26.223451] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14828 failed (30158!=0) [ 26.224570] EXT4-fs (dm-0): ext4_check_descriptors: Checksum for group 14829 failed (41375!=0) Contradicting messages when logging in Volume has been successfully created, but behind it error Volume crashed DiskStation> df Filesystem 1K-blocks Used Available Use% Mounted on /dev/md0 2451064 493432 1855232 21% / /dev/md0 2451064 493432 1855232 21% /proc/bus/pci /tmp 2026972 308 2026664 0% /tmp .

I believe BIOS reset issue is a hardware compatibility issue, not a software issue. I think DSM wants to keep time using GMT and not your local time zone. Like all modern OS, DSM wants to modify the BIOS to its correct time (GMT). Since your BIOS is not compatible with the way DSM wants to modify the time, you get a corrupted BIOS after reboot. I've found DSM doesn't like the BIOS from Supermicro but is ok with ASUS. With ASUS BIOS, I can set the shutdown time but setting a wake up time corrupts the BIOS. The best compatibility I've found so far is from Intel motherboards, specifically the DQ35xxx motherboards. I am able to schedule a wake up time with the Intel motherboards. DSM probably also doesn't like UEFI.

Hey guys, I am all new to XPEnology so forgive me if something has been explained already (while i did read a lot of threads there is not *the* beginners thread yet (or i didnt find it)). So i am looking to replace my aging DS-508 and looked at quite a lot of options -Build a ZFS based server with an i3 (ECC) or E3-1200v3 (for VT-D) or E5-1600 (for RDIMMS, >32GB) (Doable but likely high power req and definitely overkill) -Buy a new DS-1813+ (Good, but i am not willing to shell out 800+bucks for *that* old hardware) -Use XPEnology withe something between old low power Atom and (relatively) high Power E3-1200v3 -> Enter Avoton/Rangely. So with the recent availability of the new Atoms i suppose that would be a good compromise - ServertheHome showed max power usage (load) at 30ish Watts (idle usage for an E3 solution) (+ drives o/c) so i am still at the same level as an 1813+ for way better performance. So the question is - is Avoton (or Rangeley) already supported by XPenology?. As the only available board atm is the supermicro one i would use that (http://www.supermicro.com/products/motherboard/Atom/X10/A1SRi-2758F.cfm, this is the Rangeley variant which is Avoton+ some extra stuff for network devices and costs about the same here. So will this work out of the box ? Or am I looking at being a Guinea Pig;) (no dont have it ordered yet:p) I assuem there needs to be the following: Basic Chipset support (?) SATA Drivers (?) Network (Marvell Alaska 88E1543) Now that particular boards has an additional feature - "1x SATA DOM power connector" I read in some thread that its currently not possible to install DSM on a local disk since they all get initialized with the raid layout and the DOM which where on Synology devices was missing - could this be a solution to this problem ? There are different sized DOM's available on Ebay so given driver support it should be easy to use it ... Edit: This is only a power connector And primary difference Avoton -> Rangely: Intel QuickAssist Technology -> Encryption support - does anyone know whether that is usefull at all? I assume that AES-NI will be possible to run providing better performance for encrypted folders (which is horribly slow apparently even on those high end Syn' stations)? If all else fails i probably could run it with ESX but with missing VT-D to pass on a SAS controller i guess i would be running it natively if its supported;) Thanks, Thomas

I'm having issues booting usin a Supermicro X10SLQ-O motherboard with a XEON E1230V3, the board has the i217 and i210 for NICs and I also have an IBM M1015 IT mode. The system will boot and freeze, no kernel panic or anything like that. any ideas what could be wrong, thanks

Hi, I´m right now planning to switch from a synology DS213+ to a self build NAS based on a Supermicro X9SBAA-F. This board does have 2 Intel i350-AM2 network chips. I didn´t find if they are already supported by xpenology? If no is there any chance to get the drivers included? Best regards, F.

Looks like this is an issue with the LSI Controller: http://www.supermicro.com/support/faqs/ ... ?faq=13209

Trantor, I just ordered a 24bay Supermicro system from eBay. http://www.ebay.com/itm/171078773991?ss ... 1497.l2649 http://www.supermicro.com/aplus/motherb ... 8dme-2.cfm The Supermicro H8DME-2 motherboard in this system contains the following. - nVidia MCP55 Pro SATA2 3.0Gbps Controller - nVidia MCP55 Pro Chipset Dual-port LAN / Ethernet Controller Additionally, it also comes with 3x Supermicro AOC-SAT2-MV8 SATA cards (Marvell Hercules-2 Rev. C0 SATA host controller) http://www.supermicro.com/products/acce ... t2-mv8.cfm 1) Does the current release contain the SATA and Ethernet drivers for the nVidia MCP55Pro? 2) Does it contain the driver to support Marvell Hercules host controller? Thanks. I'll be testing it out once I get the hardware. I'm just curious about the compatibility prior to receive the hardware.

Is there any documentation to explain how to add LSI SAS drivers to this build? Or perhaps maybe someone could include them in the next build? LSI SAS2008 specifically in my case. When I try to pass through my LSI SAS card via VT-d I get an error on boot and it hangs. As soon as I remove the passthrough it boots up fine. I'd rather not use RDM as I like having SMART features. UPDATE: I also tried my other SAS card -- Supermicro AOC-SASLP-MV8 (Marvell 6480 chipset) via VT-D and it didn't detect any drives at all. Support for either card would be dandy. If I have to compile it myself I will.

I've got a SuperMicro Superserver with a 1230v2, 32gb RAM, LSI SAS 2308 in IT Mode and 8x Hitachi 5K3000's, ATP USB SLC SSD for ESXi. Xpenology does run natively on this box, but this machine is overkill. I want to virtualise everything with ESXi 5.1 I have SSD's on hardware RAID for datastore, but can't really find a nice elegant solution for Xpenology for my storage array, I have managed to make a VDI from the IMG, but not sure how to make a proper VMDK for ESXi. I do hope more work continues for this as 4.2 would be amazing as a VM with VT-d passthrough SAS controller