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
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.
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
mkdir /sda7
mount /dev/sda7 /sda7
unlink /sda7/lacie-boot/sda1boot
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)Then reboot the nas, you should get the firmware version before your last updating
- Code: Select all
mkdir /sda7
mount /dev/sda7 /sda7
unlink /sda7/lacie-boot/sda1boot
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
Return to Lacie 2Big Network vs2
Users browsing this forum: No registered users and 2 guests