plugout.net

Hi

after a power blackout i restart the system but is not possible
the login by admin user and so is not possible access to the folder
under mac os.
i dont receive any error from login only connection failed

what can i check ???

Thanks

Hi,

Did you try to start again the nas, sometimes the nas failed to get get an IP lease from the DHCP server of your router for example after a power outage where the router rebooting is not complete when the firmware tries to get it.

Jocko wrote:Hi,

Did you try to start again the nas, sometimes the nas failed to get get an IP lease from the DHCP server of your router for example after a power outage where the router rebooting is not complete when the firmware tries to get it.

Hi the ip address setting is static but i try to restart NAS more than one time no result folder is not available when i put inside the login after few seconds replay connection failed.

Is possible check what happen on the nas ?

Hi,

Yes you can via fvdw-sl console.

so open a standalone session on your 2big2 (which is a kirkwood platform), and post

Code: Select all

mkdir /sda7 /sda1 /sda2
mount /dev/sda7 /sda7
mount /dev/sda1 /sda1
mount /dev/sda2 /sda2

cat /sda7/boot.log
ls /sda7/lacie-boot

cat /sda1/boot.log
cat /sda2/boot.log

Jocko wrote:Hi,

Yes you can via fvdw-sl console.

so open a standalone session on your 2big2 (which is a kirkwood platform), and post

Code: Select all

mkdir /sda7 /sda1 /sda2
mount /dev/sda7 /sda7
mount /dev/sda1 /sda1
mount /dev/sda2 /sda2

cat /sda7/boot.log
ls /sda7/lacie-boot

cat /sda1/boot.log
cat /sda2/boot.log

root@Lacie-2-Big.local /$ mount /dev/sda7 /sda7
root@Lacie-2-Big.local /$ mount /dev/sda1 /sda1
root@Lacie-2-Big.local /$ mount /dev/sda2 /sda2
mount: /sda2: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program
, or other error.
start boot log
is a physical machine
detect and set platform
2big2
kirkwood
UIMAGE-414133-KIRKWOOD-1
Current kernel: 4.14.133 #1 PREEMPT Wed Jul 17 14:46:56 CEST 2019
2big2
kirkwood
mount dev/pts
update dev nodes
booting using sda1 file system...
else loop1 finished
rcS finished

ls /sda7/lacie-boot
sda1boot

root@Lacie-2-Big.local /$ cat /sda1/boot.log
start boot log
is a physical machine
detect and set platform
2big2
kirkwood
UIMAGE-414133-KIRKWOOD-1
Current kernel: 4.14.133 #1 PREEMPT Wed Jul 17 14:46:56 CEST 2019
device 2big2
family kirkwood
mount dev/pts
update dev nodes
booting using sda1 root file system...
enable IP forwarding...
run udevstart to update dev nodes when necessary
inserting kernel modules:
modprobe: module 'iscsi_trgt' not found
start buttons control daemon
device = 2big2
source = buttons-nwsp2
buttons-nwsp2 daemon started
root@Lacie-2-Big.local /$ cat /sda2/boot.log
cat: can't open '/sda2/boot.log': No such file or directory

Hi

Indeed the boot script aborts very early on sda1 :scratch . I think the best way is to roll-back on the main partition sda7 and upgrade again the firmware.

So do from a standalone session (I assume you closed the previous one)

Code: Select all

mkdir /sda7
mount /dev/sda7 /sda7
unlink /sda7/lacie-boot/sda1boot

Then reboot the nas, you should get the firmware version before your last updating

Jocko wrote:Hi

Indeed the boot script aborts very early on sda1 :scratch . I think the best way is to roll-back on the main partition sda7 and upgrade again the firmware.

So do from a standalone session (I assume you closed the previous one)

Code: Select all

mkdir /sda7
mount /dev/sda7 /sda7
unlink /sda7/lacie-boot/sda1boot

Then reboot the nas, you should get the firmware version before your last updating

I had execute the command and reinstalled the firmware with success but the system dont recognize until the connectio under any mac os

Hi

So post again

Code: Select all

mkdir /sda7 /sda1 /sda2
mount /dev/sda7 /sda7
mount /dev/sda1 /sda1
mount /dev/sda2 /sda2

cat /sda7/boot.log
ls /sda7/lacie-boot

cat /sda1/boot.log
cat /sda2/boot.log

Jocko wrote:Hi

So post again

Code: Select all

mkdir /sda7 /sda1 /sda2
mount /dev/sda7 /sda7
mount /dev/sda1 /sda1
mount /dev/sda2 /sda2

cat /sda7/boot.log
ls /sda7/lacie-boot

cat /sda1/boot.log
cat /sda2/boot.log

after mount sda1 i receive this message on sda 2
mount: /sda2: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program
, or other error.

root@Lacie-2-Big.local /$ cat /sda7/boot.log
start boot log
is a physical machine
detect and set platform
2big2
kirkwood
UIMAGE-414133-KIRKWOOD-1
Current kernel: 4.14.133 #1 PREEMPT Wed Jul 17 14:46:56 CEST 2019
2big2
kirkwood
mount dev/pts
update dev nodes
booting using sda1 file system...
else loop1 finished
rcS finished

ls /sda7/lacie-boot
sda1boot

ls /sda7/lacie-boot
sda1boot
root@Lacie-2-Big.local /$ cat /sda7/boot.log
start boot log
is a physical machine
detect and set platform
2big2
kirkwood
UIMAGE-414133-KIRKWOOD-1
Current kernel: 4.14.133 #1 PREEMPT Wed Jul 17 14:46:56 CEST 2019
2big2
kirkwood
mount dev/pts
update dev nodes
booting using sda1 file system...
else loop1 finished
rcS finished

ls /sda7/lacie-boot
sda1boot

I need all outputs !