Dashboard opens with blank only

[Jocko]

I posted here. Is it enough?

not really.

You posted information about raid status (mdstat); your attempt to mount md4 with its error and dmesg output with additional information about mount failure (did not find magic number). it is why I assumed you ran xfs_repair with the option -n.

So do you remember the output of your command

Code: Select all

xfs_repair -nv /dev/md4

. Just to know if without the option '-n' the fs will be really repaired

[fariaslcfs]

I posted here. Is it enough?

So do you remember the output of your command

Code: Select all

xfs_repair -nv /dev/md4

. Just to know if without the option '-n' the fs will be really repaired

Actually, as there was a scheduled blackout in my workplace before the end of the process, the terminal which was monitoring the xfs_repair was shutted off.
(The PC where this terminal was running also has a no-break, but enough only to a few minutes.)
Therefore, I have no idea how the process ended.
The LACIE server has its own no-break, which kept it turned on all the time til the end of the blackout.

Unfortunately, I must leave my workplace in some minutes.
If you have other actions to be tried, feel free to tell me.
Otherwise, we may continue next week.
NOTE: as I said before, a new xfs_repair was initiated today, without the -n option.

[Jocko]

Actually, as there was a scheduled blackout in my workplace before the end of the process, the terminal which was monitoring the xfs_repair was shutted off.

Be careful as soon as you close the terminal xfs_repair command is aborted if it is not running on the background and its process detached of the terminal.

[fariaslcfs]

Actually, as there was a scheduled blackout in my workplace before the end of the process, the terminal which was monitoring the xfs_repair was shutted off.

Be careful as soon as you close the terminal xfs_repair command is aborted if it is not running on the background and its process detached of the terminal.

True! So it worths a new xfs_repair try!
Again unfortunately, somebody just let me know that we'll have another scheduled blackout in some minutes.
This one will be longer, and so the Lacie no-break will not supply all the time.
Therefore, I'm going to turn everything off and start from the beggining next week.

[Jocko]

ok so next step next week !

[fariaslcfs]

NOTE: this post was incomplete and so substituted by this one.

Ok, starting this monday morning with the following operations:
- using standalone kernel version 3.9.5; run the fvdw-sl-programs to upload mini glibc and tools;
- load and use udevstart.sh;
- assemble md4;
- try to mount md4 => unsuccessful;
- run the xfs_repair command with the option -v.
Tomorrow I'll post the result.

[Jocko]

Did you assemble md3 ? xfs_repaitr will require more memory after some actions.

If not you have to open a new telnet window, and run all commands about it (mdadm; mkwsp and swapon) after you can close this window

[fariaslcfs]

Ok, starting this monday afternoon with the following operations:

1. using standalone kernel version 3.9.5; run the fvdw-sl-programs to upload mini glibc and tools;
2. load and use udevstart.sh;
3. assemble md4;
4. try to mount md4 => unsuccessful;
5. assembly and swap md3;
6. run the xfs_repair command with the option -v.

NOTE: I cancelled the previous xfs_repair operation and continued from #5 of the above list.
Tomorrow I'll post the result.

Code: Select all

root@(fvdw-kirkwood):/sbin # mdadm --assemble /dev/md3 /dev/sd[abcde]5
mdadm: /dev/md3 has been started with 5 drives.
root@(fvdw-kirkwood):/sbin # mkswap /dev/md3
Setting up swapspace version 1, size = 263057408 bytes
UUID=de473196-b481-421d-9d39-aea3ec23de36
root@(fvdw-kirkwood):/sbin # swapon /dev/md3
root@(fvdw-kirkwood):/sbin # xfs_repair -v /dev/md4
Phase 1 - find and verify superblock...
bad primary superblock - bad magic number !!!

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

[Jocko]

Ok so cross your fingers !

[fariaslcfs]

Code: Select all

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


What can we do now?