Diverge

If you want to use the first 2 slots you'll need to edit the nanoboot config like I said previously in this thread.

Check what version you have. You're probably still on previous update, since the sed commands trick the updater into going through with the update.

This is your problem. You need to unload the PATA/IDE driver in the nanoboot config, it it will keep reserving those 2 slots. If using nanoboot, you need to edit syslinux.cfg. Here's an example from my config: LABEL Synology DSM 5.0 MENU LABEL Synology DSM 5.0 kernel /zImage rmmod=ata_piix ihd_num=0 netif_num=4 syno_hw_version=DS3612xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 the part I am referring to is; rmmod=ata_piix. That unloads the driver, or my slots would be like yours, first 2 reserved. Change all the menu options in the config to reflect the change.

Why would he create it for a DS415+, which is limited to 4 bays, when it's currently one of the highest end models? edit: fixed typo, bays not days lol

Here's mine: https://lh6.googleusercontent.com/-6gjR ... 201718.jpg https://lh4.googleusercontent.com/-y4Cc ... 201727.jpg https://lh4.googleusercontent.com/-2uOj ... 201745.jpg https://lh4.googleusercontent.com/-avg_ ... 201757.jpg https://lh6.googleusercontent.com/-eiz8 ... 201946.jpg Warning, they are high resolution I haven't gotten around to making it better yet. Planned to make aluminum and plexi panels/sides, and customize the heatsink to make the case shorter. So the hardrive rack fan is flush with the motherboard I/O panel. Anyone know where to get heat pipes from in the US, relatively cheap? I need to bend my own to make my heatsink the orientation I need to make the case shorter.

I just noticed there is an update 5, anyone try it?

I just finally got around to updating mine and had the same exact warning on my first boot.. rebooting now... i hope my volume comes back. worst case I'd need to redo everything from a backup. For a few minutes I thought they were gone on 2nd reboot, but it seems it hung on the reboot and was still stuck in previous state. had to force a reboot from esxi VM console and saw my volume soon as it booted.. hope it stays that way

I don't see how you'd make this work. DSM needs it's own volume, which it creates. Flexraid is just parity on top of a filesystem. They are like polar opposites in how they work. Combining them somehow removes the point of flexraid.

Do whatever you're comfortable with. No one knows the right answer. Even if it was a real synology box the same stuff could happen, and you still have the same unknowns. If it was me, i'd redo it for peace of mind, 1TB isn't much.

ALL HOPE WAS NOT LOST!!! HUGE SUCCESS!!! Thanks to your post on cgsecurity and https://raid.wiki.kernel.org/index.php/RAID_Recovery, I managed to regain access to my files. I just subscribed to a 1 year subscription of CrashPlan as it's on promotion. I also bought a 4TB Seagate for local backup. I don't want such a tragedy to happen again. I spent the last week of my life frantically trying to recover my files and I cry myself to sleep every night (just kidding) as I would have lost my entire anime/music/movie/personal photo collection. Thanks everyone once again for all your help. I'm glad it helped! I know your pain, I had done the same with my movie, software collection Took me a long time and lots of reading to try to learn about linux software raid, and how it works, and I'm still kinda a noob. If it wasn't for the guy named Remy, I'd have been clueless on where to start.

I don't think that error message has anything to do with your array problem. A typical synology system with a one volume array consists of: md0 (dsm), md1 (swap), and md2 (volume1). That message is in regard to md0 (DSM), and it says if for everyone using nanoboot (i think his bootloader is in non-standard format), but that has nothing to do with your problem. Best best to see if your array works in a Linux OS. http://www.synology.com/en-global/support/faq/579 if it does, backup your data and then start over and copy if back once you get DSM back up.

I had a similar problem happen to me when expanding arrays a while back. My data was accessible, but DSM thought it was crashed. After enough playing I eventually fixed it, but in the end I just backed up all my data and started over. my similar issue: viewtopic.php?f=2&t=2529 A good page for the understanings of linux software raid: https://wiki.archlinux.org/index.php/So ... ID_and_LVM And one of my older experiences where my partition tables got erased while adding a disk. I was eventually able to assemble the array w/o partition tables with a lot of help from a guy named Remy: http://forum.cgsecurity.org/phpBB3/foun ... t2600.html As I said before, if you can access your data you should just back it up and start over. Either way you should back it up, this way if you want to play around and pull your hair out trying to fix it you have a fall back. Good luck

Upstairs PC and downstairs PC, duh

I've never tested the transfer speeds under esxi vs non-virtualized, but I know with a windows esxi VM you can choose between 2 different virtual nics (e1000, and VMX3NET). For my windows VM I had to change to VMX3NET or the VM wasn't able to send out multicast/broadcast packets needed for WMC and extenders. Who knows if there is a difference in transfer speeds between the 2, but I figured it would be worth mentioning.

It is headless, but it has a client program (as seen in my screen capture) that is used to manage the VM's. From that program you also have remote desktop like control over VM's. And since I am only using the windows VM for WMC, I rarely have need to use the windows desktop, but when I do I just use vSphere client. I use WMC extenders to access WMC. I've had no problems with my esxi sever, but it is different than yours. Mine is an Intel based system, and all components have VTd support (direct IO). MY LSI raid card is not used by esxi, it is passed through to my DSM VM in IT mode. The array is at DSM level, not by the LSI card. Motherboard - Intel DQ77KB CPU - Intel i7 3770T RAM - 16GB OS - ESXI 5.5 on 60GB mSATA SSD Storage - LSI 9201-8i w/ 4 x 3TB WD Red (DSM SHR volume) and 1x4TB (eSATA for backups). VM1 - Synology DSM 5 - 4493 w/ LSI card passed through. VM2 - Windows 8.1 w/WMC set to 500GB iSCSI target of Synology VM for WMC recording. I haven't gotten around to finishing my case for it, but here's its current state http://goo.gl/N1Qs9m edit: the motherboard used in those pics was the DH61AG, which I used for testing prior to swapping over my other motherboard.

my esxi 5.5 server runs off an mini ITX motherboard w/ i7 3770T (that would be wasted just for DSM). It also runs a VM with Windows 8.1 for Windows Media Center (to watch live TV with a cablecard via WMC extenders like xbox 360). It records to an iSCSI LUN from my DSM VM. I also have a Linux VM for when I need to play around with linux. It's also a lot easier to manage once you have it setup. It also makes it a lot easier to test various things, like new releases of DSM, or DSM boot images such as gnoboot/nanoboot. Why play with real data when you can quickly make a test VM?

That's strange. No difference here with IDE, same need to replace the .vmdk after 1st install. 5.5u1 also. So at least some fiddling seems necessary. Either replace .vmdk or "rmmod=at a_piix", of which I don't have an idea what it means. In case someone wants to try my all-SCSI solution, here is an .ova: http://tinyurl.com/pros2tr Just add an VMXNET3 nic and it's ready to go. (admin, no pw, dhcp, vmware tools installed). Like I said, once it's installed just replace the (small) .vmdk with a newer version of StarWind-V2V-ESXi-converted Nanoboot if available. It should read rmmod=ata_piix, typed it from my phone and it autocorrected. Anyway, that has to be added to the boot config of either grub, or syslinux. In order to do it, the img or vdmk must be mounted, then you'll see the boot files and config files. example; at D:\boot\syslinux\syslinux.cfg you'll see the following: PROMPT 0 TIMEOUT 50 DEFAULT /boot/syslinux/vesamenu.c32 MENU WIDTH 0 MENU MARGIN 5 MENU RESOLUTION 800 600 MENU BACKGROUND /boot/syslinux/synology.png MENU TITLE NanoBoot Produced by Sancome menu color border 1;30;44 #FF000000 #00000000 none menu color title 1;36;44 #FF000000 #00000000 none menu color sel 1;30;37 #FFFFFF00 #00000000 none menu color unsel 1;37;44 #FF000000 #00000000 none menu color timeout 1;37;40 #FFFFFF00 #00000000 none LABEL Synology DSM 5.0 MENU LABEL Synology DSM 5.0 kernel /zImage ihd_num=0 netif_num=4 syno_hw_version=DS3612xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 MENU SEPARATOR LABEL Synology DSM 5.0 (Debug) MENU LABEL Synology DSM 5.0 (Debug) kernel /zImage ihd_num=0 netif_num=4 syno_hw_version=DS3612xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=7 vga=0x305 debug MENU SEPARATOR MENU BEGIN MENU LABEL Synology DSM 5.0 (Upgrade/Degrade) LABEL Synology DSM 5.0-4482 MENU LABEL Synology DSM 5.0-4482 kernel /zImage ihd_num=0 netif_num=4 syno_hw_version=DS3612xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 upgrade=5.0-4482 MENU SEPARATOR LABEL Synology DSM 5.0-4458 MENU LABEL Synology DSM 5.0-4458 kernel /zImage ihd_num=0 netif_num=4 syno_hw_version=DS3612xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 upgrade=5.0-4458 MENU SEPARATOR LABEL Synology DSM 5.0-4418 MENU LABEL Synology DSM 5.0-4418 kernel /zImage ihd_num=0 netif_num=4 syno_hw_version=DS3612xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 upgrade=5.0-4418 MENU SEPARATOR LABEL Main Menu MENU LABEL Main Menu MENU GOTO .top MENU END MENU SEPARATOR LABEL Reboot MENU LABEL Reboot kernel /boot/syslinux/reboot.c32 MENU SEPARATOR LABEL Shutdown MENU LABEL Shutdown kernel /boot/syslinux/poweroff.com just add rmmod=ata_piix to the kernel /zImage lines. And it will prevent the IDE controller from loading, then DSM won't see your boot drive (if it's IDE).

Not so here. I'm using the ESX variant with SCSI controllers (e.g., VMware Paravirtual) as device 0:0. Works like a charm. That's right, but that happens only on the very first (completely fresh) install of DSM. Just power off the VM, replace Nanoboot .vmdk and boot normal. Everything works. After that one can just replace the Nanoboot .vmdk with a new version if available. DSM continues to work as before. At least my experience here. Did this the last couple of updates. The first time I did that I found it irritating that I had to replace the Nanoboot .vmdk. So instead of using SCSI I used the IDE pre-allocated .vmdk. Everything went ok. No more replacing. I'm using ESXi 5.5 update 1. So bottom line, both options should work. What I don't like about the gnoboot or nanoboot is that they use different boot menu's and menu option descriptions. It isn't clear to me what 'gnoboot.me' is or 'alpha'. So I did some editing and created the same boot menu's for both versions with the same layout and description. It's also easier for new persons to understand. Maybe a tip for upcoming releases to have a better description in the menu's? That happens because DSM is seeing your boot drive. If you use ide for your vdmk boot drive you can rmmod=at a_piix so that drive won't be detected.

Trying to install nanoboot in ESXi 5.5 the whole weekend . The .vmdk or .iso are been overwritten after install dsm. VM can't reboot. VM will not start. It works fine with gnoboot 4458. Wil try again with some modding to the img file. If you're booting a CD/DVD iso in ESXI, then your problem is most likely the ESXI bios. You can change the boot order to CD/DVD first, but it will keep reverting back to it's default state after a successful boot (following one will try to boot hard drive first - likely one of your array drives).

yeah, I don't think it's fully functional just yet.

It works fine in both gnoboot and nanoboot. Not sure why you're having issues.

nope, you'd need to ask sancome. Or ask gnoboot what he changed from 10.4 to 10.5 to break it (but it seems he's MIA). edit: basically when fixed, it doesn't do that unload/reload of driver, reset of card, and re-init of the drives (only initializes them once).

Maybe a newer version will solve this ? (latest is v18) There's actually a newer version (v19). I'm not sure why newer ones aren't used, but it was fixed using same old one (13.1).

Yeah, I found someone else that had the same issue with gnoboot. gnoboot 10.4 works fine for me. I suspect 10.5 has this bug. Nanoboot was able to fix it, so expect a release with it working soon (my guess).

Any experts out there know why this would be happening? [ 0.946148] mpt2sas version 13.100.00.00 loaded [ 0.946272] scsi0 : Fusion MPT SAS Host [ 0.947094] mpt2sas 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [ 0.947167] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (6118604 kB) [ 0.947583] mpt2sas 0000:03:00.0: irq 72 for MSI/MSI-X [ 0.947806] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 72 [ 0.947808] mpt2sas0: iomem(0x00000000fd4fc000), mapped(0xffffc900080f0000), size(16384) [ 0.947810] mpt2sas0: ioport(0x0000000000004000), size(256) [ 1.072962] mpt2sas0: Allocated physical memory: size(7418 kB) [ 1.072964] mpt2sas0: Current Controller Queue Depth(3307), Max Controller Queue Depth(3432) [ 1.072965] mpt2sas0: Scatter Gather Elements per IO(128) [ 1.132059] mpt2sas0: LSISAS2008: FWVersion(18.00.00.00), ChipRevision(0x03), BiosVersion(07.35.00.00) [ 1.132062] mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ) [ 1.132138] mpt2sas0: sending port enable !! [ 1.136060] mpt2sas0: host_add: handle(0x0001), sas_addr(0x500605b004f0ff80), phys(8) [ 1.143506] mpt2sas0: port enable: SUCCESS [ 1.145393] scsi 0:0:0:0: Direct-Access WDC WD30EFRX-68EUZN0 0A80 PQ: 0 ANSI: 6 [ 1.145397] scsi 0:0:0:0: SATA: handle(0x000c), sas_addr(0x4433221103000000), phy(3), device_name(0x50014ee003bb2b5f) [ 1.145399] scsi 0:0:0:0: SATA: enclosure_logical_id(0x500605b004f0ff80), slot(0) [ 1.145493] scsi 0:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) [ 1.145496] scsi 0:0:0:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1) [ 1.145605] syno_disk_type_get: disk driver 'Fusion MPT SAS Host' [ 1.145607] syno_disk_type_get: Got UNKNOWN port type 3 [ 1.145611] sd_probe: Got UNKNOWN disk sda with index 0 [ 1.146047] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 1.146145] sd 0:0:0:0: [sda] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) [ 1.146147] sd 0:0:0:0: [sda] 4096-byte physical blocks --------------------------------------------------------------------- [ 1.619124] mpt2sas version 13.100.00.00 unloading [ 1.620886] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 1.620908] sd 0:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00 [ 1.623997] mpt2sas0: removing handle(0x000c), sas_addr(0x4433221103000000) [ 1.628784] sd 0:0:1:0: [sdb] Synchronizing SCSI cache [ 1.628803] sd 0:0:1:0: [sdb] Result: hostbyte=0x01 driverbyte=0x00 [ 1.632105] mpt2sas0: removing handle(0x0009), sas_addr(0x4433221100000000) [ 1.637083] sd 0:0:2:0: [sdc] Synchronizing SCSI cache [ 1.637101] sd 0:0:2:0: [sdc] Result: hostbyte=0x01 driverbyte=0x00 [ 1.639341] mpt2sas0: removing handle(0x000b), sas_addr(0x4433221101000000) [ 1.644550] sd 0:0:3:0: [sdd] Synchronizing SCSI cache [ 1.644568] sd 0:0:3:0: [sdd] Result: hostbyte=0x01 driverbyte=0x00 [ 1.647608] mpt2sas0: removing handle(0x000a), sas_addr(0x4433221102000000) [ 1.651126] mpt2sas0: sending message unit reset !! [ 1.652819] mpt2sas0: message unit reset: SUCCESS [ 1.653146] mpt2sas 0000:03:00.0: PCI INT A disabled --------------------------------------------------------------------- [ 1.806736] mpt2sas version 13.100.00.00 loaded [ 1.806840] scsi1 : Fusion MPT SAS Host [ 1.807685] mpt2sas 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [ 1.807755] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (6118604 kB) [ 1.808185] mpt2sas 0000:03:00.0: irq 72 for MSI/MSI-X [ 1.808368] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 72 [ 1.808370] mpt2sas0: iomem(0x00000000fd4fc000), mapped(0xffffc90008090000), size(16384) [ 1.808371] mpt2sas0: ioport(0x0000000000004000), size(256) [ 1.923993] mpt2sas0: Allocated physical memory: size(7418 kB) [ 1.923995] mpt2sas0: Current Controller Queue Depth(3307), Max Controller Queue Depth(3432) [ 1.923996] mpt2sas0: Scatter Gather Elements per IO(128) [ 1.982958] mpt2sas0: LSISAS2008: FWVersion(18.00.00.00), ChipRevision(0x03), BiosVersion(07.35.00.00) [ 1.982961] mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ) [ 1.983037] mpt2sas0: sending port enable !! [ 1.986919] mpt2sas0: host_add: handle(0x0001), sas_addr(0x500605b004f0ff80), phys(8) [ 1.993404] mpt2sas0: port enable: SUCCESS [ 1.995399] scsi 1:0:0:0: Direct-Access WDC WD30EFRX-68EUZN0 0A80 PQ: 0 ANSI: 6 [ 1.995403] scsi 1:0:0:0: SATA: handle(0x000c), sas_addr(0x4433221103000000), phy(3), device_name(0x50014ee003bb2b5f) [ 1.995405] scsi 1:0:0:0: SATA: enclosure_logical_id(0x500605b004f0ff80), slot(0) [ 1.995523] scsi 1:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) [ 1.995528] scsi 1:0:0:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1) [ 1.995698] syno_disk_type_get: disk driver 'Fusion MPT SAS Host' [ 1.995700] syno_disk_type_get: Got UNKNOWN port type 3 [ 1.995703] sd_probe: Got UNKNOWN disk sdb with index 1 [ 1.996024] sd 1:0:0:0: Attached scsi generic sg0 type 0 [ 1.996213] sd 1:0:0:0: [sdb] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) [ 1.996215] sd 1:0:0:0: [sdb] 4096-byte physical blocks basically on boot, mpt2sas loads, finds all drives on scsi0, sets them up as sda, sdb, sdc, sdd. Then further into boot, it unloads/reloads driver, resets the card, finds all the drives on scsi1 (not 0 this time), and sets them up starting at sdb, instead of sda. I'm testing LSI controller support for nanoboot. So any help from experts would be appreciated