vtrchan

Trial of Nanoboot (4493) - 5.0.3.1

Recommended Posts

Thanks to your guide I have installed a new VM with Nanoboot and original 4482 pat file. :grin: :D

Your tip to delete the vmdk and re-upload when the install does not reboot, did the trick for me!!

 

Thanks mate!

Great, From what i can tell thats due DSM installing it self over the VMDK file. So close to beating my visitor count on my website :smile:

Share this post


Link to post
Share on other sites
Ahh oke!

I understand.

 

I do have another question though.

I now have a 1GB disk that is not initialised.

See screenshot:

https://www.dropbox.com/s/fvl3h92dqbf5w ... .57.20.png

 

Is that correct? Can it be removed?

read the bottom part of my tutorial :smile: it's the VMDK file once again, best bet would be to convert to a read only format but i haven't the time currently.

Share this post


Link to post
Share on other sites
Ahh oke!

I understand.

 

I do have another question though.

I now have a 1GB disk that is not initialised.

See screenshot:

https://www.dropbox.com/s/fvl3h92dqbf5w ... .57.20.png

 

Is that correct? Can it be removed?

read the bottom part of my tutorial :smile: it's the VMDK file once again, best bet would be to convert to a read only format but i haven't the time currently.

 

if you set the vdmk at IDE, and then rmmod=ata_piix it would solve it most likely. Right now removing ata_piix is broken, since it's compiled into the kernel rather than a kernel mod. The creator will fix it next release.

Share this post


Link to post
Share on other sites
Ahh oke!

I understand.

 

I do have another question though.

I now have a 1GB disk that is not initialised.

See screenshot:

https://www.dropbox.com/s/fvl3h92dqbf5w ... .57.20.png

 

Is that correct? Can it be removed?

read the bottom part of my tutorial :smile: it's the VMDK file once again, best bet would be to convert to a read only format but i haven't the time currently.

 

if you set the vdmk at IDE, and then rmmod=ata_piix it would solve it most likely. Right now removing ata_piix is broken, since it's compiled into the kernel rather than a kernel mod. The creator will fix it next release.

 

Yeah i know thanks though, Obviously since it's broke in this realease it seems pointless mentioning that :smile:

Share this post


Link to post
Share on other sites

I have successfully added vid and pid to the boot config. But how can I mount the boot drive back if I want to edit the config file again?

Share this post


Link to post
Share on other sites
Any news on LSI 9211 HBA support?

+1

 

I need this if I upgrade my main system from gnoboot to nanoboot.

Share this post


Link to post
Share on other sites

I'm running into an issue where it looks Nanoboot is not pulling IPs for the NICs. For hardware, i'm using the c2750d4i with marvel NICS coming from DSM5 with gnoboot 10.5a.

 

I get the error below on boot:

 

Running /usr/syno/etc/rc.d/J)3ssdps.sh...

/usr/syno/sbin/minissdpd

Usage: /usr/syno/sbin/minissdpd [-d] [-6] [-s socket] -[p pidfile] -i [-i ] ...

 

< interface> is eitehr an IPv4 address such as 192.168.1.42, or an

interface name such as eth0.

 

By defaulth, socket will be open as /var/run/minissdpd.sock

and pid written to file /var/run/minissdpd.pid

start SSDPD failed.

 

From the guide off cyanlabs, the execution line should be:

/usr/syno/sbin/minissdpd -i eth0 -i eth1

 

Any insight would be appreciated. Thanks in advanced.

Share this post


Link to post
Share on other sites
I'm running into an issue where it looks Nanoboot is not pulling IPs for the NICs. For hardware, i'm using the c2750d4i with marvel NICS coming from DSM5 with gnoboot 10.5a.

 

I get the error below on boot:

 

Running /usr/syno/etc/rc.d/J)3ssdps.sh...

/usr/syno/sbin/minissdpd

Usage: /usr/syno/sbin/minissdpd [-d] [-6] [-s socket] -[p pidfile] -i [-i ] ...

 

< interface> is eitehr an IPv4 address such as 192.168.1.42, or an

interface name such as eth0.

 

By defaulth, socket will be open as /var/run/minissdpd.sock

and pid written to file /var/run/minissdpd.pid

start SSDPD failed.

 

From the guide off cyanlabs, the execution line should be:

/usr/syno/sbin/minissdpd -i eth0 -i eth1

 

Any insight would be appreciated. Thanks in advanced.

it probably doesn't have drivers for that NIC, also what do you mean by "From the guide off cyanlabs, the execution line should be: /usr/syno/sbin/minissdpd -i eth0 -i eth1"?

Share this post


Link to post
Share on other sites
it probably doesn't have drivers for that NIC, also what do you mean by "From the guide off cyanlabs, the execution line should be: /usr/syno/sbin/minissdpd -i eth0 -i eth1"?

 

Ah, driver issue. i suspected that.

 

As for the your guide, the same line listed -i eth0 and -i eth1 in the screenshot so I wasn't sure why I was getting the same thing. You do great work. I followed you guide before to get 4458 up. Fantastic stuff!

 

Thank you to F5BJR for the PM with the 4482 repack.

Share this post


Link to post
Share on other sites
I'm running into an issue where it looks Nanoboot is not pulling IPs for the NICs. For hardware, i'm using the c2750d4i with marvel NICS coming from DSM5 with gnoboot 10.5a.

 

Intel I210 NICs are likely not supported as they were in other bootloaders. I have the same boards.

Share this post


Link to post
Share on other sites
Intel I210 NICs are likely not supported as they were in other bootloaders. I have the same boards.

 

Right,my mistake. marvel was for the sata controller. I guess i'll have to wait for the driver for the Intel I210 to get added.

Share this post


Link to post
Share on other sites

I have a problem shutting down with Nanoboot. The console shows:

 

umount root

can't umount /: device or resource busy

umount fail, killall again

 

It shows this five times then reboots. I login via the GUI and shutdown again. The unit then stays off.

Share this post


Link to post
Share on other sites

umount root

can't umount /: device or resource busy

umount fail, killall again

 

This part is normal. It keeps retrying until successful.

 

The rebooting on shutdowns I'm not sure the reason for, but I'm not really using nanoboot yet until rmmod=ata_piix is fixed. And lsi 9211-8i support works.

Share this post


Link to post
Share on other sites

Gents,

 

gnoboot had a problem where the drive temperatures didn't display properly when running through ESX-i (I wasn't the only one to spot this).

 

Is this an issue on Nanoboot too?

 

Thanks in advance

Share this post


Link to post
Share on other sites
Dear

 

Anyone had the open tools for DSM5?

I got one but fail to start at 4482...

 

Thanks!

: >

 

Do you mean the Open VM Tools?

If so I do have them working on my ESXi 5.5 box.

Download this SPK file: https://drive.google.com/file/d/0B5r1mh ... V4LTQ/edit

Install manually in Package Center.

 

Thanks to gnoBoot for the Open VM Tools.

 

[update]

The Open VM Tools do work but my ESXi vSphere client cannot see the IP address.

https://www.dropbox.com/s/1uoo9kewgr18y ... .26.25.png

Edited by Guest

Share this post


Link to post
Share on other sites
I have successfully added vid and pid to the boot config. But how can I mount the boot drive back if I want to edit the config file again?

Why it's useful to change those values​​? :?:

 

*edit*

Ok, I found it by myself... if you put VID & PID of your boot device, you can hide it inside DSM... useful to not erase your boot device.

 

@666

If think you can remove VID & PID in the debug menu option, so if you want to see your boot device inside DSM you must boot in debug mode.

 

Thanks!

ema

Share this post


Link to post
Share on other sites

Update from Gnoboot 10.5 on Hyper-V VM yesterday evening without any issues. Works like a charm now with 4482 update.

Thanks Nanoboot :cool:

Share this post


Link to post
Share on other sites

Just download Nanoboot 5.0.2.1 test run on Asus J1800I-C mainboard with Celeron 2.4Ghz. Install DSM5.0-4482 work fine only USB3.0 not working.

 

Thanks Nanoboot.

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

This is awesome. Crossgrade / upgrade from gnoboot 10.5 4458 to Nanoboot 4482 under ESXi worked like a charm.

 

Did the Gnoboot -> nanoboot upgrade preserve your shares?

Yes. Afaict everything's ok. Just had to un-/reinstall vmtools.

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.