Lacie Cloudbox

Re: Lacie Cloudbox

Postby rimoth » Wed Jul 31, 2013 10:51 pm

I am getting this error. Do I need to mount a partition first?
Code: Select all
root@(none):/ # tftp -l /etc/init.d/rcS -r rcS -g 192.168.1.58
tftp: can't open '/etc/init.d/rcS': No such file or directory
rimoth
Donator VIP
Donator VIP
 
Posts: 61
Joined: Mon Jul 08, 2013 9:33 am

Re: Lacie Cloudbox

Postby fvdw » Wed Jul 31, 2013 10:59 pm

yes

indeed , again an error form my side, I am doing to much things at same time :pound

mount sda7 on /sda7 (you need to remake the folder if you have restarted the standalone kernel) and then do this

Code: Select all
tftp -l /sda7/etc/init.d/rcS -r rcS -g 192.168.1.58


and chmod of course also adapted command
Code: Select all
chmod /sda7/etc/init.d/rcS
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Lacie Cloudbox

Postby rimoth » Wed Jul 31, 2013 11:00 pm

Yes I found the file on sda7/etc/init.d/ and replaced it. Rebooting now....
rimoth
Donator VIP
Donator VIP
 
Posts: 61
Joined: Mon Jul 08, 2013 9:33 am

Re: Lacie Cloudbox

Postby rimoth » Wed Jul 31, 2013 11:04 pm

Still not booting to give an ip address on the router. Should I start the tftp and uboot console and load the kernel manually?
rimoth
Donator VIP
Donator VIP
 
Posts: 61
Joined: Mon Jul 08, 2013 9:33 am

Re: Lacie Cloudbox

Postby fvdw » Wed Jul 31, 2013 11:05 pm

mmmm... not nice still something not right
well load the the standalone kernel once more and mount sda7 and do again
Code: Select all
cat /sda7/boot.log

to see if it proceeded in the boot script
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Lacie Cloudbox

Postby rimoth » Wed Jul 31, 2013 11:13 pm

It appears to have proceeded a lot better/further....
Code: Select all
root@(none):/sda7 # cat boot.log
start boot log
booting using  root file system...
make dev node for buttons...
make dev node for tun device...
enable IP forwarding...
do not start buttons control daemon
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...                  [ OK ]
 * Starting udevd...                                     [ OK ]
 * Starting web server...                                [ Fail ]
 * Initializing Timezone...                      [ OK ]
 * Configuring Samba...                                  [ OK ]
 * Starting syncawayd...                                 [ OK ]
start portmap service
starting php based setup routines step 2


 * Starting dropbear...                                  [ OK ]
 * Kill temporary dropbear...                    [ OK ]
 * Starting daemon update Hosts File...  [ OK ]
starting php based setup routines step banner


*** fvdw-sl NAS firmware
    This is fvdw-sl version: fvdw-sl 14.0
    built on: December 23 2012

    LAN IP address: 192.168.1.56 (DHCP)

    Port configuration:

    LAN   -> eth0
php based setup routines finished
web permission on resolv.conf
set device tuning for dms performance
rcS finished
root@(none):/sda7 #


Looks like the webserver just failed to start. I will reboot the nas again and see if I can connect via ssh
rimoth
Donator VIP
Donator VIP
 
Posts: 61
Joined: Mon Jul 08, 2013 9:33 am

Re: Lacie Cloudbox

Postby rimoth » Wed Jul 31, 2013 11:16 pm

Good news. I can ssh into the nas now!!

How to start the webserver next I guess?
rimoth
Donator VIP
Donator VIP
 
Posts: 61
Joined: Mon Jul 08, 2013 9:33 am

Re: Lacie Cloudbox

Postby fvdw » Wed Jul 31, 2013 11:21 pm

yes the webserver failed to start but that can be solved as well. It seems the ssh server (dropbear is running) and it has an ip address so you should be able to connect via ssh (putty), also smaba server is running so you should be able to access the public share as well

One thing we adapted now rcS on sda7. if you install the firmware again by using the web inetrafce it will start to use sda1 or sda2, so to avoid the problem we have seen you must use an adapted firmware for the cloudbox with an adapted rcS file

if you can get access via ssh then put the tar archive I will sent you in the public folder and unpack using the the tar command
Code: Select all
tar -xvf /share/1000/public/httpd-conf-files.tar -C /etc
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Lacie Cloudbox

Postby fvdw » Wed Jul 31, 2013 11:35 pm

pm sent

to reboot use in putty the command
Code: Select all
reboot
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Lacie Cloudbox

Postby rimoth » Wed Jul 31, 2013 11:39 pm

Done what next. Reboot?

ps I am using linux now and not windows so everything is a but easier!
rimoth
Donator VIP
Donator VIP
 
Posts: 61
Joined: Mon Jul 08, 2013 9:33 am

PreviousNext

Return to Lacie cloudbox (white casing)

Who is online

Users browsing this forum: Bing Bot and 11 guests