gnoboot Posted February 8, 2014 Author Share #101 Posted February 8, 2014 I'm currently preparing my upcoming release, so far I broke iSCSI again with the following drivers and features added (w/o my iSCSI fix). Add all PATA/SATA/SCSI and Network (1G - 10G) drivers supported by popular Linux distributions Infiniband - Qlogic, Chelsio, Mellanox Set maximum CPU supported to 4K Virtual I/O HyperV drivers Alpha5 is coming soon, maximum CPU supported will not be included as breaks iSCSI . But more drivers were added in this release, check my blog to see the complete list;). Don't forget to click ads to support my development and I'm also accepting donations . I think it is better if you can add the drive for hp n36l/n54l.NIC is NC107I.thanks a lot. Could you post the `lspci -v`result? I am using HP N54L too, I can post it for your reference... thanks. 00:00.0 Class 0600: Device 1022:9601 Subsystem: Device 103c:1609 Flags: bus master, 66MHz, medium devsel, latency 0 Capabilities: [c4] HyperTransport: Slave or Primary Interface Capabilities: [54] HyperTransport: UnitID Clumping Capabilities: [40] HyperTransport: Retry Mode Capabilities: [9c] HyperTransport: #1a Capabilities: [f8] HyperTransport: #1c 00:01.0 Class 0604: Device 103c:9602 Flags: bus master, 66MHz, medium devsel, latency 64 Bus: primary=00, secondary=01, subordinate=01, sec-latency=64 I/O behind bridge: 0000e000-0000efff Memory behind bridge: fe700000-fe8fffff Prefetchable memory behind bridge: 00000000f0000000-00000000f7ffffff Capabilities: [44] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [b0] Subsystem: Device 103c:1609 00:06.0 Class 0604: Device 1022:9606 Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 Memory behind bridge: fe900000-fe9fffff Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot-), MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [b0] Subsystem: Device 103c:1609 Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [110] Virtual Channel Kernel driver in use: pcieport 00:11.0 Class 0106: Device 1002:4391 (rev 40) (prog-if 01) Subsystem: Device 103c:1609 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 41 I/O ports at d000 [size=1] I/O ports at c000 [size=1] I/O ports at b000 [size=1] I/O ports at a000 [size=1] I/O ports at 9000 [size=1] Memory at fe6ffc00 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] MSI: Enable+ Count=1/8 Maskable- 64bit+ Capabilities: [70] SATA HBA v1.0 Capabilities: [a4] PCI Advanced Features Kernel driver in use: ahci 00:12.0 Class 0c03: Device 1002:4397 (prog-if 10) Subsystem: Device 103c:1609 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 18 Memory at fe6fe000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci_hcd 00:12.2 Class 0c03: Device 1002:4396 (prog-if 20) Subsystem: Device 103c:1609 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 17 Memory at fe6ff800 (32-bit, non-prefetchable) [size=11] Capabilities: [c0] Power Management version 2 Capabilities: [e4] Debug port: BAR=1 offset=00e0 Kernel driver in use: ehci_hcd 00:13.0 Class 0c03: Device 1002:4397 (prog-if 10) Subsystem: Device 103c:1609 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 18 Memory at fe6fd000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci_hcd 00:13.2 Class 0c03: Device 1002:4396 (prog-if 20) Subsystem: Device 103c:1609 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 17 Memory at fe6ff400 (32-bit, non-prefetchable) [size=11] Capabilities: [c0] Power Management version 2 Capabilities: [e4] Debug port: BAR=1 offset=00e0 Kernel driver in use: ehci_hcd 00:14.0 Class 0c05: Device 1002:4385 (rev 42) Flags: 66MHz, medium devsel 00:14.3 Class 0601: Device 1002:439d (rev 40) Subsystem: Device 103c:1609 Flags: bus master, 66MHz, medium devsel, latency 0 00:14.4 Class 0604: Device 1002:4384 (rev 40) (prog-if 01) Flags: bus master, 66MHz, medium devsel, latency 64 Bus: primary=00, secondary=03, subordinate=03, sec-latency=64 00:16.0 Class 0c03: Device 1002:4397 (prog-if 10) Subsystem: Device 103c:1609 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 18 Memory at fe6fc000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci_hcd 00:16.2 Class 0c03: Device 1002:4396 (prog-if 20) Subsystem: Device 103c:1609 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 17 Memory at fe6ff000 (32-bit, non-prefetchable) [size=11] Capabilities: [c0] Power Management version 2 Capabilities: [e4] Debug port: BAR=1 offset=00e0 Kernel driver in use: ehci_hcd 00:18.0 Class 0600: Device 1022:1200 Flags: fast devsel Capabilities: [80] HyperTransport: Host or Secondary Interface 00:18.1 Class 0600: Device 1022:1201 Flags: fast devsel 00:18.2 Class 0600: Device 1022:1202 Flags: fast devsel 00:18.3 Class 0600: Device 1022:1203 Flags: fast devsel Capabilities: [f0] Secure device <?> Kernel driver in use: k10temp 00:18.4 Class 0600: Device 1022:1204 Flags: fast devsel 01:05.0 Class 0300: Device 1002:9712 Subsystem: Device 103c:1609 Flags: bus master, fast devsel, latency 0, IRQ 10 Memory at f0000000 (32-bit, prefetchable) [size=128M] I/O ports at e000 [size=11] Memory at fe8f0000 (32-bit, non-prefetchable) [size=64K] Memory at fe700000 (32-bit, non-prefetchable) [size=1M] Expansion ROM at [disabled] Capabilities: [50] Power Management version 3 Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ 02:00.0 Class 0200: Device 14e4:165b (rev 10) Subsystem: Device 103c:705d Flags: bus master, fast devsel, latency 0, IRQ 42 Memory at fe9f0000 (64-bit, non-prefetchable) [size=64K] Capabilities: [48] Power Management version 3 Capabilities: [40] Vital Product Data Capabilities: [60] Vendor Specific Information: Len=6c <?> Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [cc] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Virtual Channel Capabilities: [160] Device Serial Number xx-xx-xx-xx-xx-xx-xx-xx Capabilities: [16c] Power Budgeting <?> Kernel driver in use: tg3 Fixed, need testers... Quote Link to comment Share on other sites More sharing options...
revaiz Posted February 8, 2014 Share #102 Posted February 8, 2014 Thanks a lot!! I would like to download the gnoboot-alpha5, but the file type is .RSDF? Quote Link to comment Share on other sites More sharing options...
gnoboot Posted February 8, 2014 Author Share #103 Posted February 8, 2014 Thanks a lot!! I would like to download the gnoboot-alpha5, but the file type is .RSDF? Just use jdownloader to get the image or google for decrypt RSDF. Enjoy and report any issues . Quote Link to comment Share on other sites More sharing options...
revaiz Posted February 8, 2014 Share #104 Posted February 8, 2014 Thanks a lot!! I would like to download the gnoboot-alpha5, but the file type is .RSDF? Just use jdownloader to get the image or google for decrypt RSDF. Enjoy and report any issues . Thanks!! I can boot it on my N54L!! Quote Link to comment Share on other sites More sharing options...
goddamnit Posted February 8, 2014 Share #105 Posted February 8, 2014 I tried this with virtual box ,it cannot install any PAT ,with stock or patched one . But ,after install DSM in VMWare ,it work fine in virtual box . Hope this help Quote Link to comment Share on other sites More sharing options...
gnoboot Posted February 8, 2014 Author Share #106 Posted February 8, 2014 Upgrade guide from 4.x to 5.x posted on page 1. I tried this with virtual box ,it cannot install any PAT ,with stock or patched one .But ,after install DSM in VMWare ,it work fine in virtual box . Hope this help Post your `lspci -v` or boot to debug mode and enable serial logging if supported by virtualbox, send me the results. Thanks! Quote Link to comment Share on other sites More sharing options...
Diverge Posted February 8, 2014 Share #107 Posted February 8, 2014 Upgrade guide from 4.x to 5.x posted on page 1. Could you explain your guide in more detail? I don't follow under what system you're mounting images, and for what reasons. On another note, I just played with latest gnoboot and upgraded an array from DSM 4.3 to DSM 5 while retaining all data. My tests consisted of: Create a brand new VM with DSM 4.3 options in gnboot. Created a virtual 3 disk array. Installed unmodded DSM_DS3612xs_3810.pat. Setup DSM 4.3 and copied some test data to the new array. Shutdown the DSM 4.3 VM.Move the array to another VM setup for DSM 5 options in gnoboot. Upon starting the DSM 5 VM you're greeted with a web wizard to migrate your array to new DSM version. Picked option to retain all my data and settings, chose new unmodded DSM_DS3612xs_4418.pat, installed. And booted up to upgraded DSM The only thing you have to redo is setting permissions on shared folders. Quote Link to comment Share on other sites More sharing options...
goddamnit Posted February 8, 2014 Share #108 Posted February 8, 2014 Upgrade guide from 4.x to 5.x posted on page 1. I tried this with virtual box ,it cannot install any PAT ,with stock or patched one .But ,after install DSM in VMWare ,it work fine in virtual box . Hope this help Post your `lspci -v` or boot to debug mode and enable serial logging if supported by virtualbox, send me the results. Thanks! I find out the problem and it work fine now . Becoz someone set the vbox vm to 128Mb so it fail to install lol ... Quote Link to comment Share on other sites More sharing options...
stilldre79 Posted February 9, 2014 Share #109 Posted February 9, 2014 Is there anyway possible for you to also get the Temperature and Smart Status working for ESXi once you get the shutdown problem fixed, this would ultimately make my ESXi setup complete for my N54L Quote Link to comment Share on other sites More sharing options...
newsony1 Posted February 9, 2014 Share #110 Posted February 9, 2014 Will, I test alpha5 image, but still can't boot from my MB. The MB's BIOS is Phoenix, MB is N70E-DR V2. Thanks. Quote Link to comment Share on other sites More sharing options...
goddamnit Posted February 9, 2014 Share #111 Posted February 9, 2014 Is there anyway possible for you to also get the Temperature and Smart Status working for ESXi once you get the shutdown problem fixed, this would ultimately make my ESXi setup complete for my N54L This is the problem of ESXI/VBOX/VMWARE that cannot report the real temp/smart but not related to sth like kernel But I hope someone can solve this ,too Quote Link to comment Share on other sites More sharing options...
Diverge Posted February 9, 2014 Share #112 Posted February 9, 2014 (edited) @gnoboot, Should I be able to passthrough my Intel Panther Point ACHI controller to gnoboot? I'm getting pagefault errors: My ESXI install and datastore are on PCIe Sata controller, and I want to try to passthrough motherboards onboard controller so I can use Direct I/O, rather than RDM mappings to my disks. Is this possible, or do I need to give up? edit: here's serial debug out: http://pastebin.com/1KMGU6St edit2: same happens when I add the passed through controller to a linux live CD... So I guess it's not related to gnoboot... Anyone have any experience with passthrough? Edited February 9, 2014 by Guest Quote Link to comment Share on other sites More sharing options...
EmmTeh Posted February 9, 2014 Share #113 Posted February 9, 2014 How do we install the RS3614xs+ codebase? I see you mentioned that you tested it in your OP. I've tried editing the v5 grub entry and changing DS3612xs to RS3614xs+ but it didn't work. Quote Link to comment Share on other sites More sharing options...
gnoboot Posted February 9, 2014 Author Share #114 Posted February 9, 2014 @Diverge Are you using esxi 5.1 or 5.5? LInux kernel version that you tested? @EmmTeh Why do you want to use RS3614xs+? Edit: @gnoboot, Should I be able to passthrough my Intel Panther Point ACHI controller to gnoboot? I'm getting pagefault errors: Known kernel issue with ASM1083/1085 - https://lkml.org/lkml/2012/1/30/216 Quote Link to comment Share on other sites More sharing options...
Diverge Posted February 9, 2014 Share #115 Posted February 9, 2014 @DivergeAre you using esxi 5.1 or 5.5? LInux kernel version that you tested? I'm using esxi 5.5. Not sure the linux kernel offhand, tried gnoboot dsm5 and a Parted Magic Live CD. System is offline atm so can't check right now. will edit post when I get the info. edit: Known kernel issue with ASM1083/1085 - https://lkml.org/lkml/2012/1/30/216 That matters even if ASM 1081 PCIe SATA controller isn't being passthrough? It's my esxi boot device. When I don't try to passthrough the Panther Point AHCI controller everything works fine with the ASM 1061 controller as esxi boot and datastore. Quote Link to comment Share on other sites More sharing options...
EmmTeh Posted February 9, 2014 Share #116 Posted February 9, 2014 @Diverge@EmmTeh Why do you want to use RS3614xs+? 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 Quote Link to comment Share on other sites More sharing options...
gnoboot Posted February 9, 2014 Author Share #117 Posted February 9, 2014 (edited) @Diverge@EmmTeh Why do you want to use RS3614xs+? 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? That matters even if ASM 1081 PCIe SATA controller isn't being passthrough? It's my esxi boot device. When I don't try to passthrough the Panther Point AHCI controller everything works fine with the ASM 1061 controller as esxi boot and datastore. 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. Edited February 9, 2014 by Guest Quote Link to comment Share on other sites More sharing options...
EmmTeh Posted February 9, 2014 Share #118 Posted February 9, 2014 Have you tried this guide - viewtopic.php?f=2&t=2028? Yessir! I have the optimal settings but I always end up with a crashed volume on reboot. It doesn't happen right away... but always within a few days. Quote Link to comment Share on other sites More sharing options...
Diverge Posted February 9, 2014 Share #119 Posted February 9, 2014 Edit: @Diverge, found a possible patch. Nice! I downloaded the latest ubuntu, and will test that out in a little bit. I want to put back my original boot SSD and make sure I didn't mess up my array first, since when I redid my RDM mappings on new boot disk, and booted gnoboot 5 with my array attached (it's dsm 4.2), it said configuration lost instead of migration at DSM web page edit: my array is still there, and old setup still working. back to testing edit2: I moved my array and some VM's to a new disk/datastore and moved the 4.2 array (RDMs) to gnoboot w/ DSM 5. All data intact, had to reinstall and setup all my synology apps though. so far so good. Playing with my real data Quote Link to comment Share on other sites More sharing options...
gnoboot Posted February 10, 2014 Author Share #120 Posted February 10, 2014 Did you update DSM 5 to update 1 first before moving your array? Quote Link to comment Share on other sites More sharing options...
Diverge Posted February 10, 2014 Share #121 Posted February 10, 2014 Did you update DSM 5 to update 1 first before moving your array? nope, I just moved disks from DSM 4.2 system to one new system with gnoboot DSM 5. Setup with DSM_DS3612xs_4418.pat, then did update 1 by downloading update in DSM, then console to: sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info > /autoupd@te.info1 mv /autoupd@te.info1 /autoupd@te.info Then hit update button. This method works great (for small update). I've done it like 3-4 times aready. Too bad it can't be done automatically somehow. edit: original post is here viewtopic.php?f=2&t=2049 Quote Link to comment Share on other sites More sharing options...
sjtuross Posted February 10, 2014 Share #122 Posted February 10, 2014 Any idea to get vmtools working? Tried steps here http://xpenology.com/forum/viewtopic.php?f=2&t=558&start=280#p9968, but it seems the vmtools cannot run. Any plan to integrate vmtools in the gnoBoot? Thanks for your great work! Quote Link to comment Share on other sites More sharing options...
Diverge Posted February 10, 2014 Share #123 Posted February 10, 2014 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 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). Quote Link to comment Share on other sites More sharing options...
EmmTeh Posted February 11, 2014 Share #124 Posted February 11, 2014 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). I couldn't get gnoboot to recognize any disks on those cards yesterday (tried 3). The SAT2-MV8 works (PCI-X) Quote Link to comment Share on other sites More sharing options...
gnoboot Posted February 11, 2014 Author Share #125 Posted February 11, 2014 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). I couldn't get gnoboot to recognize any disks on those cards yesterday (tried 3). The SAT2-MV8 works (PCI-X) 88SE6480 - is not supported, it will only work with Linux kernel 2.6.x if you compile the driver from the vendor. Any idea to get vmtools working? Tried steps here http://xpenology.com/forum/viewtopic.php?f=2&t=558&start=280#p9968, but it seems the vmtools cannot run. Any plan to integrate vmtools in the gnoBoot? Thanks for your great work! I'm currently working on it. EDIT: I will release open-vm-tools spk later, please visit my blog and click the ADs . Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.