Jump to content
XPEnology Community

Trial of Nanoboot (4493) - 5.0.3.1


Recommended Posts

I can't get any sort of download links from http://nanoboot.tk/. http://www.colafile.com/u/sancome comes up as a not online, or an actual site.

 

Does anyone have a link to the latest version that isn't on a crappy file sharing site with a million hoops to jump through?

 

 

i cant download either to try it out. seems that link needs vip account to download :eek:

Link to comment
Share on other sites

I can't get any sort of download links from http://nanoboot.tk/. http://www.colafile.com/u/sancome comes up as a not online, or an actual site.

 

Does anyone have a link to the latest version that isn't on a crappy file sharing site with a million hoops to jump through?

 

 

i cant download either to try it out. seems that link needs vip account to download :eek:

 

It's free, but it seems relatively slow access from abroad.

Link to comment
Share on other sites

is there any way to unload modules like gnoboot, or just remove them?

 

I tried adding rmmod=ata_piix to kernel boot parameters, but it still loaded.

 

This parameter is working, it will be loaded first, and then unload the module.

 

I don't think it works correctly.

 

dmesg still shows ata_piix being loaded, also shows it's being used in lspci. The reason I need to unload it is because in my VM, it will include the nanoboot drive listed with drives in DSM. With gnboot I need to use rmmod=ata_piix to prevent (gnoboot/nanoboot installed as vmware IDE drive).

 

ata_piix not listed with lsmod, but shown in dmesg and lspci.

Link to comment
Share on other sites

I can confirm that after writing the nanoboot x64 to my previously used gnoboot flash drive, i booted and by using the boot menu "upgrade 4482" i was able to migrate my NAS to 5.0-4482)

My system was found as being "migrateable" and it was easy. Too easy.

Unfortunately i have lots of issues with DSM 5 and are not fixed with this upgrade. Apparently i need to do a fresh install.

Link to comment
Share on other sites

Can anyone else confirm if rmmod is working for them?

 

It doesn't seem to remove ata_piix for me.

 

[    0.000000] Linux version 3.2.40 (root@build2) (gcc version 4.7.3 20130102 (prerelease) (crosstool-NG 1.18.0) ) #2 SMP Sun May 11 16:32:06 CST 2014
[    0.000000] Command line: rmmod=ata_piix ihd_num=0 netif_num=4 syno_hw_version=DS3612xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=7 vga=0x305 debug BOOT_IMAGE=/zImage 
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
..
[    0.000000] Kernel command line: rmmod=ata_piix ihd_num=0 netif_num=4 syno_hw_version=DS3612xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=7 vga=0x305 debug BOOT_IMAGE=/zImage 
[    0.000000] Internal HD num: 0
[    0.000000] Internal netif num: 4
[    0.000000] Synology Hardware Version: DS3612xs-j
[    0.000000] Serial Number: B3J4N01003
[    0.000000] Synoboot VID: ea0
[    0.000000] Synoboot PID: 2168
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
[    0.000000] xsave/xrstor: enabled xstate_bv 0x7, cntxt size 0x340
[    0.000000] Checking aperture...
[    0.000000] No AGP bridge found
[    0.000000] Memory: 994632k/1048576k available (4230k kernel code, 516k absent, 53428k reserved, 4276k data, 27196k init)
[    0.000000] Hierarchical RCU implementation.
[    0.000000] 	CONFIG_RCU_FANOUT set to non-default value of 32
[    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
[    0.000000] NR_IRQS:4352 nr_irqs:512 16
[    0.000000] Extended CMOS year: 2000
[    0.000000] Console: colour dummy device 80x25
[    0.000000] console [tty0] enabled
[    0.000000] hpet clockevent registered
[    0.000000] TSC freq read from hypervisor : 2494.333 MHz
[    0.000000] Detected 2494.333 MHz processor.
[    0.000001] Calibrating delay loop (skipped) preset value.. 4988.66 BogoMIPS (lpj=2494333)
[    0.000004] pid_max: default: 32768 minimum: 301
[    0.000028] Mount-cache hash table entries: 256
[    0.000142] Disabled fast string operations
[    0.000150] CPU: Physical Processor ID: 0
[    0.000151] CPU: Processor Core ID: 0
[    0.000198] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    0.000199] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
[    0.000208] mce: CPU supports 0 MCE banks
[    0.000314] ACPI: Core revision 20110623
[    0.008195] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.018186] CPU0: Intel(R) Core(TM) i7-3770T CPU @ 2.50GHz stepping 09
[...
[    0.945260] Loading iSCSI transport class v2.0-870.
[    0.956900] rdac: device handler registered
[    0.959041] ata_piix 0000:00:07.1: version 2.13
[    0.964294] scsi0 : ata_piix
[    0.965764] scsi1 : ata_piix
[    0.966218] ata1: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0x1060 irq 14
[    0.966240] ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0x1068 irq 15
[    0.966255] Enable Synology sata fast booting
[    0.966269] ata1: COMRESET failed (errno=-95)
[    0.966282] ata2: COMRESET failed (errno=-95)
[    0.971889] i8042: PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:MOUS] at 0x60,0x64 irq 1,12
[    0.973185] serio: i8042 KBD port at 0x60,0x64 irq 1
[    0.973205] serio: i8042 AUX port at 0x60,0x64 irq 12
[    0.975178] rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
[    0.975282] rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
[    0.977262] i2c /dev entries driver
[    0.978717] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
[    0.980300] md: linear personality registered for level -1
[    0.980480] md: raid0 personality registered for level 0
[    0.980655] md: raid1 personality registered for level 1
[    0.980828] md: raid10 personality registered for level 10
[    0.981001] md: raid6 personality registered for level 6
[    0.981181] md: raid5 personality registered for level 5
[    0.981353] md: raid4 personality registered for level 4
[    0.981691] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: dm-devel@redhat.com
[    0.981870] cpuidle: using governor ladder
[    0.982046] cpuidle: using governor menu
[    0.982233] EFI Variables Facility v0.08 2004-May-17
[    0.982508] TCP cubic registered
[    0.982694] NET: Registered protocol family 17
[    0.982879] Registering the dns_resolver key type
[    0.987209] rtc_cmos 00:04: setting system clock to 2014-05-12 21:00:14 UTC (1399928414)
[    1.127784] ata1.00: ATA-4: VMware Virtual IDE Hard Drive, 00000001, max UDMA/33
[    1.128706] ata1.00: 32000 sectors, multi 16: LBA 
[    1.132051] ata1.00: configured for UDMA/33
[    1.132233] ata1.00: Find SSD disks. [VMware Virtual IDE Hard Drive]
[    1.132602] scsi 0:0:0:0: Direct-Access     VMware   Virtual IDE Hard Drive   0000 PQ: 0 ANSI: 5
[    1.133210] sd 0:0:0:0: [sda] 32000 512-byte logical blocks: (16.3 MB/15.6 MiB)
[    1.133405] sd 0:0:0:0: [sda] Write Protect is off
[    1.133598] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    1.133799] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    1.137058]  sda:
[    1.137349] sd 0:0:0:0: [sda] Attached SCSI disk
[    1.140193] Freeing unused kernel memory: 27196k freed
[    1.143410] Write protecting the kernel read-only data: 8192k
[    1.146243] Freeing unused kernel memory: 1896k freed
[    1.147654] Freeing unused kernel memory: 736k freed
[    1.190623] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    1.199660] mpt2sas version 13.100.00.00 loaded
[    1.204418] megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006)
[    1.207944] megaraid: 2.20.5.1 (Release Date: Thu Nov 16 15:32:35 EST 2006)
[    1.212088] megasas: 00.00.06.12-rc1 Wed. Oct. 5 17:00:00 PDT 2011
[    1.219539] e100: Unknown symbol mii_ethtool_sset (err 0)
[    1.219995] e100: Unknown symbol mii_link_ok (err 0)
[    1.220847] e100: Unknown symbol mii_check_link (err 0)
[    1.221285] e100: Unknown symbol mii_nway_restart (err 0)
[    1.221508] e100: Unknown symbol generic_mii_ioctl (err 0)
[    1.221728] e100: Unknown symbol mii_ethtool_gset (err 0)
[    1.224612] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
[    1.225020] e1000: Copyright (c) 1999-2006 Intel Corporation.
[    1.225321] e1000 0000:02:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[    1.225570] e1000 0000:02:00.0: setting latency timer to 64
[    1.555251] e1000 0000:02:00.0: eth0: (PCI:66MHz:32-bit) xxxxxxxxxxxxxxx
[    1.555811] e1000 0000:02:00.0: eth0: Intel(R) PRO/1000 Network Connection
[    1.560375] e1000e: Intel(R) PRO/1000 Network Driver - 1.5.1-k
[    1.560776] e1000e: Copyright(c) 1999 - 2011 Intel Corporation.
[    1.563928] VMware PVSCSI driver - version 1.0.1.0-k
[    1.564415] vmw_pvscsi 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[    1.564752] vmw_pvscsi: using 64bit dma
[    1.566165] vmw_pvscsi 0000:03:00.0: setting latency timer to 64
[    1.566928] vmw_pvscsi 0000:03:00.0: irq 72 for MSI/MSI-X
[    1.567178] vmw_pvscsi: using MSI-X
[    1.567437] scsi2 : VMware PVSCSI storage adapter rev 2, req/cmp/msg rings: 8/8/1 pages, cmd_per_lun=64
[    1.567758] vmw_pvscsi 0000:03:00.0: VMware PVSCSI rev 2 host #2
[    1.568122] scsi 2:0:0:0: Direct-Access     VMware   Virtual disk             1.0  PQ: 0 ANSI: 2
[    1.569326] sd 2:0:0:0: [sdc] 16777216 512-byte logical blocks: (8.58 GB/8.00 GiB)
[    1.569593] sd 2:0:0:0: [sdc] Write Protect is off
[    1.569830] sd 2:0:0:0: [sdc] Mode Sense: 31 00 00 00
[    1.570082] sd 2:0:0:0: [sdc] Cache data unavailable
[    1.570312] sd 2:0:0:0: [sdc] Assuming drive cache: write through
[    1.571227] sd 2:0:0:0: [sdc] Cache data unavailable
[    1.571469] sd 2:0:0:0: [sdc] Assuming drive cache: write through
[    1.571762] sd 2:0:0:0: Attached scsi generic sg1 type 0
[    1.575051]  sdc: sdc1 sdc2 sdc3 < sdc5 >
[    1.579229] sd 2:0:0:0: [sdc] Cache data unavailable
[    1.579907] sd 2:0:0:0: [sdc] Assuming drive cache: write through
[    1.580129] sd 2:0:0:0: [sdc] Attached SCSI disk
[    1.588295] VMware vmxnet3 virtual NIC driver - version 1.1.29.0-k-NAPI
[    1.617605] mpt2sas version 13.100.00.00 unloading
[    1.624811] mpt2sas version 13.100.00.00 loaded
[    1.630726] md: Autodetecting RAID arrays.
[    1.632895] md: invalid raid superblock magic on sdc5
[    1.633249] md: sdc5 does not have a valid v0.90 superblock, not importing!
[    1.633610] md: Scanned 3 and added 2 devices.
[    1.633983] md: autorun ...
[    1.635871] md: considering sdc1 ...
[    1.636085] md:  adding sdc1 ...
[    1.636298] md: sdc2 has different UUID to sdc1
[    1.636506] md: created md0
[    1.636706] md: bind
[    1.636910] md: running: 
[    1.637158] bio: create slab  at 1
[    1.637403] md/raid1:md0: active with 1 out of 12 mirrors
[    1.637614] md0: detected capacity change from 0 to 2549940224
[    1.637868] md: considering sdc2 ...
[    1.638060] md:  adding sdc2 ...
[    1.638590] md: created md1
[    1.638780] md: bind
[    1.638962] md: running: 
[    1.640024] md/raid1:md1: active with 1 out of 12 mirrors
[    1.640231] md1: detected capacity change from 0 to 2147418112
[    1.640535] md: ... autorun DONE.
[    1.641900]  md1: unknown partition table
[    1.653565] bromolow_synobios: module license 'Synology Inc.' taints kernel.
[    1.653723] Disabling lock debugging due to kernel taint
[    1.674517] synobios: load, major number 201
[    1.675087] Brand: Synology
[    1.675269] Model: DS-3612xs
[    1.675439] set group disks wakeup number to 4, spinup time deno 7
[    2.175631] synobios cpu_arch proc entry initialized
[    2.186269] synobios: unload
[    2.199543]  md0: unknown partition table
[    2.201229] EXT4-fs (md0): barriers disabled
[    2.281087] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 23696
[    2.281727] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 23691
[    2.281909] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5003
[    2.282076] EXT4-fs (md0): 3 orphan inodes deleted
[    2.282235] EXT4-fs (md0): recovery complete
[    2.283170] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: 
[    2.904921] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: barrier=1
[    2.978466] EXT4-fs (md0): re-mounted. Opts: (null)
[    3.478998] Adding 2097084k swap on /dev/md1.  Priority:-1 extents:1 across:2097084k 
[    3.579887] zram: module is from the staging directory, the quality is unknown, you have been warned.
[    3.581692] zram: Created 2 device(s) ...
[    3.585165] Adding 307196k swap on /dev/zram0.  Priority:1 extents:1 across:307196k SS
[    3.588005] Adding 307196k swap on /dev/zram1.  Priority:1 extents:1 across:307196k SS
[    3.643738] NET: Registered protocol family 10
[    3.669299] usbcore: registered new interface driver usbfs
[    3.670473] usbcore: registered new interface driver hub
[    3.671015] usbcore: registered new interface driver ethub
[    3.672279] usbcore: registered new device driver usb
[    3.807442] fuse init (API version 7.22)
[    3.811530] dca service started, version 1.12.1
[    3.819638] Intel(R) Gigabit Ethernet Network Driver - version 3.2.10-k
[    3.820225] Copyright (c) 2007-2011 Intel Corporation.
[    3.829430] ixgbe: Unknown symbol mdio_mii_ioctl (err 0)
[    3.830085] ixgbe: Unknown symbol mdio45_probe (err 0)
[    3.857666] bio: create slab  at 2
[    3.858385] Btrfs loaded
[    3.872101] synobios: load, major number 201
[    3.872723] Brand: Synology
[    3.872903] Model: DS-3612xs
[    3.873080] set group disks wakeup number to 4, spinup time deno 7
[    4.373795] synobios cpu_arch proc entry initialized
[    4.531991] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
[    4.532680] ADDRCONF(NETDEV_UP): eth0: link is not ready
[    4.534102] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    5.568211] md: md2 stopped.
[    5.574282] md: bind
[    5.574757] md/raid1:md2: active with 1 out of 1 mirrors
[    5.574937] md2: detected capacity change from 0 to 3741384704
[    5.576869]  md2: unknown partition table
[    5.827925] EXT4-fs (dm-0): barriers disabled
[    5.839266] EXT4-fs (dm-0): recovery complete
[    5.840739] EXT4-fs (dm-0): mounted filesystem with writeback data mode. Opts: usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,synoacl,data=writeback,oldalloc
[    5.933657] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    5.938433] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    5.956827] uhci_hcd: USB Universal Host Controller Interface driver
[    5.963539] Initializing USB Mass Storage driver...
[    5.964194] usbcore: registered new interface driver usb-storage
[    5.964385] USB Mass Storage support registered.
[    5.969320] usbcore: registered new interface driver usblp
[    5.983016] usbcore: registered new interface driver usbhid
[    5.983711] usbhid: USB HID core driver
[    6.072705] __SYNOCaselessStat(600) orig name:[/volume1/test] len:[13]
[    6.074152] __SYNOCaselessStat(616) convert name:[/volume1/test]
[    7.282752] netlink: 12 bytes leftover after parsing attributes.
[    9.770733] loop: module loaded
[   11.815195] findhostd uses obsolete (PF_INET,SOCK_PACKET)
[   11.938035] ata1.00: configured for UDMA/33
[   11.938584] ata1: EH complete
[   15.014002] eth0: no IPv6 routers present
[   16.739972] synobios_ioctl: SYNOIO_RTC_TIME_WRITE
[   16.741382] (0h, 1e) (1h, 0) (2h, 15) (3h, 1) (4h, c) (5h, 4) (6h, 72)
[   41.769406] dm request get [md2], push down wakeup no work
[   41.770657] wake up [sdc5]
[   41.773368] Sync page end [sdc] 

Link to comment
Share on other sites

The only thing is that nanoboot uses pattern file from Diskstation RS3411RPxs.Why? Can someone alter this to 3612xs?

 

Where'd you get that info? I used a 3612xs .PAT file to install on my test VM.

 

edit: I think I figured out your problem after downloading your ISO. It doesn't have the kernel commandline configs, specifically the one that identifies it as 3612xs.

Link to comment
Share on other sites

I have to find that the nanoboot can't correct detach NIC R8111 driver of r8168. How to make nanoboot detach nic change tor r8168?

 

DiskStation> ethtool -i eth0

driver: r8169

version: 2.3LK-NAPI

firmware-version: N/A

bus-info: 0000:03:00.0

 

Please reference gnoboot- alpha10 blog...

http://www.gnoboot.me/2014/03/gnoboot-alpha10.html

 

also I try add "rmmod=r8169_new" on boot menu, but no luck.

 

I hope your nanoboot be a great and perfect bootloader!!! thank you so much!

Link to comment
Share on other sites

I have to find that the nanoboot can't correct detach NIC R8111 driver of r8168. How to make nanoboot detach nic change tor r8168?

 

DiskStation> ethtool -i eth0

driver: r8169

version: 2.3LK-NAPI

firmware-version: N/A

bus-info: 0000:03:00.0

 

Please reference gnoboot- alpha10 blog...

http://www.gnoboot.me/2014/03/gnoboot-alpha10.html

 

also I try add "rmmod=r8169_new" on boot menu, but no luck.

 

I hope your nanoboot be a great and perfect bootloader!!! thank you so much!

 

I'm pretty sure rmmod doesn't work in nanoboot. He said it should work, but it doesn't. I been using gnoboot since the beginning, so I'm 99.99% sure that I'm not doing something wrong and that it is broken.

Link to comment
Share on other sites

I'm pretty sure rmmod doesn't work in nanoboot. He said it should work, but it doesn't. I been using gnoboot since the beginning, so I'm 99.99% sure that I'm not doing something wrong and that it is broken.

 

It's my fault, I put ata_piix compiled into the kernel, and not as a module, so "rmmod=ata_piix" does not work.

I will fix this problem in the next version, thanks for your feedback.

Link to comment
Share on other sites

I'm pretty sure rmmod doesn't work in nanoboot. He said it should work, but it doesn't. I been using gnoboot since the beginning, so I'm 99.99% sure that I'm not doing something wrong and that it is broken.

 

It's my fault, I put ata_piix compiled into the kernel, and not as a module, so "rmmod=ata_piix" does not work.

I will fix this problem in the next version, thanks for your feedback.

 

oic! how about r8168 nic driver? it also compiled into the kernel or not?

Link to comment
Share on other sites

I'm pretty sure rmmod doesn't work in nanoboot. He said it should work, but it doesn't. I been using gnoboot since the beginning, so I'm 99.99% sure that I'm not doing something wrong and that it is broken.

 

It's my fault, I put ata_piix compiled into the kernel, and not as a module, so "rmmod=ata_piix" does not work.

I will fix this problem in the next version, thanks for your feedback.

 

No problem, I'm happy to test and give feedback. Thanks for confirming issue, and finding the cause :smile:

Link to comment
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.

×
×
  • Create New...