Sign in to follow this  
gnoboot

XPEnology gnoBoot v5-4418

Recommended Posts

hi

any guide to what if anything to change on boot stick

 

tried an upgrade but get error 2 temp directory problem not sure what the error is

would really like to get this working as vpn is fixed and doesn't take over whole interface

tested on my ds111 and works great

Share this post


Link to post
Share on other sites
nice!,could you publish image gnoBoot image for v5?

I'm still working on seamless upgrade from v4 :wink:

[spoiler=]ncmb0h.png

 

Edit: upgrade doesn't workout properly :cry: , get gnoBoot image for v5 on my main thread.

Share this post


Link to post
Share on other sites

get as far synoacl_ext4 ok then hangs on a dell 330

4.3 trantor v1.0 was ok any ideas whats hanging it

Share this post


Link to post
Share on other sites
get as far synoacl_ext4 ok then hangs on a dell 330

4.3 trantor v1.0 was ok any ideas whats hanging it

 

I built it just for fun, so expect it not working properly. Try it first on a VM :wink:

 

Initial Test:

  • NFS working
  • iSCSI (LIO) regular files working, you have to copy the modules from 4.3.
  • IET broken and LIO block

Share this post


Link to post
Share on other sites

It seems to install fine for me (besides it saying it's installing to 2 disks), then stalls here on boot:

 

jgvnRlU.png

 

edit: it seems to have installed, it was at a new IP. The console is buggy though... it's like lagged. can't see what you type until you hit enter.

 

edit2: after a reboot of first boot, no more console lag, also didn't see that message again.

Share this post


Link to post
Share on other sites

Something I just noticed playing around. you can't put disks is slots 1 and 2. The first disk starts off in slot 3.

 

I created 12 x 8GB virtual drives, but can only use 10 of them, as nothing goes into slots 1 and 2. Also, I'm pretty sure this happens for both versions of gnoboot DSM 4.3 and 4.5, at least for me, on my system using ESXI 5.5 and a Intel DH61AG motherboard.

 

edit:

DS45> cat /proc/partitions
major minor  #blocks  name

  8        0     204800 sda
  8        1      16033 sda1
  8       32    8388608 sdc
  8       33    2490240 sdc1
  8       34    2097152 sdc2
  8       35          1 sdc3
  8       37    3654768 sdc5
  8       48    8388608 sdd
  8       49    2490240 sdd1
  8       50    2097152 sdd2
  8       51          1 sdd3
  8       53    3654768 sdd5
  8       64    8388608 sde
  8       65    2490240 sde1
  8       66    2097152 sde2
  8       67          1 sde3
  8       69    3654768 sde5
  8       80    8388608 sdf
  8       81    2490240 sdf1
  8       82    2097152 sdf2
  8       83          1 sdf3
  8       85    3654768 sdf5
  8       96    8388608 sdg
  8       97    2490240 sdg1
  8       98    2097152 sdg2
  8       99          1 sdg3
  8      101    3654768 sdg5
  8      112    8388608 sdh
  8      113    2490240 sdh1
  8      114    2097152 sdh2
  8      115          1 sdh3
  8      117    3654768 sdh5
  8      128    8388608 sdi
  8      129    2490240 sdi1
  8      130    2097152 sdi2
  8      131          1 sdi3
  8      133    3654768 sdi5
  8      144    8388608 sdj
  8      145    2490240 sdj1
  8      146    2097152 sdj2
  8      147          1 sdj3
  8      149    3654768 sdj5
  8      160    8388608 sdk
  8      161    2490240 sdk1
  8      162    2097152 sdk2
  8      163          1 sdk3
  8      165    3654768 sdk5
  8      176    8388608 sdl
  8      177    2490240 sdl1
  8      178    2097152 sdl2
  8      179          1 sdl3
  8      181    3654768 sdl5
  8      192    8388608 sdm
  8      208    8388608 sdn
  9        0    2490176 md0
  9        1    2097088 md1
  9        2   32883264 md2
253        0   32882688 dm-0
DS45>

 

DS45> fdisk -l

Disk /dev/sdc: 8589 MB, 8589934592 bytes
64 heads, 32 sectors/track, 8192 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

  Device Boot      Start         End      Blocks  Id System
/dev/sdc1               1        2432     2490240  fd Linux raid autodetect
Partition 1 does not end on cylinder boundary
/dev/sdc2            2433        4480     2097152  fd Linux raid autodetect
Partition 2 does not end on cylinder boundary
/dev/sdc3            4609        8185     3662816   f Win95 Ext'd (LBA)
Partition 3 does not end on cylinder boundary
/dev/sdc5            4616        8185     3654768  fd Linux raid autodetect

Disk /dev/sdd: 8589 MB, 8589934592 bytes
64 heads, 32 sectors/track, 8192 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

  Device Boot      Start         End      Blocks  Id System
/dev/sdd1               1        2432     2490240  fd Linux raid autodetect
Partition 1 does not end on cylinder boundary
/dev/sdd2            2433        4480     2097152  fd Linux raid autodetect
Partition 2 does not end on cylinder boundary
/dev/sdd3            4609        8185     3662816   f Win95 Ext'd (LBA)
Partition 3 does not end on cylinder boundary
/dev/sdd5            4616        8185     3654768  fd Linux raid autodetect

Disk /dev/sde: 8589 MB, 8589934592 bytes
64 heads, 32 sectors/track, 8192 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

  Device Boot      Start         End      Blocks  Id System
/dev/sde1               1        2432     2490240  fd Linux raid autodetect
Partition 1 does not end on cylinder boundary
/dev/sde2            2433        4480     2097152  fd Linux raid autodetect
Partition 2 does not end on cylinder boundary
/dev/sde3            4609        8185     3662816   f Win95 Ext'd (LBA)
Partition 3 does not end on cylinder boundary
/dev/sde5            4616        8185     3654768  fd Linux raid autodetect

Disk /dev/sdf: 8589 MB, 8589934592 bytes
64 heads, 32 sectors/track, 8192 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

  Device Boot      Start         End      Blocks  Id System
/dev/sdf1               1        2432     2490240  fd Linux raid autodetect
Partition 1 does not end on cylinder boundary
/dev/sdf2            2433        4480     2097152  fd Linux raid autodetect
Partition 2 does not end on cylinder boundary
/dev/sdf3            4609        8185     3662816   f Win95 Ext'd (LBA)
Partition 3 does not end on cylinder boundary
/dev/sdf5            4616        8185     3654768  fd Linux raid autodetect

Disk /dev/sdg: 8589 MB, 8589934592 bytes
64 heads, 32 sectors/track, 8192 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

  Device Boot      Start         End      Blocks  Id System
/dev/sdg1               1        2432     2490240  fd Linux raid autodetect
Partition 1 does not end on cylinder boundary
/dev/sdg2            2433        4480     2097152  fd Linux raid autodetect
Partition 2 does not end on cylinder boundary
/dev/sdg3            4609        8185     3662816   f Win95 Ext'd (LBA)
Partition 3 does not end on cylinder boundary
/dev/sdg5            4616        8185     3654768  fd Linux raid autodetect

Disk /dev/sdh: 8589 MB, 8589934592 bytes
64 heads, 32 sectors/track, 8192 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

  Device Boot      Start         End      Blocks  Id System
/dev/sdh1               1        2432     2490240  fd Linux raid autodetect
Partition 1 does not end on cylinder boundary
/dev/sdh2            2433        4480     2097152  fd Linux raid autodetect
Partition 2 does not end on cylinder boundary
/dev/sdh3            4609        8185     3662816   f Win95 Ext'd (LBA)
Partition 3 does not end on cylinder boundary
/dev/sdh5            4616        8185     3654768  fd Linux raid autodetect

Disk /dev/sdi: 8589 MB, 8589934592 bytes
64 heads, 32 sectors/track, 8192 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

  Device Boot      Start         End      Blocks  Id System
/dev/sdi1               1        2432     2490240  fd Linux raid autodetect
Partition 1 does not end on cylinder boundary
/dev/sdi2            2433        4480     2097152  fd Linux raid autodetect
Partition 2 does not end on cylinder boundary
/dev/sdi3            4609        8185     3662816   f Win95 Ext'd (LBA)
Partition 3 does not end on cylinder boundary
/dev/sdi5            4616        8185     3654768  fd Linux raid autodetect

Disk /dev/sdj: 8589 MB, 8589934592 bytes
64 heads, 32 sectors/track, 8192 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

  Device Boot      Start         End      Blocks  Id System
/dev/sdj1               1        2432     2490240  fd Linux raid autodetect
Partition 1 does not end on cylinder boundary
/dev/sdj2            2433        4480     2097152  fd Linux raid autodetect
Partition 2 does not end on cylinder boundary
/dev/sdj3            4609        8185     3662816   f Win95 Ext'd (LBA)
Partition 3 does not end on cylinder boundary
/dev/sdj5            4616        8185     3654768  fd Linux raid autodetect

Disk /dev/sdk: 8589 MB, 8589934592 bytes
64 heads, 32 sectors/track, 8192 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

  Device Boot      Start         End      Blocks  Id System
/dev/sdk1               1        2432     2490240  fd Linux raid autodetect
Partition 1 does not end on cylinder boundary
/dev/sdk2            2433        4480     2097152  fd Linux raid autodetect
Partition 2 does not end on cylinder boundary
/dev/sdk3            4609        8185     3662816   f Win95 Ext'd (LBA)
Partition 3 does not end on cylinder boundary
/dev/sdk5            4616        8185     3654768  fd Linux raid autodetect

Disk /dev/sdl: 8589 MB, 8589934592 bytes
64 heads, 32 sectors/track, 8192 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

  Device Boot      Start         End      Blocks  Id System
/dev/sdl1               1        2432     2490240  fd Linux raid autodetect
Partition 1 does not end on cylinder boundary
/dev/sdl2            2433        4480     2097152  fd Linux raid autodetect
Partition 2 does not end on cylinder boundary
/dev/sdl3            4609        8185     3662816   f Win95 Ext'd (LBA)
Partition 3 does not end on cylinder boundary
/dev/sdl5            4616        8185     3654768  fd Linux raid autodetect

Disk /dev/sdm: 8589 MB, 8589934592 bytes
64 heads, 32 sectors/track, 8192 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Disk /dev/sdm doesn't contain a valid partition table

Disk /dev/sdn: 8589 MB, 8589934592 bytes
64 heads, 32 sectors/track, 8192 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Disk /dev/sdn doesn't contain a valid partition table
DS45>

 

first data drive always starts at sdc for me. The 11 and 12 disks get ingnored since DSM isn't looking at anything past sdl, since it's not using sda and sdb for data drives for some reason. sda is gnoBoot I guess.

Share this post


Link to post
Share on other sites
Something I just noticed playing around. you can't put disks is slots 1 and 2. The first disk starts off in slot 3.

 

I created 12 x 8GB virtual drives, but can only use 10 of them, as nothing goes into slots 1 and 2. Also, I'm pretty sure this happens for both versions of gnoboot DSM 4.3 and 4.5, at least for me, on my system using ESXI 5.5 and a Intel DH61AG motherboard.

 

edit:

DS45> cat /proc/partitions
major minor  #blocks  name

  8        0     204800 sda
  8        1      16033 sda1
  8       32    8388608 sdc
  8       33    2490240 sdc1
  8       34    2097152 sdc2
  8       35          1 sdc3
  8       37    3654768 sdc5
  8       48    8388608 sdd
  8       49    2490240 sdd1
  8       50    2097152 sdd2
  8       51          1 sdd3
  8       53    3654768 sdd5
  8       64    8388608 sde
  8       65    2490240 sde1
  8       66    2097152 sde2
  8       67          1 sde3
  8       69    3654768 sde5
  8       80    8388608 sdf
  8       81    2490240 sdf1
  8       82    2097152 sdf2
  8       83          1 sdf3
  8       85    3654768 sdf5
  8       96    8388608 sdg
  8       97    2490240 sdg1
  8       98    2097152 sdg2
  8       99          1 sdg3
  8      101    3654768 sdg5
  8      112    8388608 sdh
  8      113    2490240 sdh1
  8      114    2097152 sdh2
  8      115          1 sdh3
  8      117    3654768 sdh5
  8      128    8388608 sdi
  8      129    2490240 sdi1
  8      130    2097152 sdi2
  8      131          1 sdi3
  8      133    3654768 sdi5
  8      144    8388608 sdj
  8      145    2490240 sdj1
  8      146    2097152 sdj2
  8      147          1 sdj3
  8      149    3654768 sdj5
  8      160    8388608 sdk
  8      161    2490240 sdk1
  8      162    2097152 sdk2
  8      163          1 sdk3
  8      165    3654768 sdk5
  8      176    8388608 sdl
  8      177    2490240 sdl1
  8      178    2097152 sdl2
  8      179          1 sdl3
  8      181    3654768 sdl5
  8      192    8388608 sdm
  8      208    8388608 sdn
  9        0    2490176 md0
  9        1    2097088 md1
  9        2   32883264 md2
253        0   32882688 dm-0
DS45>

 

first data drive always starts at sdc for me. The 11 and 12 disks get ingnored since DSM isn't looking at anything past sdl, since it's not using sda and sdb for data drives for some reason. sda is gnoBoot I guess.

 

sda is gnoboot;), unless you want to stick usb on your VM :razz:

 

Another issue, mac address is random in v5. Will fixed it at a later time. Enjoy my build!

Share this post


Link to post
Share on other sites

 

sda is gnoboot;), unless you want to stick usb on your VM :razz:

 

Another issue, mac address is random in v5. Will fixed it at a later time. Enjoy my build!

 

No thanks (on USB stick), but there must be better way to do it. I'm not complaining, or trying to create work for you. I figure you made gnoBoot cause you like to create and fix stuff :smile:

 

I have another ESXI system. It's my main system and has been running for over 6 months on DSM 4.2. It's not based on trantor's builds, its step by step from the ESXI pdf someone made. Anyway, that VM doesn't mount boot as sda. sda is the first data disk. So there must be a way to do it :razz:

 

Below is an ESXI 5.1 system with 4 physical 2TB disks using RDM mapping with DSM 4.2.

BusyBox v1.16.1 (2013-03-01 01:11:47 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

DiskStation> cat /proc/partitions
major minor  #blocks  name

  8        0 1953514584 sda
  8        1    2490240 sda1
  8        2    2097152 sda2
  8        3          1 sda3
  8        5 1948780864 sda5
  8       16 1953514584 sdb
  8       17    2490240 sdb1
  8       18    2097152 sdb2
  8       19          1 sdb3
  8       21 1948780864 sdb5
  8       32 1953514584 sdc
  8       33    2490240 sdc1
  8       34    2097152 sdc2
  8       35          1 sdc3
  8       37 1948780864 sdc5
  8       48 1953514584 sdd
  8       49    2490240 sdd1
  8       50    2097152 sdd2
  8       51          1 sdd3
  8       53 1948780864 sdd5
  9        0    2490176 md0
  9        1    2097088 md1
  9        2 5846338944 md2
253        0 5846335488 dm-0
DiskStation>

 

If you want to fix it, somehow, so synoboot isn't mounted by itself as sda, i'll be glad to keep testing for ya :grin: It seems DS3612 DSM only looks at sda-sdl for it's 12 data disks. Is it possible to mount gnoboot to something higher than sdl or not at all like above example? Not that I ever plan to use so many disks.

Edited by Guest

Share this post


Link to post
Share on other sites

 

sda is gnoboot;), unless you want to stick usb on your VM :razz:

 

Another issue, mac address is random in v5. Will fixed it at a later time. Enjoy my build!

 

No thanks (on USB stick), but there must be better way to do it. I'm not complaining, or trying to create work for you. I figure you made gnoBoot cause you like to create and fix stuff :smile:

 

I have another ESXI system. It's my main system and has been running for over 6 months on DSM 4.2. It's not based on trantor's builds, its step by step from the ESXI pdf someone made. Anyway, that VM doesn't mount boot as sda. sda is the first data disk. So there must be a way to do it :razz:

 

BusyBox v1.16.1 (2013-03-01 01:11:47 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

DiskStation> cat /proc/partitions
major minor  #blocks  name

  8        0 1953514584 sda
  8        1    2490240 sda1
  8        2    2097152 sda2
  8        3          1 sda3
  8        5 1948780864 sda5
  8       16 1953514584 sdb
  8       17    2490240 sdb1
  8       18    2097152 sdb2
  8       19          1 sdb3
  8       21 1948780864 sdb5
  8       32 1953514584 sdc
  8       33    2490240 sdc1
  8       34    2097152 sdc2
  8       35          1 sdc3
  8       37 1948780864 sdc5
  8       48 1953514584 sdd
  8       49    2490240 sdd1
  8       50    2097152 sdd2
  8       51          1 sdd3
  8       53 1948780864 sdd5
  9        0    2490176 md0
  9        1    2097088 md1
  9        2 5846338944 md2
253        0 5846335488 dm-0
DiskStation>

Yes, there is. Use alpha0 kernel and update the rd.gz from alpha2;) You can also put your gnoboot on the last port for SATA/SCSI disk, so it won't become sda.

 

Edit: Changing disk port order in your VMX file.

before:
sata0.present = "TRUE"
sata0:0.present = "TRUE"
sata0:0.fileName = "gnoboot-0.vmdk" <---- boot image
sata0:0.redo = ""
sata0.pciSlotNumber = "36"
sata0:1.present = "TRUE"
sata0:1.fileName = "gnoboot-1.vmdk"

after:
sata0.present = "TRUE"
sata0:0.present = "TRUE"
sata0:0.fileName = "gnoboot-1.vmdk" 
sata0:0.redo = ""
sata0.pciSlotNumber = "36"
sata0:1.present = "TRUE"
sata0:1.fileName = "gnoboot-0.vmdk" <---- boot image

Share this post


Link to post
Share on other sites

I found an easier way to get rid of gnoBoot mounting itself in DSM. just move it to IDE 1:0 instead of 0:0 right in ESXI - no editing of config files necessary. It's no longer listed in /proc/partitions. Only problem now is disk slots 1 and 2 still aren't usable. my last 2 drives out of 12 are mounted as sdm and sdn. DSM looks for disk 1, 2, 3...12 as sda, sdb, sdc...sdl,everything else is ignored for building volumes.

 

my first data disk is SCSI 0:0 and it gets mounted by gnoboot (dsm) as sdc for some reason.

 

edit: I guess because it sees IDE 0:0 and IDE 0:1 even though there are no drives attached to them, and reserves those for sda and sdb.

Share this post


Link to post
Share on other sites

make sense to me, have you tried using SCSI as boot image? One of my test machines uses SCSI and it maps to sdaeX.

Share this post


Link to post
Share on other sites
make sense to me, have you tried using SCSI as boot image? One of my test machines uses SCSI and it maps to sdaeX.

 

I haven't tried that, but I don't think it will make a difference. I was playing around in the VM bios, and it has 2 IDE controllers built in (primary and secondary), which would be 0:0,0:1,1:0,1:1, since I see my gnoBoot drive attached to the secondary controller after I moved it to 1:0. I can disable primary IDE in the bios, but settings don't stick even after I hit save. Apparently you can extract ESXI virtual machine bios and edit it http://forums.mydigitallife.info/thread ... ols/page10 . I've edited my physical machine bioes before, but that just seems like too much work for testing purposes :razz:

Share this post


Link to post
Share on other sites

Me too. Anyway, I'm working on getting all the ATA drivers as modules. Or I would build a separate virtual boot image which doesn't include all the useless drivers with exception to RAID controllers. Would that be ok?

Share this post


Link to post
Share on other sites
Me too. Anyway, I'm working on getting all the ATA drivers as modules. Or I would build a separate virtual boot image which doesn't include all the useless drivers with exception to RAID controllers. Would that be ok?

 

How would modules work? Would you then need to add/remove a particular module for lets say in my case IDE, at initial boot, prior to installing?

Share this post


Link to post
Share on other sites
Me too. Anyway, I'm working on getting all the ATA drivers as modules. Or I would build a separate virtual boot image which doesn't include all the useless drivers with exception to RAID controllers. Would that be ok?

 

How would modules work? Would you then need to add/remove a particular module for lets say in my case IDE, at initial boot, prior to installing?

 

http://en.wikipedia.org/wiki/Loadable_kernel_module

 

For virtual machines, gnoboot image will not add any ATA drivers but you can still have an option to load it after installation. But this would bring problems to baremetal users during installation if drivers are not available.

 

EDIT: modular ATA drivers working - http://xpenology.com/forum/viewtopic.php?f=2&t=2152&p=11010#p11010

Share this post


Link to post
Share on other sites
Me too. Anyway, I'm working on getting all the ATA drivers as modules. Or I would build a separate virtual boot image which doesn't include all the useless drivers with exception to RAID controllers. Would that be ok?

 

How would modules work? Would you then need to add/remove a particular module for lets say in my case IDE, at initial boot, prior to installing?

 

http://en.wikipedia.org/wiki/Loadable_kernel_module

 

For virtual machines, gnoboot image will not add any ATA drivers but you can still have an option to load it after installation. But this would bring problems to baremetal users during installation if drivers are not available.

 

EDIT: modular ATA drivers working - http://xpenology.com/forum/viewtopic.php?f=2&t=2152&p=11010#p11010

 

Thanks. I'm learning about all this stuff as I play around with your gnoBoot :smile: I hope i'm not filling your thread with noob stuff hehe

Share this post


Link to post
Share on other sites

I know it is a bit unrelated, but I gotta ask. Is there any chance to get a PCI/PCIe WiFi card working with the "WiFi" option of DSM 5.0?

Share this post


Link to post
Share on other sites

It isn't about drivers, as I'm pretty sure the Linksys basic models are supported (they are usually in the list of default drivers), but about the UI/Synology systems. It specifies that it needs USB, and I am about to try the PCI Linksys card I have (WMP300N ver.2).

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.

Sign in to follow this