Lacie Cloudbox

[fvdw]

I noticed another reason why it couldn't find the root files systeem I forgot add it in the command above

change this

Code: Select all

Marvell>> setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/

to this

Code: Select all

Marvell>> setenv bootargs console=ttyS0,115200 root=/dev/sda7 netconsole=6666@${ipaddr}/,6666@${serverip}/

when loading the kernel via tftp and with net console support

but lest first check some things with poking around with the standalone kernel

[fvdw]

when you have the standalone kernel running and are able to mount sda7 on the folder you created (/sda7)
also perform

Code: Select all

cat /sda7/boot.log

If this gives output it means that the kernel has started up the nas...It then also will show if it got an ip address or not

[rimoth]

OK, sda7 can't be mounted....

Code: Select all

root@(none):/ # mkdir /sda7
root@(none):/ # mount /dev/sda7
mount: can't read '/etc/fstab': No such file or directory
root@(none):/ #


Output from cat /proc/partitiions is....

Code: Select all

root@(none):/ # cat /proc/partitions
major minor  #blocks  name

  31        0        500 mtdblock0
  31        1          4 mtdblock1
   8        0 2930266584 sda
   8        1     524288 sda1
   8        2     524288 sda2
   8        3     524288 sda3
   8        4       8192 sda4
   8        5     786432 sda5
   8        6       8192 sda6
   8        7     524288 sda7
   8        8 2927364551 sda8
root@(none):/ #


Let me know if I should try booting with the standalone kernel.

[fvdw]

this command is wrong

Code: Select all

root@(none):/ # mount /dev/sda7

should be

Code: Select all

root@(none):/ # mount /dev/sda7 /sda7

[rimoth]

OK. sda7 mounts fine and I can do a directory listing. I will now try with standalone kernel.

[fvdw]

no wait you are running the standalone kernel

first do

Code: Select all

cat /sda7/boot.log

[rimoth]

Output from boot.log is...

Code: Select all

root@(none):/ # cat /sda7/boot.log
start boot log
booting using  root file system...
make dev node for buttons...
make dev node for tun device...
enable IP forwarding...
start buttons control daemon
buttons-nwsp2 daemon started
initializing date
Wed Nov 16 12:00:00 GMT+1 2011
run udevstart to update dev nodes when necessary
depmod: chdir(3.9.5): No such file or directory
inserting kernel modules:
depmod: chdir(3.9.5): No such file or directory
modprobe: chdir(3.9.5): No such file or directory
modprobe: chdir(3.9.5): No such file or directory
modprobe: chdir(3.9.5): No such file or directory
modprobe: chdir(3.9.5): No such file or directory
modprobe: chdir(3.9.5): No such file or directory
configure loopback netwerk interface
starting php based setup routines step 1



 * Initial XML configuration file...     [ OK ]
 * Configuring Disks...                                  [ OK ]
 * Configuring System Users...
        Root password: use default password
        Set users, linux and samba accounts      [ OK ]
 * Starting mount of volumes...
   - Mounting volume Default:                    [ OK ]
 * Finishing mount of volumes...                 [ OK ]
 * Generating Hosts File...                      [ OK ]
 * Configuring System Hostname...                [ OK ] 
 * Configuring Samba...                                  [ OK ]
 * Configuring LAN interface... ERROR: lacfg_init fail to open file /sys/bus/i2c/devices/0-0050/eeprom
ERROR: lacfg_load_key no map defined
write_byte_storage : error loading key=power
ERROR : writing into the storage
error setting power on
ERROR: lacfg_cleanup no map defined
                 [ OK ]
 * Starting udevd...                                     [ OK ]
 * Starting web server... root@(none):/ #


[fvdw]

so it is booting and starts the boot script, it seems to fail with setting up the lan interface because of missing I2C
so it doesn't get an IP and you can not access it

I will need some time to look at what is going on there...and what nees to be adapted

[fvdw]

think the problem is the buttons daemon that is started. it is designed for the nwsp2 and uses a Lacie binary to access the eeprom to influence the setting of the power button.
It seems that this makes the nas halt as the boot script is not completed

I have sent you by pm an adapted file
unpack the zip file and put the file in the tftp directory
Upload it via tftp to the cloudbox while running the standalone kernel

Code: Select all

tftp -l /etc/init.d/rcS -r rcS -g ip-pc

replace ip-pc by ip of the pc running fvdw-sl console

After uploading it ensure that it is executable

Code: Select all

chmod 755 /etc/init.d/rcS

now try again if it boots by using command in telnet to initiate a reboot

Code: Select all

sync
reboot -f

[fvdw]

pm sent