vtrchan

Trial of Nanoboot (4493) - 5.0.3.1

Recommended Posts

for those who have migrated to update 5 , can you enable web station ?

 

i face this "the operation failed. Please log in DSM again and retry" if i want to enable it , put R/O or R/W access to web folder for group http (permission which was gone same as the others i guess) does not help)

 

webstation was not enabled before the update so not sure if there is a relation

 

also , i would like to downgrade , my only path is return to PAT stock so 4493 , is anyone knows how i could manually update to update 4 ?

 

Thanks,

XT

Share this post


Link to post
Share on other sites
Hi,

But my VM nanoboot still doesn't work in proxmox :sad:

I use proxmox 3.2 and I create my VM like that :

mini_435896proxmoxnanoboot.jpg

I try all nanoboot.img (converted to raw or qcow2) found on the web and as you can see the VM can load the beginning but stop after loading kernel................................

What could be wrong ? Can someone send me a fully functionnal raw or qcow2 image of nanoboot ? ? Please.....

Regards

 

Hi,

some news : I can launch the VM with nanoboot only when the KVM material virtualisation is disabled in proxmox, but then it's extremly slow...

To resume, in proxmox :

- gnoboot works perfectly :grin:

- nanoboot works, but slowly, when the KVM material virtualisation is disabled :cry:

- nanoboot stops booting when the KVM material virtualisation is enabled :mad:

 

So, what's the way to find the solution ? some materials differences between nanoboot and gnoboot ?

I'm going crazy :mrgreen:

Regards

Share this post


Link to post
Share on other sites
for those who have migrated to update 5 , can you enable web station ?

 

i face this "the operation failed. Please log in DSM again and retry" if i want to enable it , put R/O or R/W access to web folder for group http (permission which was gone same as the others i guess) does not help)

 

webstation was not enabled before the update so not sure if there is a relation

 

also , i would like to downgrade , my only path is return to PAT stock so 4493 , is anyone knows how i could manually update to update 4 ?

 

Thanks,

XT

 

EDIT : downgraded successfully to 4493 "update 0" , i could immediatly enable web station , so now any guidance to migrate to update 4 would be appreciate :smile:

Share this post


Link to post
Share on other sites
for those who have migrated to update 5 , can you enable web station ?

 

i face this "the operation failed. Please log in DSM again and retry" if i want to enable it , put R/O or R/W access to web folder for group http (permission which was gone same as the others i guess) does not help)

 

webstation was not enabled before the update so not sure if there is a relation

 

also , i would like to downgrade , my only path is return to PAT stock so 4493 , is anyone knows how i could manually update to update 4 ?

 

Thanks,

XT

 

EDIT : downgraded successfully to 4493 "update 0" , i could immediatly enable web station , so now any guidance to migrate to update 4 would be appreciate :smile:

You can get all of the minor updates from here: http://www.xpenology.nl/xpenology-software/

Just choose the one you want & apply in the normal way.

Share this post


Link to post
Share on other sites

Hi,

 

Could someone give links for NanoBoot-5.0.1.1-fat.img to NanoBoot-5.0.1.4-fat.img (x64) but not with colafile.com (I don't understand chinese language and links seem to be dead)

Regards

Share this post


Link to post
Share on other sites
Hi,

But my VM nanoboot still doesn't work in proxmox :sad:

I use proxmox 3.2 and I create my VM like that :

mini_435896proxmoxnanoboot.jpg

I try all nanoboot.img (converted to raw or qcow2) found on the web and as you can see the VM can load the beginning but stop after loading kernel................................

What could be wrong ? Can someone send me a fully functionnal raw or qcow2 image of nanoboot ? ? Please.....

Regards

 

Hi,

some news : I can launch the VM with nanoboot only when the KVM material virtualisation is disabled in proxmox, but then it's extremly slow...

To resume, in proxmox :

- gnoboot works perfectly :grin:

- nanoboot works, but slowly, when the KVM material virtualisation is disabled :cry:

- nanoboot stops booting when the KVM material virtualisation is enabled :mad:

 

So, what's the way to find the solution ? some materials differences between nanoboot and gnoboot ?

I'm going crazy :mrgreen:

Regards

 

 

I got EXACTLY the same pbs... with proxmox on N54L I guess I tried everything -> disable KVM virtualisation too (same results as yours !

 

I don't know what to do :mad:

Share this post


Link to post
Share on other sites
Hm.. i did a copy the /lib/modules from gnoboot to nanoboot, but the same issue :sad:.. I would like to ha a mixture between gnoboot and nanoboot, or nanoboot with all drivers from gnoboot too..

 

Sent from my CloudMobile using Tapatalk

 

Eventually how i could see what .ko file is for this Synology Remote? Maybe i can try with insmod cmd...

 

hey

sorry for my bad english,

 

i'm in the same configuration, have you find any idee to use your synology remote?

 

thanks for help

Share this post


Link to post
Share on other sites

With gnoboot is Ok.. With nanoboot, at system information i can see the device, but doesnt work :sad:. No ideea why..

 

Sent from my CloudMobile using Tapatalk

Share this post


Link to post
Share on other sites
Hi,

But my VM nanoboot still doesn't work in proxmox :sad:

I use proxmox 3.2 and I create my VM like that :

mini_435896proxmoxnanoboot.jpg

I try all nanoboot.img (converted to raw or qcow2) found on the web and as you can see the VM can load the beginning but stop after loading kernel................................

What could be wrong ? Can someone send me a fully functionnal raw or qcow2 image of nanoboot ? ? Please.....

Regards

 

Hi,

some news : I can launch the VM with nanoboot only when the KVM material virtualisation is disabled in proxmox, but then it's extremly slow...

To resume, in proxmox :

- gnoboot works perfectly :grin:

- nanoboot works, but slowly, when the KVM material virtualisation is disabled :cry:

- nanoboot stops booting when the KVM material virtualisation is enabled :mad:

 

So, what's the way to find the solution ? some materials differences between nanoboot and gnoboot ?

I'm going crazy :mrgreen:

Regards

 

 

I got EXACTLY the same pbs... with proxmox on N54L I guess I tried everything -> disable KVM virtualisation too (same results as yours !

 

I don't know what to do :mad:

 

Hello guys, same problem here, if someone give us tips how to get nanoboot and proxmox working together!

Share this post


Link to post
Share on other sites

Guys,

 

I've tried just about everything but can't seem to get it to work. I am using an old Viao laptop to test, asfter which I will go to a new dedicated board (Asrock).

I have put the 4493 image on a usb stick (downlaoded the correct 4493 pat file from synology i.e. the main, not the update 1-5),

started the laptop,

started synology assistant on a different laptop.

it shows the new Viao Synology (Saio) as migratable.

double clicked it,

go to the web assisstant.

downloaded the 4493 pat file,

uploaded it to the Saio.

system reboots,

 

however it remains in migratable, and can't get past that. any help?

Share this post


Link to post
Share on other sites

hi

I have some troubles with installing dsm 5 with nanoboot

I'm trying to install it on Athlon64 system (s939) with IDE hdd

Synology Assistant gives an error 38 when I give pat file to it, I tried two hdds

dsm 4.3 installed and works ok on this hardware

any ideas?

Share this post


Link to post
Share on other sites

HI. I still need drivers for my N54l display. It seems that only one or two people here be able to modify the boot images. asking for the sources brings no reaction. does anybody have an instruction for inserting driver in nanoboot or explaining the nanoboot structure that we can force development by ourself. regards michael.

Share this post


Link to post
Share on other sites
Hm.. i did a copy the /lib/modules from gnoboot to nanoboot, but the same issue :sad:.. I would like to ha a mixture between gnoboot and nanoboot, or nanoboot with all drivers from gnoboot too..

 

Sent from my CloudMobile using Tapatalk

 

Eventually how i could see what .ko file is for this Synology Remote? Maybe i can try with insmod cmd...

 

hey

sorry for my bad english,

 

i'm in the same configuration, have you find any idee to use your synology remote?

 

thanks for help

 

Ok, with Nanoboot 5.0.3.2 is Ok :smile:.

 

Sent from my CloudMobile using Tapatalk

Share this post


Link to post
Share on other sites
Where did you get Nanoboot 5.0.3.2 ?

 

On first boot, did you use upgrade from older versions (5.0.3.1)?

 

No, i had XPenology set and working with 5.0.3.1 (from SD card), i put 5.0.3.2 on USB stick, i booted from it, and it was OK :smile:.

Share this post


Link to post
Share on other sites

bump.

 

any ideas on the migratable issue which pertains?

 

Guys,

 

I've tried just about everything but can't seem to get it to work. I am using an old Viao laptop to test, asfter which I will go to a new dedicated board (Asrock).

I have put the 4493 image on a usb stick (downlaoded the correct 4493 pat file from synology i.e. the main, not the update 1-5),

started the laptop,

started synology assistant on a different laptop.

it shows the new Viao Synology (Saio) as migratable.

double clicked it,

go to the web assisstant.

downloaded the 4493 pat file,

uploaded it to the Saio.

system reboots,

 

however it remains in migratable, and can't get past that. any help?

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.