plugout.net

@ Jocko @fvdw

Hi guys, after updating the kernel (after reboot) the 5bigN2 isn't available anymore via ssh nor ip address... :dontknow

Maybe there is an issue with this last kernel version.

You can try to load an external kernel by using fvdw-sl console (be careful not the action "load a standalone kernel")

So after starting fvdw-sl console et choosing the action "load an external kernel", select the kernel 3.14.2 in the browse tree window in the subfolder 'kirkwood'

if you can connect to the NAS then that means that there is an issue with the kernel

ok, I need to set this up on my "specific" local network again so I'll have to test it tomorrow...
I'll keep you guys updated :z)

Jocko wrote:Maybe there is an issue with this last kernel version.

You can try to load an external kernel by using fvdw-sl console (be careful not the action "load a standalone kernel")

So after starting fvdw-sl console et choosing the action "load an external kernel", select the kernel 3.14.2 in the browse tree window in the subfolder 'kirkwood'

if you can connect to the NAS then that means that there is an issue with the kernel

no good news here...I can't load external kernel (it doesn't start after booting up while waiting for U-Boot) and the assistant doesn't find my NAS...does this mean I need to re-do the firmware install all over again?

--edit-- for info the NAS is seen from the network by its hostname; running a "netstat" command it appears as "Lacie5Big.local link#7 UHLWI 0 3 en0"

If you have edited your host file, please try again after removing the line added for Lacie5big.

Seems you have trouble with every action you do ;)
One question are there any usb disk connected when you load the kernel? If yes remove them and try again. Maybe the automount of hfs+ causes an issue.

And no you don't have to do install of the firmware again, unless you have written the new kernel to the wrong partition. With the standalone kernel we can restore the previous kernel

I tested the kernel on my 5big2 and it runs fine, so you must be doing something wrong (did you extract the kernel from the zip archive I have sent you ?, so did not use directly the zip archive itself.)

ok got it! :woohoo

Wasn't connected to the network port 1 which is the only one enabled after the kernel install... :hammerhead

Very tired so my apologies for this...

I now have the NAS up and running with access to the external usb drive so a massive thank you to all 3 of you guys, you're truly amazing and extremely knowledgable!!! :hail

I'm well happy to be part of this forum!

Surely speak soon :-D

macdalor wrote:Wasn't connected to the network port 1 which is the only one enabled after the kernel install...

Previously i noted you enabled bonding feature (from nas-central.org). So this should not happen.

Can you confirm that bonding feature is disabled and if yes try to enable to check what happens.

Can you also post the the output of dmesg command?

Jocko wrote:

macdalor wrote:Wasn't connected to the network port 1 which is the only one enabled after the kernel install...

Previously i noted you enabled bonding feature (from nas-central.org). So this should not happen.

Can you confirm that bonding feature is disabled and if yes try to enable to check what happens.

Can you also post the the output of dmesg command?

I will run this command this evening when back home.

Funny you say that because I saw it disabled after the kernel update and I tried to enable it last night but it seems to take a awfully long time to save changes; it even hangs there...Maybe it's just me and my bad luck but I feel that in general the web interface isn't so fast responding to commands since the update...Maybe @fvdw can confirm it runs well on his side?