Dashboard opens with blank only

[Jocko]

be careful you are not in fvdw-sl console environment and then do not perform the previous commands.

So just

Code: Select all

mount

and also

Code: Select all

which xfs_repair

[fariaslcfs]

be careful you are not in fvdw-sl console environment and then do not perform the previous commands.

So just

Code: Select all

mount

and also

Code: Select all

which xfs_repair

Sorry, didn't know it would be so easy like that...
(Note that I performed the command below previously in this session.)

Code: Select all

[root@(none) /]# mdadm --assemble /dev/md4 /dev/sd[abcde]2

Here comes the result from your instructions:

Code: Select all

[root@(none) /]# mount
rootfs on / type rootfs (rw)
/dev/md0 on /oldroot type ext3 (ro,data=ordered)
none on /oldroot/proc type proc (rw)
none on /oldroot/sys type sysfs (rw)
udev on /oldroot/dev type tmpfs (rw)
devpts on /oldroot/dev/pts type devpts (rw)
none on /oldroot/dev/shm type tmpfs (rw)
/dev/md1 on /oldroot/var/original type ext3 (ro,data=ordered)
/dev/md2 on /oldroot/snapshots type ext3 (rw,data=ordered)
unionfs on / type unionfs (rw,dirs=/oldroot/snapshots/snaps/00=rw:/oldroot/var/original=ro)
sys on /sys type sysfs (rw)
proc on /proc type proc (rw)
/dev/md2 on /var type ext3 (rw,data=ordered)
udev on /dev type tmpfs (rw)
/dev/md2 on /tmp type ext3 (rw,data=ordered)
usbfs on /proc/bus/usb type usbfs (rw)
[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]

unused devices: <none>
[root@(none) /]# which xfs_repair
/usr/sbin/xfs_repair


[Jocko]

Yes you are now on the Lacie environment and indeed it seems Lacie OS fails also to mount /dev/md4.

We go to try to repair the fs on /dev/md4 (which failed with fvdw-sl console). So run

Code: Select all

xfs_repair -v /dev/md4

[fariaslcfs]

Yes you are now on the Lacie environment and indeed it seems Lacie OS fails also to mount /dev/md4.

We go to try to repair the fs on /dev/md4 (which failed with fvdw-sl console). So run

Code: Select all

xfs_repair -v /dev/md4

Just started:

Code: Select all

[root@(none) /]# xfs_repair -v /dev/md4
Phase 1 - find and verify superblock...
bad primary superblock - bad magic number !!!

attempting to find secondary superblock...
.............................................

Now, need to wait hours again and see if that finishes successfully...

[Jocko]

Ok so just need to wait now :?

[fvdw]

:applause

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

Just out of curiosity what was the admin password?

[fariaslcfs]

:applause

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

Just out of curiosity what was the admin password?

The password was LACIE's administrative account one, set by our team, as you suggested here.
(Not "admin" or any other suggested in this forum.)

[fvdw]

Now you are logged in can you post the content of /etc/ passwd and /etc/shadow files
This just to see if they are indeed different from the ones we edited on md8. This might be useful for others users with problems in the future

[fariaslcfs]

Now you are logged in can you post the content of /etc/ passwd and /etc/shadow files
This just to see if they are indeed different from the ones we edited on md8. This might be useful for others users with problems in the future

I'm away from office, but maybe tomorrow.

[fariaslcfs]

Code: Select all

.............................................................Sorry, could not find valid secondary superblock
Exiting now.


About the passwd and shadow files, I found that root and admin have the same <string> (coherent to what was explained here):

Code: Select all

root:<string>:12542:0:99999:7:::
(...)
admin:<string>:12488:0:99999:7:::