gnoboot

XPEnology gnoBoot

Recommended Posts

Add the following code in your /etc/rc.local.

 

touch /etc/rc.local
chmod 755 /etc/rc.local
echo "rmmod ata_piix" > /etc/rc.local

 

Thanks. Maybe I should have done that prior to adding my array, because the change has no effect on how the disks fill the slots now.

 

I double checked

lsmod | grep ata_piix

after rebooting, and it's not loaded.

 

edit: I just removed array from VM and rebooted so synoboot disk was only one present. ata_piix is loaded. so I did it again while setup like this (no array), rebooted, and it's back again. any ideas?

Share this post


Link to post
Share on other sites

You need to remove the driver from the ramdisk, code above will only work after DSM is installed. I will make it easier to add/remove drivers on the next release.

Share this post


Link to post
Share on other sites
You need to remove the driver from the ramdisk, code above will only work after DSM is installed. I will make it easier to add/remove drivers on the next release.

 

Okay, thanks. I wasn't sure I did it correctly the first time when I renamed the file. I guess that's what works for now.

 

edit: just posting back that I was able to get all 12 disks working in the same VM I made earlier that was ignoring slots 1 and 2. I had to remove ata_piix.ko from the ramdisk, and the next boot DSM said it reassmbled my array and needed to do a scandisk and reboot. Rebooted and all was good :grin:

 

I been having fun trying to break my gnoboot/Xpenology VM. So far I haven't lost any of my test data moving my array around to all different VM's, rebuilding arrays, expanding, ect :mrgreen:

Share this post


Link to post
Share on other sites

Alpha4 is available.

 

To load and unload drivers use the following parameters in grub:

[spoiler=]load:

kernel /zImage root=/dev/md0 ihd_num=1 netif_num=0 syno_hw_version=DS3612xs vga=0x370 mod_add=igb,zram

 

unload

kernel /zImage root=/dev/md0 ihd_num=1 netif_num=0 syno_hw_version=DS3612xs vga=0x370 mod_del=ata_piix,e1000

 

Share this post


Link to post
Share on other sites

cool, I'll give it a test :grin:

 

whats with the download changes? that jdownloader tool wants to install browser tool bars (no thanks)...

 

edit: found an online site that decrypts the DLC file.

 

edit2: did a little testing, seems to work good. haven't attached my array yet. will try that tomorrow.

Share this post


Link to post
Share on other sites

Hello

 

Sorry for a dumb question maybe, but i cannot find the answer.

What's the purpose/differences of the gnoboot version vs a 'traditionnal' transtor/VM install?

 

 

thanks a lot for all the work here!

Share this post


Link to post
Share on other sites
Hello

 

Sorry for a dumb question maybe, but i cannot find the answer.

What's the purpose/differences of the gnoboot version vs a 'traditionnal' transtor/VM install?

 

 

thanks a lot for all the work here!

 

Check features from page one.

Share this post


Link to post
Share on other sites

Dear gnoboot,

 

Could you live a links for the live CD? it have much version.

i.e. sus , ubuntu and/or xxx verion of live CD.

Or simply state, what is use at your side?

 

Thanks!

Share this post


Link to post
Share on other sites
Which version is appropriate for testing on real hardware?

use the latest one

 

Dear gnoboot,

 

Could you live a links for the live CD? it have much version.

i.e. sus , ubuntu and/or xxx verion of live CD.

Or simply state, what is use at your side?

 

Thanks!

Any livecd will work as long as it has dd. I'm using system rescue cd.

 

@Diverge,

I'm was able to reproduced the issue reported on ESXi. I will try to fixed it soon.

Share this post


Link to post
Share on other sites

@Diverge,

I'm was able to reproduced the issue reported on ESXi. I will try to fixed it soon.

 

Good to know, I was thinking maybe it was something I was doing wrong when going from .IMG's to virtual disks, or adding/removed stuff from the images (zImage, rd, kernel mods, ect).

Share this post


Link to post
Share on other sites

@Diverge,

I'm was able to reproduced the issue reported on ESXi. I will try to fixed it soon.

 

Good to know, I was thinking maybe it was something I was doing wrong when going from .IMG's to virtual disks, or adding/removed stuff from the images (zImage, rd, kernel mods, ect).

 

My init script was broken starting from alpha3 to the latest release which cause auto shutdown for fresh installs. Will try to fix it this week.

Share this post


Link to post
Share on other sites

Features:

....[*]Works with original or custom version 4.x/5.x pat files, tested with DS3612xs and RS3614xs+ pat files.

 

 

First I'd like to thank you for all your work :smile: But I have one question. Does dis mean, if using XPEnology gnoBoot it is possible to simply use a orginal pat file from the Synology website? And if I did understand it correctly also online updates will be working without modification?

 

Thanks for clarification.

 

Regards

Vlaves

Share this post


Link to post
Share on other sites

Features:

....[*]Works with original or custom version 4.x/5.x pat files, tested with DS3612xs and RS3614xs+ pat files.

 

 

First I'd like to thank you for all your work :smile: But I have one question. Does dis mean, if using XPEnology gnoBoot it is possible to simply use a orginal pat file from the Synology website? And if I did understand it correctly also online updates will be working without modification?

 

Thanks for clarification.

 

Regards

Vlaves

 

You can use original pats, I have every time I played with a new install. I'm not 100% sure about the updates, since I followed a guide here that changes the updater script just before you apply the updates so it doesn't try to reflash over the boot flash (i'm not sure if there is any built in protection in gnoboot to prevent that - would be cool if there was :smile:).

Share this post


Link to post
Share on other sites

 

You can use original pats, I have every time I played with a new install. I'm not 100% sure about the updates, since I followed a guide here that changes the updater script just before you apply the updates so it doesn't try to reflash over the boot flash (i'm not sure if there is any built in protection in gnoboot to prevent that - would be cool if there was :smile:).

 

I will try to re-write a new updater script, but users will have to learn how to make their own pat files and not my priority right now. I don't also want to distribute pat files :grin: .

 

For those who want to try my boot image, please wait for the next release as it will include the fix for auto shutdown issue. But it's ok if you're just upgrading from an older release. This means you are not upgrading/updating DSM to the latest version.

 

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

Share this post


Link to post
Share on other sites

Thanks for the update.

 

I personally like using the stock synology PATS, and would rather not rely on modified pats. I was hoping there would be some way to prevent the updates from messing with the boot image. Editing the updater script between download and pressing update works, and that just seems to prevent a portion of the updater script from writing to boot. Can the boot image be set to read only, or does info get written to it under normal use? And if I seem to not know what I am talking about, can you explain how different parts of synology DSM work (boot, updates, ect)?

Share this post


Link to post
Share on other sites

I've already tricked updater script to write on a seperate partition. Though, I haven't included it on the current boot image as it makes a larger download (32MB - /dev/synoboot1, 96MB - /dev/synoboot2). After updating the boot image, it will then update the hardware BIOS which break the whole update process. I've already posted some screenshot while trying to make it work on DSM 5.0 beta.

 

IMHO, update/upgrade process:

  • upload pat file to DSM and verify checksum
  • extract hda1.tgz to a certain directory
  • verify checksum, update kernel and grub
  • update AMI bios firmware
  • reboot???
  • /etc/upgrade.sh will remove the current root directory and move the extracted hda1.tgz (I tried this part but it breaks DSM installation)
  • gnoboot will replace any updated kernel drivers.

Share this post


Link to post
Share on other sites
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?

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites
I have tried it for my HP N54L (Real PC), but cannot boot. Have anyone can boot it on N54L?

 

Thanks.

i thinks there is no Nic driver so we can not find n54l from PC . thanks your lspci infomation. i can not get it now because i had running esxi.

Share this post


Link to post
Share on other sites
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 sorry i had use esxi now so i can not get the lspci -v information .But now there are friends to provide it.

Share this post


Link to post
Share on other sites

Thank the file!

 

Here is my problem.

 

I use win32diskimager write the alpha4 image to USB but can't boot. But I use Trantor's DSM 5.0b image file boot ok!

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.