Dashboard opens with blank only

[fariaslcfs]

And what is reponse if you try to login with user: admin and password: admin

"Access denied"

[fariaslcfs]

Can you try to specify your own command:

Code: Select all

ssh <user>@<ip-address>  /bin/sh -i

I tried to found a way to do that on PuTTY but don't know how.

[Mijzelf]

that must be then coming from partiton 7.

No, partition 9. Partition 7 contains the initial rootfs, partition 8 is the read-only layer of the target rootfs, and partition 9 contains one or more rw layers, which are, laid upon partition 8, chrooted from the system running on partition 7. (Or maybe a switchroot is applied. Can't remember)

[fariaslcfs]

that must be then coming from partiton 7.

No, partition 9. Partition 7 contains the initial rootfs, partition 8 is the read-only layer of the target rootfs, and partition 9 contains one or more rw layers, which are, laid upon partition 8, chrooted from the system running on partition 7. (Or maybe a switchroot is applied. Can't remember)

Mounted partition 9 but its contents are:

Code: Select all

root@(fvdw-kirkwood):/md9 # ls -lh
total 24
drwxr-xr-x    4 root     root        4.0K Jan  1  2000 EDMINI
drwx------    2 root     root       16.0K Jan  1  2000 lost+found
drwxr-xr-x    3 root     root        4.0K Jan  1  2000 snaps


[fariaslcfs]

that must be then coming from partiton 7.
Fausto try to assemble an array from sdx7 and have a look in /md7/etc if there a passwd and shadow file is present, if yes post content please

nope

Code: Select all

root@(fvdw-kirkwood):/ # cd md7
root@(fvdw-kirkwood):/md7 # ls -lh
total 29
drwxr-xr-x    2 root     root        1.0K Nov  3  2010 bin
drwxr-xr-x    2 root     root        1.0K Nov  3  2010 boot
drwxr-xr-x    2 root     root        1.0K Nov  3  2010 dev
drwxr-xr-x    3 root     root        1.0K Nov  3  2010 etc
drwxr-xr-x    3 root     root        1.0K Nov  3  2010 home
drwxr-xr-x    2 root     root        1.0K Nov  3  2010 include
drwxr-xr-x    4 root     root        1.0K Nov  3  2010 lib
drwx------    2 root     root       12.0K Feb  5  2011 lost+found
drwxr-xr-x    2 root     root        1.0K Nov  3  2010 mnt
drwxr-xr-x    2 root     root        1.0K Nov  3  2010 opt
drwxr-xr-x    2 root     root        1.0K Nov  3  2010 proc
drwxr-xr-x    2 root     root        1.0K Nov  3  2010 root
drwxr-xr-x    2 root     root        1.0K Sep  3  2015 sbin
drwxr-xr-x    2 root     root        1.0K Nov  3  2010 snapshots
drwxr-xr-x    2 root     root        1.0K Nov  3  2010 sys
drwxr-xr-x    2 root     root        1.0K Nov  3  2010 tmp
drwxr-xr-x    4 root     root        1.0K Nov  3  2010 usr
drwxr-xr-x    5 root     root        1.0K Nov  3  2010 var
root@(fvdw-kirkwood):/md7 # cd etc
root@(fvdw-kirkwood):/md7/etc # ls -lh
total 3
-rw-r--r--    1 root     root          19 Jun 24  2008 inittab
-rw-r--r--    1 root     root           0 Jun 24  2008 mtab
-rw-r--r--    1 root     root         103 Apr 21  2009 partition.map
drwxr-xr-x    2 root     root        1.0K Nov  3  2010 udev


[fariaslcfs]

And what is reponse if you try to login with user: admin and password: admin
If this gives remote host closed connection then modify in file /md8/etc/ passwd the admin line, replace /bin/false by by /bin/sh
It us curious that user fausto is not mentioned in passwd file as sshd daemon seems to accept that username and passwd. Maybe this old lacie firmware uses a different location for the passwd and shadow file?? :scratch

It gives "Access denied" but, even so, I replaced "false" by "sh".
Booted again, tried login = "admin" and respective password (which is different of "admin" because it was set by me previously when LACIE was healthy), but that gave "Connection closed by remote host"

[Mijzelf]

Can you try to specify your own command:

Code: Select all

ssh <user>@<ip-address>  /bin/sh -i

I tried to found a way to do that on PuTTY but don't know how.

I don't think it can be done in putty. It's done with the command line version of ssh. If it can be done in putty, search for something like 'remote command', which should be '/bin/sh -i'.

that must be then coming from partiton 7.

No, partition 9. Partition 7 contains the initial rootfs, partition 8 is the read-only layer of the target rootfs, and partition 9 contains one or more rw layers, which are, laid upon partition 8, chrooted from the system running on partition 7. (Or maybe a switchroot is applied. Can't remember)

Mounted partition 9 but its contents are:

Code: Select all

root@(fvdw-kirkwood):/md9 # ls -lh
total 24
drwxr-xr-x    4 root     root        4.0K Jan  1  2000 EDMINI
drwx------    2 root     root       16.0K Jan  1  2000 lost+found
drwxr-xr-x    3 root     root        4.0K Jan  1  2000 snaps


The layers are in snaps. It contains one or more directories which contain only mutations on the rootfs on partition 8. So if one of these directories contains a passwd/shadow file, the files on partition 8 are 'invisible' for the running Lacie OS.

[fariaslcfs]

And what is reponse if you try to login with user: admin and password: admin
If this gives remote host closed connection then modify in file /md8/etc/ passwd the admin line, replace /bin/false by by /bin/sh
It us curious that user fausto is not mentioned in passwd file as sshd daemon seems to accept that username and passwd. Maybe this old lacie firmware uses a different location for the passwd and shadow file?? :scratch

It gives "Access denied" but, even so, I replaced "false" by "sh".
Booted again, tried login = "admin" and respective password (which is different of "admin" because it was set by me previously when LACIE was healthy), but that gave "Connection closed by remote host"

GOOD GOOD news!
Tried with "root" and administrator account password (not "admin", as explained above) and succeeded!

Code: Select all

[root@(none) ~]# cd /
[root@(none) /]# ls -lh
-rw-rw-r--    1 root     root       690.3k Nov  3  2010 System.map
drwxr-xr-x    1 root     root         4.0k Nov  3  2010 bin
drwxr-xr-x    1 root     root         4.0k Nov  3  2010 boot
drwxr-xr-x    9 root     root         3.8k Dec 31 22:12 dev
drwxr-xr-x    1 root     root         4.0k Dec 31 22:12 etc
drwxr-xr-x    1 root     users        4.0k Nov  3  2010 home
drwxr-xr-x    1 root     root         4.0k Nov  3  2010 lacie
drwxr-xr-x    1 root     root         4.0k Nov  3  2010 lib
drwx------    1 root     root        16.0k Feb  5  2011 lost+found
drwxr-xr-x    1 root     root         4.0k Nov  3  2010 media
drwxr-xr-x    1 root     root         4.0k Nov  3  2010 mnt
drwxr-xr-x   20 root     root         1.0k Feb  5  2011 oldroot
drwxr-xr-x    1 root     root         4.0k Nov  3  2010 opt
dr-xr-xr-x   67 root     root            0 Dec 31  1969 proc
drwxr-x---    1 root     root         4.0k Oct 16  2014 root
drwxr-xr-x    1 root     root         4.0k Nov  3  2010 sbin
drwxr-xr-x    1 root     root         4.0k Nov  3  2010 share
drwxr-xr-x    1 root     root         4.0k Dec 31 22:02 shares
drwxr-xr-x   11 root     root            0 Dec 31  1969 sys
drwxr-xr-x    4 root     root         4.0k Dec 31 22:12 tmp
-rw-rw-r--    1 root     root         1.8M Nov  3  2010 uImage
drwxr-xr-x    1 root     root         4.0k Nov  3  2010 usr
drwxr-xr-x   15 root     root         4.0k Dec 31 22:00 var
drwxr-xr-x    1 root     root         4.0k Nov  3  2010 www
-rwxrwxr-x    1 root     root         1.8M Nov  3  2010 zImage


[Jocko]

:thumbup
So post

Code: Select all

mount
cat /proc/mdstat

[fariaslcfs]

:thumbup
So post

Code: Select all

mount
cat /proc/mdstat

Like that? (I couldn't mount, don't know where is the command mount)

Code: Select all

[root@(none) /]# mdadm --assemble /dev/md4 /dev/sd[abcde]2
mdadm: /dev/md4 has been started with 5 drives.
[root@(none) /]# mkdir /md4
[root@(none) /]# /usr/sbin/mount /dev/md4 /md4
-sh: /usr/sbin/mount: No such file or directory
[root@(none) /]# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md4 : active raid5 sda2[0] sde2[5] sdd2[3] sdc2[2] sdb2[1]
      7805490688 blocks super 1.2 level 5, 64k chunk, algorithm 2 [5/5] [UUUUU]

md3 : active raid1 sda5[0] sdb5[4] sdc5[3] sdd5[2] sde5[1]
      256896 blocks [5/5] [UUUUU]

md2 : active raid1 sda9[0] sdb9[4] sdc9[3] sdd9[2] sde9[1]
      875392 blocks [5/5] [UUUUU]

md1 : active raid1 sda8[0] sdb8[4] sdc8[3] sdd8[2] sde8[1]
      851328 blocks [5/5] [UUUUU]

md0 : active raid1 sde7[4] sdd7[3] sdc7[2] sdb7[1] sda7[0]
      7936 blocks [5/5] [UUUUU]


Found that just need to call "mount" directly, so did it. However, the syntax is not correct:

Code: Select all

[root@(none) /]# mount /dev/md4 /md4
mount: mounting /dev/md4 on /md4 failed: Invalid argument
[root@(none) /]# mount -help
mount: invalid option -- h
BusyBox v1.10.4 (2010-11-03 11:04:02 UTC) multi-call binary

Usage: mount [flags] DEVICE NODE [-o options,more-options]

Mount a filesystem. Filesystem autodetection requires /proc be mounted.

Options:
        -a              Mount all filesystems in fstab
        -f              Update /etc/mtab, but don't mount
        -n              Don't update /etc/mtab
        -r              Read-only mount
        -t fs-type      Filesystem type
        -w              Read-write mount (default)
-o option:
        loop            Ignored (loop devices are autodetected)
        [a]sync         Writes are asynchronous / synchronous
        [no]atime       Disable / enable updates to inode access times
        [no]diratime    Disable / enable atime updates to directories
        [no]dev         Allow use of special device files / disallow them
        [no]exec        Allow use of executable files / disallow them
        [no]suid        Allow set-user-id-root programs / disallow them
        [r]shared       Convert [recursively] to a shared subtree
        [r]slave        Convert [recursively] to a slave subtree
        [r]private      Convert [recursively] to a private subtree
        [un]bindable    Make mount point [un]able to be bind mounted
        bind            Bind a directory to an additional location
        move            Relocate an existing mount point
        remount         Remount a mounted filesystem, changing its flags
        ro/rw           Mount for read-only / read-write

There are EVEN MORE flags that are specific to each filesystem
You'll have to see the written documentation for those filesystems