Trial of Nanoboot (4493) - 5.0.3.1


Recommended Posts

Did there is another location in the US or Europe to downlad Nanoboot ?

 

Thanks

 

Back a page or 2 someone posted links to other filehosts that work in US and I assume EU. I tried to use the chinese one, but most of the time page doesn't load, and when it does I dunno what I am doing and all sorts of audio clips start opening :lol:

Link to post
Share on other sites
You are correct. When I compared the two files I discovered my mistake. Uploaded new Image.

 

Download Xpenology NanoBoot 5.0-4482 bootloader ISO X64.

Download Xpenology NanoBoot 5.0-4482 bootloader ISO X86.

 

Hi,

Can you explain please how did you alter / create that iso ? i would like to do same for latest version of nanoboot

 

Thanks for your comprehension

XT

Link to post
Share on other sites
You are correct. When I compared the two files I discovered my mistake. Uploaded new Image.

 

Download Xpenology NanoBoot 5.0-4482 bootloader ISO X64.

Download Xpenology NanoBoot 5.0-4482 bootloader ISO X86.

 

Hi,

Can you explain please how did you alter / create that iso ? i would like to do same for latest version of nanoboot

 

Thanks for your comprehension

XT

 

I'm not sure how he created them originally, but to update them just download one of the ISO's. Use a ISO program that allows ISO editing (UltraISO), and swap the zImage. You can also make changes to the syslinux menu's as well if you need. Save the changes to ISO and you're done.

 

On a side note, if anyone knows how to make esxi always boot off the cdrom (iso) it would be helpful. VM Bios changes to boot order don't stick :cry:

Edited by Guest
Link to post
Share on other sites
Are there any performance improvements with using the x64 nanoboot or not really is it more hardware compatibility..?

gnoboot and trantor have always been x64, nanoboot x64 wud be the best to use, x86 was added to support older/slower hardware :smile:

 

x86 is just magic for those like me who rent a VPS with a cpu which don't have VT enabled , you can setup your Xpen VM easily with virtualbox

Link to post
Share on other sites

LSI 8i-9211 still not working correctly. It detects the card, and the attached drives. but comes up with an error when I think it tries to assign drive letter (sda, sdb, ect). It then unloads and reloads the driver, and retries again. See attached pictures.

 

TQ6xLKX.png

gufWzkd.png

GrIAKjv.png

 

edit: google returns some hits for that error, but I don't really know anything about compiling/building kernels https://www.google.com/search?q=SCSI+disk+(sd)+name+lenght+exceeded&oq=SCSI+disk+(sd)+name+lenght+exceeded&aqs=chrome..69i57.15892j0j7&sourceid=chrome&es_sm=93&ie=UTF-8#q=mpt2sas+SCSI+disk+(sd)+name+length+exceeded&start=0

 

everything works fine with previous gnoboot, for what it's worth. Here's portion of dmesg from gnoboot:

 

[    1.214198] Fusion MPT base driver 3.04.20
[    1.214200] Copyright (c) 1999-2008 LSI Corporation
[    1.220690] Fusion MPT SPI Host driver 3.04.20
[    1.224541] Fusion MPT SAS Host driver 3.04.20
[    1.228567] mpt2sas version 13.100.00.00 loaded
[    1.228687] scsi0 : Fusion MPT SAS Host
[    1.229615] mpt2sas 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[    1.229689] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (6118628 kB)
[    1.230110] mpt2sas 0000:03:00.0: irq 72 for MSI/MSI-X
[    1.230366] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 72
[    1.230368] mpt2sas0: iomem(0x00000000fd4fc000), mapped(0xffffc90008230000), size(16384)
[    1.230369] mpt2sas0: ioport(0x0000000000004000), size(256)
[    1.345288] mpt2sas0: Allocated physical memory: size(7418 kB)
[    1.345290] mpt2sas0: Current Controller Queue Depth(3307), Max Controller Queue Depth(3432)
[    1.345291] mpt2sas0: Scatter Gather Elements per IO(128)
[    1.403667] mpt2sas0: LSISAS2008: FWVersion(18.00.00.00), ChipRevision(0x03), BiosVersion(07.35.00.00)
[    1.403671] mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)
[    1.403750] mpt2sas0: sending port enable !!
[    1.407717] mpt2sas0: host_add: handle(0x0001), sas_addr(0x500605b004f0ff80), phys(8)
[    1.415051] mpt2sas0: port enable: SUCCESS
[    1.416875] scsi 0:0:0:0: Direct-Access     WDC      WD30EFRX-68EUZN0         0A80 PQ: 0 ANSI: 6
[    1.416880] scsi 0:0:0:0: SATA: handle(0x000c), sas_addr(0x4433221103000000), phy(3), device_name(0x50014ee003bb2b5f)
[    1.416882] scsi 0:0:0:0: SATA: enclosure_logical_id(0x500605b004f0ff80), slot(0)
[    1.416981] scsi 0:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[    1.416984] scsi 0:0:0:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[    1.417127] syno_disk_type_get: disk driver 'Fusion MPT SAS Host'
[    1.417128] syno_disk_type_get: Got UNKNOWN port type 0
[    1.417133] sd_probe: Got UNKNOWN dev_prefix (sd), index (0), disk_name (sda), disk_len (20)
[    1.417562] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    1.417776] sd 0:0:0:0: [sda] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
[    1.417778] sd 0:0:0:0: [sda] 4096-byte physical blocks
[    1.420713] scsi 0:0:1:0: Direct-Access     WDC      WD30EFRX-68EUZN0         0A80 PQ: 0 ANSI: 6
[    1.420718] scsi 0:0:1:0: SATA: handle(0x0009), sas_addr(0x4433221100000000), phy(0), device_name(0x50014ee003c0786f)
[    1.420720] scsi 0:0:1:0: SATA: enclosure_logical_id(0x500605b004f0ff80), slot(3)
[    1.420818] scsi 0:0:1:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[    1.420820] scsi 0:0:1:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[    1.421124] syno_disk_type_get: disk driver 'Fusion MPT SAS Host'
[    1.421125] syno_disk_type_get: Got UNKNOWN port type 0
[    1.421129] sd_probe: Got UNKNOWN dev_prefix (sd), index (1), disk_name (sdb), disk_len (20)
[    1.421675] sd 0:0:1:0: Attached scsi generic sg1 type 0
[    1.421697] sd 0:0:1:0: [sdb] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
[    1.421701] sd 0:0:1:0: [sdb] 4096-byte physical blocks
[    1.422712] sd 0:0:0:0: [sda] Write Protect is off
[    1.422714] sd 0:0:0:0: [sda] Mode Sense: 7f 00 10 08
[    1.423642] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    1.424698] scsi 0:0:2:0: Direct-Access     WDC      WD30EFRX-68EUZN0         0A80 PQ: 0 ANSI: 6
[    1.424703] scsi 0:0:2:0: SATA: handle(0x000b), sas_addr(0x4433221101000000), phy(1), device_name(0x50014ee0ae685dac)
[    1.424705] scsi 0:0:2:0: SATA: enclosure_logical_id(0x500605b004f0ff80), slot(2)
[    1.424797] scsi 0:0:2:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[    1.424800] scsi 0:0:2:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[    1.425366] syno_disk_type_get: disk driver 'Fusion MPT SAS Host'
[    1.425368] syno_disk_type_get: Got UNKNOWN port type 0
[    1.425370] sd_probe: Got UNKNOWN dev_prefix (sd), index (2), disk_name (sdc), disk_len (20)
[    1.425975] sd 0:0:2:0: [sdc] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
[    1.425977] sd 0:0:2:0: [sdc] 4096-byte physical blocks
[    1.426204] sd 0:0:2:0: Attached scsi generic sg2 type 0
[    1.426545] sd 0:0:1:0: [sdb] Write Protect is off
[    1.426548] sd 0:0:1:0: [sdb] Mode Sense: 7f 00 10 08
[    1.427353] sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    1.429577] scsi 0:0:3:0: Direct-Access     WDC      WD30EFRX-68EUZN0         0A80 PQ: 0 ANSI: 6
[    1.429581] scsi 0:0:3:0: SATA: handle(0x000a), sas_addr(0x4433221102000000), phy(2), device_name(0x50014ee2b448831f)
[    1.429583] scsi 0:0:3:0: SATA: enclosure_logical_id(0x500605b004f0ff80), slot(1)
[    1.429682] scsi 0:0:3:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[    1.429686] scsi 0:0:3:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[    1.429809] syno_disk_type_get: disk driver 'Fusion MPT SAS Host'
[    1.429810] syno_disk_type_get: Got UNKNOWN port type 0
[    1.429812] sd_probe: Got UNKNOWN dev_prefix (sd), index (3), disk_name (sdd), disk_len (20)
[    1.430507] sd 0:0:3:0: [sdd] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
[    1.430509] sd 0:0:3:0: [sdd] 4096-byte physical blocks
[    1.430614] sd 0:0:3:0: Attached scsi generic sg3 type 0
[    1.430801] sd 0:0:2:0: [sdc] Write Protect is off
[    1.430803] sd 0:0:2:0: [sdc] Mode Sense: 7f 00 10 08
[    1.431601] sd 0:0:2:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    1.435394] sd 0:0:3:0: [sdd] Write Protect is off
[    1.435396] sd 0:0:3:0: [sdd] Mode Sense: 7f 00 10 08
[    1.436233] sd 0:0:3:0: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    1.485006]  sdb: sdb1 sdb2 sdb5 sdb6
[    1.490802]  sdc: sdc1 sdc2 sdc5 sdc6
[    1.491694] sd 0:0:1:0: [sdb] Attached SCSI disk
[    1.492914]  sda: sda1 sda2 sda5 sda6
[    1.498366] sd 0:0:2:0: [sdc] Attached SCSI disk
[    1.500877]  sdd: sdd1 sdd2 sdd5 sdd6
[    1.502442] sd 0:0:0:0: [sda] Attached SCSI disk
[    1.508827] sd 0:0:3:0: [sdd] Attached SCSI disk
[    1.513352] megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006)
[    1.516371] megaraid: 2.20.5.1 (Release Date: Thu Nov 16 15:32:35 EST 2006)
[    1.519982] megasas: 00.00.06.12-rc1 Wed. Oct. 5 17:00:00 PDT 2011

Link to post
Share on other sites

Does anybody have a guide of how to install nanoboot with 4482 from scratch, on a clean new physical machine?

 

fma965 made a very useful tutorial (thank you fma965!) http://cyanlabs.co.uk/tutorials/synolog ... o-nanoboot but it's talking about migration from gnoboot. Unfortunately it's a bit confusing, also because there's a lot of virtualization stuff all over the place.

Link to post
Share on other sites
Does anybody have a guide of how to install nanoboot with 4482 from scratch, on a clean new physical machine?

 

fma965 made a very useful tutorial (thank you fma965!) http://cyanlabs.co.uk/tutorials/synolog ... o-nanoboot but it's talking about migration from gnoboot. Unfortunately it's a bit confusing, also because there's a lot of virtualization stuff all over the place.

 

Ok so people seem to want a guide specific to not using ESXi, i will see what i can do, as for fresh installs... well i can't seem to get that working, my best answer is just install gnoboot, once its booted to synology "desktop" shut it downa dn replace gnoboot with nanoboot then select upgrade/downgrade etc. etc.

Link to post
Share on other sites

Can we keep this thread for feedback on Nanoboot?

 

There's plenty of info in this forum on how to install on various systems, and once you know how to, it pretty much applies to all the different variations; trantors, gnoboot, nanboot...

Link to post
Share on other sites

Short question.

 

Background: I did an update with Nanoboot 5.0.2.2 yesterday directly from Trantors beta 5, very easy. Web-GUI said its migrateable and I chose Migration (keep files and most of the settings). I assume clean installation (keep your files) would have led to a swipe of the hard drives.

Uploaded original pat file and it works without additional adjustments. Maybe that helps some people.

 

Question: In the pic you'll see that the little one as a reminder of an update did not disappear. Upon checking, it says, latest version installed. Why doesnt the red 1 disappear?

Clipboard01.jpg.d83252f1a912934937908c966c5620d2.jpg

Link to post
Share on other sites
Short question.

 

Background: I did an update with Nanoboot 5.0.2.2 yesterday directly from Trantors beta 5, very easy. Web-GUI said its migrateable and I chose Migration (keep files and most of the settings). I assume clean installation (keep your files) would have led to a swipe of the hard drives.

Uploaded original pat file and it works without additional adjustments. Maybe that helps some people.

 

Question: In the pic you'll see that the little one as a reminder of an update did not disappear. Upon checking, it says, latest version installed. Why doesnt the red 1 disappear?

 

No one knows the reasoning, or how to get rid of that (without redoing the whole system). I have that as well. Happened from 4458 update 1 to update 2 for me.

Link to post
Share on other sites

Nanoboot 5.0.2.2 broke my network connection just like gnoBoot, on a Gigabyte GA-H87M-HD3 which has a Realtek 8111F NIC.

 

gnoboot-alpha-10.5 loads r8168 (v8.037?), LAN disconnects unless ethernet cable is unplugged and reinserted

Nanoboot 5.0.2.1 loads r8169, no LAN problems

Nanoboot 5.0.2.2 loads r8168 (v8.038), LAN disconnects unless ethernet cable is unplugged and reinserted

 

Tried rmmod=r8168 inmod=r8169_new, no LAN connectivity at all.

Link to post
Share on other sites
Nanoboot 5.0.2.2 broke my network connection just like gnoBoot, on a Gigabyte GA-H87M-HD3 which has a Realtek 8111F NIC.

 

gnoboot-alpha-10.5 loads r8168 (v8.037?), LAN disconnects unless ethernet cable is unplugged and reinserted

Nanoboot 5.0.2.1 loads r8169, no LAN problems

Nanoboot 5.0.2.2 loads r8168 (v8.038), LAN disconnects unless ethernet cable is unplugged and reinserted

 

Tried rmmod=r8168 inmod=r8169_new, no LAN connectivity at all.

 

Is "insmod" instead "inmod", try again.

Link to post
Share on other sites
Nanoboot 5.0.2.2 broke my network connection just like gnoBoot, on a Gigabyte GA-H87M-HD3 which has a Realtek 8111F NIC.

 

gnoboot-alpha-10.5 loads r8168 (v8.037?), LAN disconnects unless ethernet cable is unplugged and reinserted

Nanoboot 5.0.2.1 loads r8169, no LAN problems

Nanoboot 5.0.2.2 loads r8168 (v8.038), LAN disconnects unless ethernet cable is unplugged and reinserted

 

Tried rmmod=r8168 inmod=r8169_new, no LAN connectivity at all.

 

Is "insmod" instead "inmod", try again.

Same result

Link to post
Share on other sites
Hi,

 

I have 2 LSI 9211 SAS cards and drives connected to SAS cards in nanoboot 5.0.2.2 are not being detect.

 

Check dmesg, and see if you're getting same errors in the pics I posted a few posts back.

 

Can you help me to test it? I will send a test firmware for you.

Link to post
Share on other sites
Hi,

 

I have 2 LSI 9211 SAS cards and drives connected to SAS cards in nanoboot 5.0.2.2 are not being detect.

 

Check dmesg, and see if you're getting same errors in the pics I posted a few posts back.

 

Can you help me to test it? I will send a test firmware for you.

 

Sure, I don't mind testing stuff. It's fun for me. Let me know when you have something for me to test.

Link to post
Share on other sites
Lol?

It's a Xeon E3 btw and not Core i3. I guess recognizing this in a VM is not so easy. And it's not important to me. Just out of curiosity.

 

That's just cosmetic stuff in DSM. If you check dmesg you'll see your real hardware. Mine says i7 3770T in dmesg, but i3 in DSM (same as in the picture).

Link to post
Share on other sites
Lol?

It's a Xeon E3 btw and not Core i3. I guess recognizing this in a VM is not so easy. And it's not important to me. Just out of curiosity.

 

That's just cosmetic stuff in DSM. If you check dmesg you'll see your real hardware. Mine says i7 3770T in dmesg, but i3 in DSM (same as in the picture).

 

Does that count for v-cores as well?

I assigned 2 cores to my VM but DSM is not showing them.

Are the 2 cores actually working right now?

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.