Cannot access cloudbox

[riotshield]

After being away from home for 2 weeks, I noticed that transmission server was not working so I restarted cloudbox through the console.

After the restart, the device is not visible on the network and I cannot access it - any ideas on what to check to find out what is wrong. (it was running the latest firmware)

[fvdw]

If the device is not visible in the network then probably boot failed.
What you could do is use the fvdw-sl console and load and start the standalone kernel.
When connected via telnet have a look at the boot logs.
To do that give these commands

Code: Select all

mkdir /sda7
mount /dev/sda7 /sda7
cat /sda7/boot.log

Post the output.
If the output mention using sda1 or sda2 do the same for either sda1 or sda2

[riotshield]

I get this

Code: Select all

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 = cloudbox
source = buttons-cloudbox
buttons-nwsp2 daemon started
Keep old Min free memory=2000
initializing date
Mon Jan  1 12:00:00 EET 2018
configuration partition is rightly mounted
create temporary passwd file
create temporary group file
set samba environment for version 4.x
configure loopback network interface
setting reboot and standby
cloudbox
rebootd-cloudbox
cloudbox
standbyd-cloudbox
starting php based setup routines step 1
 * Initialize the volatile db file...    [ OK ]
 * Starting udevd...                                     [ OK ]
 * Finishing restore RAID devices...     [ OK ]
 * Found database configuration file...  [ OK ]
 * Updating Disks database...                    [ OK ]
 * Starting mount of volumes...
root@fvdw-sta-kirkwood:/ #

[fvdw]

So it stops when trying to mount partitions
Two possibilities
1. Probkem with one of the partitions that must be mounted
2. A corrupt sda1 partition with result that tequired scripts don't run.

Lets first try option 1.
Load and start standlone kernel
To see which partitions can be mounted and which not do this and see if there are errors while mounting

Code: Select all

mkdir /sda5
mkdir sda7
mkdir /sda8
mount /dev/sda5 /sda5
mount /dev/sda7 /sda7
mount /dev/sda8 /sda8


Ps this line in boot.log

Keep old Min free memory=2000

Did you add something in rcS bootscript?

[riotshield]

Spa8 mount failed: Function not implemented

[riotshield]

Ps this line in boot.log

Keep old Min free memory=2000

Did you add something in rcS bootscript?

I am not really sure about this. At some point Jocko suggested to add the following commands due to some strange permission problems with transmission. Could it be related?

Code: Select all

 plugout download 4611
tar -xf /tmp/transmission-2.92patched-30sept16.tar.gz -C /usr/local
unlink /usr/local/share/transmission/update

Code: Select all

sed -rie 's/"umask".*,/"umask": 0,/' /direct-usb/tr-daemon/settings.json

[fvdw]

Spa8 mount failed: Function not implemented

I don't understand what you write ??

[fvdw]

if sda8 cannot be mounted start standalone kernel and run command fvdw-sl-programs
select the option to download mini glibc and tools
After that run this command

Code: Select all

e2fsck -fy /dev/sda8

It is also a good idea to run this command for sda1, sda2, sda5 and sda7
Be sure that the partitions are not mounted when using thsi command. When using standalone kernel in principle no partition is mounted

After running these commands try to mount the partitions as posted earlier

[riotshield]

Spa8 mount failed: Function not implemented

this was more or less the error I got when I tried to mount spa8 (5 and 7 succeeded).

I run the command and these are the results - it appears that spa8 in now mounting

EDIT: I confirm the NAS is now again up and running! Thanks a lot for your help.

Code: Select all

root@fvdw-sta-kirkwood:/ # e2fsck -fy /dev/sda8
e2fsck 1.41.14 (22-Dec-2010)
/dev/sda8: recovering journal
Error reading block 243835370 (Attempt to read block from filesystem resulted in short read).  Ignore error? yes

Force rewrite? yes

Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Unattached inode 92798981
Connect to /lost+found? yes

Inode 92798981 ref count is 2, should be 1.  Fix? yes

Pass 5: Checking group summary information
Block bitmap differences:  -(378459157--378459173) +(378459297--378459313) +378459321 +(378459337--378459338)
Fix? yes

Free blocks count wrong for group #11549 (1637, counted=1634).
Fix? yes

Free blocks count wrong (134594714, counted=134594711).
Fix? yes

/dev/sda8: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda8: 23909/121913344 files (33.9% non-contiguous), 353058426/487653137 blocks
root@fvdw-sta-kirkwood:/ # mkdir /sda8
root@fvdw-sta-kirkwood:/ # mount /dev/sda8 /sda8
root@fvdw-sta-kirkwood:/ #

[fvdw]

Glad to hear that we could solve the problem