Dashboard opens with blank only

[fariaslcfs]

Correct

So, @fvdw, is the previous listing ok?

[fariaslcfs]

Sorry I did not notice your previous message.

Please to note I do not know what login must be used with the telnet server of Lacie firmware.

Besides, I also don't know what is expected to be done after the actions suggested by @mijzelf.
Just leave the Lacie server boot normally, and then try to connect with telnet terminal?

[Jocko]

Currently your steps performed from fvdw-sl console may allow to run a telnet server on the Lacie OS after rebooting it.

Later I assume mijzelf idea is to try to mount md4 from the lacie OS. So you will need to login on the telnet server. so need to know what login you have to use ? (for example your admin account of the lacie dashboard)

Anyhow I think it is a bad new xfs_repair fails to detect no superblock

[Mijzelf]

The login is no problem. The telnet daemon is started in 'loginless mode', so you directly get a shell.

Later I assume mijzelf idea is to try to mount md4 from the lacie OS.

Anyhow I think it is a bad new xfs_repair fails to detect no superblock

I vaguely remember there was something with xfs and Lacie. So I hope there is some incompatibility between 'Lacie xfs' and mainline xfs, and that the filesystem will 'just mount', when booted in Lacie firmware.

[fariaslcfs]

Currently your steps performed from fvdw-sl console may allow to run a telnet server on the Lacie OS after rebooting it.
Later I assume mijzelf idea is to try to mount md4 from the lacie OS. So you will need to login on the telnet server. so need to know what login you have to use ? (for example your admin account of the lacie dashboard)
Anyhow I think it is a bad new xfs_repair fails to detect no superblock

I can try one admin account of mine.
P.S. : thanks @mijzelf for the clue.
Regarding the listing presented before, I am not confident if all steps there are ok or necessary. Could you guys give me a hint?

I vaguely remember there was something with xfs and Lacie. So I hope there is some incompatibility between 'Lacie xfs' and mainline xfs, and that the filesystem will 'just mount', when booted in Lacie firmware.

The boot of Lacie firmware has some kind of problem which does not present a functional dashboard on the browser, but a blank frame instead. That's the visible malfunction. It is not clear if the firmware is malfunctioning as well to other tasks such as raid mounting.

[Jocko]

Hi Mijzelf

I vaguely remember there was something with xfs and Lacie. So I hope there is some incompatibility between 'Lacie xfs' and mainline xfs, and that the filesystem will 'just mount', when booted in Lacie firmware.

I hope but previously some users succeeded to repair a lacie xfs from fvdw-sl console

[Mijzelf]

Regarding the listing presented before, I am not confident if all steps there are ok or necessary. Could you guys give me a hint?

Step 6 is not right. You should omit the '-t xfs'. The filesystem is ext2 or ext3.

I vaguely remember there was something with xfs and Lacie. So I hope there is some incompatibility between 'Lacie xfs' and mainline xfs, and that the filesystem will 'just mount', when booted in Lacie firmware.

The boot of Lacie firmware has some kind of problem which does not present a functional dashboard on the browser, but a blank frame instead. That's the visible malfunction. It is not clear if the firmware is malfunctioning as well to other tasks such as raid mounting.

Sure. It is possible that the array is not mounted. But the malfunctioning of the webinterface doesn't have to do anything with the data partition.

Hi Mijzelf

I vaguely remember there was something with xfs and Lacie. So I hope there is some incompatibility between 'Lacie xfs' and mainline xfs, and that the filesystem will 'just mount', when booted in Lacie firmware.

I hope but previously some users succeeded to repair a lacie xfs from fvdw-sl console

OK. I admit that my rationale is not bulletproof.

[fariaslcfs]

Updated listing after @Mijzelf revision (#6) + initng* :

1. using standalone kernel version 3.9.5; run the fvdw-sl-programs to upload mini glibc and tools;
   

   Code: Select all

   cd /
tftp -r fvdw-sl-programs.sh -l fvdw-sl-programs.sh -g ip-pc
chmod 755 fvdw-sl-programs.sh
/fvdw-sl-programs.sh

2. load and use udevstart.sh;
   

   Code: Select all

   cd /sbin
tftp -r udevstart.sh -l udevstart.sh -g ip-pc
chmod 755 udevstart.sh
udevstart.sh
ls -l /dev/sd*

3. assemble md4;
   

   Code: Select all

   gdisk -l /dev/sdd
mdadm --assemble --run /dev/md4 /dev/sd[abcde]2
cat /proc/mdstat

4. try to mount md4;
   

   Code: Select all

   cd /
mkdir /md4
/usr/sbin/mount -t xfs /dev/md4 /md4

5. assemble the raid array md8:
   

   Code: Select all

   mdadm --assemble /dev/md8 /dev/sd[abcde]8

6. try to mound md8;
   

   Code: Select all

   mkdir /md8
/usr/sbin/mount /dev/md8 /md8

7. Add a file telnetd.i to /md8/etc/initng/ with the content:
   

   Code: Select all

   #!/sbin/itype
daemon telnetd {
   need = virtual/net;
   exec daemon = /usr/sbin/telnetd -l /bin/sh ;
   forks;
   daemon_stops_badly;
}

8. add a line 'telnetd' to /md8/etc/initng/runlevel/default.runlevel:
   

   Code: Select all

   echo telnetd >> /md8/etc/initng/runlevel/default.runlevel

Unfortunately, my workplace will be closed tomorrow, so see you next monday.
Anyway, I'd like to express my gratitude to @fvdw, @Jocko and @Mijzelf for all your precious orientations given so far.

* @Mijzelf named a path as 'initng', and then @fvdw observed that the correct name is 'initg'. However, I realized that, in fact, @Mijzelf is correct: after doing a listing in the /md8/etc subdirectory, 'initng' was found (unless a new directory 'initg' must be created; anyway, I'll be usign 'initng' directory for now).

[fariaslcfs]

md8 mounting of the previous listing #6 was executed successfully.
The listing of /md8 directory is shown below.
Now, items #7 and #8 of the list will be executed.

Code: Select all

root@(fvdw-kirkwood):/md8 # ls -lh
total 4580
-rw-rw-r--    1 root     root      690.3K Nov  3  2010 System.map
drwxr-xr-x    2 root     root        4.0K Nov  3  2010 bin
drwxr-xr-x    2 root     root        4.0K Nov  3  2010 boot
drwxrwxr-x    2 root     root        4.0K Nov  3  2010 dev
drwxr-xr-x   27 root     root        4.0K Jan  1 00:00 etc
drwxr-xr-x    2 root     100         4.0K Nov  3  2010 home
drwxr-xr-x    3 root     root        4.0K Nov  3  2010 lacie
drwxr-xr-x    7 root     root        4.0K Nov  3  2010 lib
drwx------    2 root     root       16.0K Feb  5  2011 lost+found
drwxr-xr-x    2 root     root        4.0K Nov  3  2010 media
drwxr-xr-x    2 root     root        4.0K Nov  3  2010 mnt
drwxr-xr-x    2 root     root        4.0K Nov  3  2010 opt
drwxr-xr-x    2 root     root        4.0K Nov  3  2010 proc
drwxr-x---    2 root     root        4.0K Oct 16  2014 root
drwxr-xr-x    2 root     root        4.0K Nov  3  2010 sbin
drwxr-xr-x    2 root     root        4.0K Nov  3  2010 share
drwxr-xr-x    2 root     root        4.0K Nov  3  2010 sys
drwxrwxrwt    2 root     root        4.0K Nov  3  2010 tmp
-rw-rw-r--    1 root     root        1.8M Nov  3  2010 uImage
drwxr-xr-x   14 root     root        4.0K Nov  3  2010 usr
drwxr-xr-x   15 root     root        4.0K Nov  3  2010 var
drwxr-xr-x    6 root     root        4.0K Nov  3  2010 www
-rwxrwxr-x    1 root     root        1.8M Nov  3  2010 zImage


[fariaslcfs]

Just executed items #7 and #8.
What shall I do now? Just boot Lacie normally and then try a telnet session?