Dashboard opens with blank only

[fariaslcfs]

Please, can anybody help me? After a reset my dashboard opens in the browser but only shows a blank frame. I used nmap to scan the Lacie (all ports 0-65535) but only ports 80 and 443 are open. No other ports are open. The boot process occurs normally according to the frontal led indication.

[fvdw]

Which firmware lacie or fvdw-sl?
I assume you use lacie.
The fact that port 80 is open indicates a webserver is running
What happens if you connect with a browser to the ip of your device? (http://ip-adres) replace ip-adres by real ip of your device

[fariaslcfs]

Thanks for replying. I still am using Lacie firmware. Only a blank frame appears. The http server is running but no links are presented in the interface. As I said, the boot procedure occurs normally, but as a result of a port scan ranging the whole "ports space (0-65535)" only ports 80 and 443 are shown open. In fact, the server responds in either ports (http or https). I also checked all the 5 HDs individually and externally with mdadm and the result was normal.

[fvdw]

well it seems some files are corrupt of the lacie firmware. I believe there is a factory reset procedure available, see the manual and it should preseve your data stored on the device although it is moved to a new folder rwith name recovery

from the manual

For the 5big Network 2, there are two methods for resetting your LaCie NAS to factory conditions. Both will erase the default Dashboard data such as users, groups, machine name, etc. However, the first method, Reset Without Data Loss, will not delete files stored to the NAS, and the second, Reset With Data Loss, will. The second method constitutes a complete restoration to the out-of-box state.

Note that neither Reset Without Data Loss nor Reset With Data Loss will affect attached external hard drives.
Reset Without Data Loss


Caution: Following these steps will erase all Dashboard data such as users, groups, shares, and settings. It will also reset the machine name to the default and reset the network settings to DHCP.




Caution: After following these steps, all files will be moved to a folder called Recovery in Share and so by default will be available only to the administrator.


Make sure the product is turned OFF.
Press and hold down the front button. Without releasing the front button, turn the product on by pressing the power switch on the rear of the product.
Keep the front button pressed until the front LED becomes solid red, then release it. (The LED should become solid red about 10 seconds after you turn on the product.)
The front LED will blink blue. When it becomes static blue, press the front button once within 5 seconds to confirm reset.
If any of the steps are omitted, the product will boot normally without resetting.

source: http://manuals.lacie.com/en/manuals/d2-2big-5big-network2/

[fariaslcfs]

Thanks a lot friend!
However, I already tried the factory reset without data loss but found a problem: there is no red light.
Even so, I did the factory reset actions, assuming that no light = red light (maybe a burned led).
However, nothing apparently changed after the procedure.

[fariaslcfs]

So, what else can I do assuming factory reset process is apparently not working? Is there other access procedure?

[fvdw]

As it is lacie firmware I have limited knowledge. In principle there is no other way to access the lacie firmware if all ports except http are dead and the webserver does,t function.
Of course a full reset is possible but that will erase all your data maybe you want to save your data.
An option for that is using our fvdw-sl console and load our standalone kernel that runs from ram and try to repair the lacie firmware and/or assemble the raid array and copy your data before reinstall. There are some topics in this forums describing it, it is a somewhat difficult process

[fariaslcfs]

Thanks.

[fariaslcfs]

Hi, me again.

I finally get inside Lacie 5big with fvdw-sl tools.
There is a very favourable scenario: all 5 hds are apparently healthy.

Following the instruction of this post, everything goes fine until we try:

Code: Select all

/usr/sbin/mount /dev/md4 /md4


which returns "Function not implemented".

This is the last barrier to reach the folders that need to be backuped.

Could you please give some advice on how to tackle this issue? Thanks!

P. S. : additional information on md4 and sd[abcde]2 below.

Code: Select all

 root@fvdw-sta-kirkwood:/ # 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/4] [UUUU_]
      [>....................]  recovery =  4.3% (84283776/1951372672) finish=1221.2min speed=25480K/sec


Code: Select all

root@fvdw-sta-kirkwood:/ # mdadm -D /dev/md4
/dev/md4:
        Version : 1.2
  Creation Time : Thu Jan  1 01:15:34 1970
     Raid Level : raid5
     Array Size : 7805490688 (7443.90 GiB 7992.82 GB)
  Used Dev Size : 1951372672 (1860.97 GiB 1998.21 GB)
   Raid Devices : 5
  Total Devices : 5
    Persistence : Superblock is persistent

    Update Time : Thu Jan  1 00:26:29 1970
          State : clean, degraded, recovering
 Active Devices : 4
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 1

         Layout : left-symmetric
     Chunk Size : 64K

 Rebuild Status : 4% complete

           Name : fvdw-sta-kirkwood:0  (local to host fvdw-sta-kirkwood)
           UUID : 1126e27a:134ee56d:e944b67e:ecaecaf8
         Events : 15

    Number   Major   Minor   RaidDevice State
       0       8       34        0      active sync   /dev/sda2
       1       8       18        1      active sync   /dev/sdb2
       2       8        2        2      active sync   /dev/sdc2
       3       8       66        3      active sync   /dev/sdd2
       5       8       50        4      spare rebuilding   /dev/sde2

root@fvdw-sta-kirkwood:/ # mdadm -E /dev/sd[abcde]2
/dev/sda2:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 1126e27a:134ee56d:e944b67e:ecaecaf8
           Name : fvdw-sta-kirkwood:0  (local to host fvdw-sta-kirkwood)
  Creation Time : Thu Jan  1 01:15:34 1970
     Raid Level : raid5
   Raid Devices : 5

 Avail Dev Size : 3902745671 (1860.97 GiB 1998.21 GB)
     Array Size : 7805490688 (7443.90 GiB 7992.82 GB)
  Used Dev Size : 3902745344 (1860.97 GiB 1998.21 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 94935723:bfc0c17e:c48f391a:d758bcee

    Update Time : Thu Jan  1 00:32:17 1970
       Checksum : 40736bf0 - correct
         Events : 16

         Layout : left-symmetric
     Chunk Size : 64K

   Device Role : Active device 0
   Array State : AAAAA ('A' == active, '.' == missing)
/dev/sdb2:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 1126e27a:134ee56d:e944b67e:ecaecaf8
           Name : fvdw-sta-kirkwood:0  (local to host fvdw-sta-kirkwood)
  Creation Time : Thu Jan  1 01:15:34 1970
     Raid Level : raid5
   Raid Devices : 5

 Avail Dev Size : 3902745671 (1860.97 GiB 1998.21 GB)
     Array Size : 7805490688 (7443.90 GiB 7992.82 GB)
  Used Dev Size : 3902745344 (1860.97 GiB 1998.21 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 7d128e42:e5b25516:ab56428e:f59eb05e

    Update Time : Thu Jan  1 00:32:17 1970
       Checksum : db3aea04 - correct
         Events : 16

         Layout : left-symmetric
     Chunk Size : 64K

   Device Role : Active device 1
   Array State : AAAAA ('A' == active, '.' == missing)
/dev/sdc2:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 1126e27a:134ee56d:e944b67e:ecaecaf8
           Name : fvdw-sta-kirkwood:0  (local to host fvdw-sta-kirkwood)
  Creation Time : Thu Jan  1 01:15:34 1970
     Raid Level : raid5
   Raid Devices : 5

 Avail Dev Size : 3902745671 (1860.97 GiB 1998.21 GB)
     Array Size : 7805490688 (7443.90 GiB 7992.82 GB)
  Used Dev Size : 3902745344 (1860.97 GiB 1998.21 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : e901b52e:5597c7c7:b8680c01:e03acc1e

    Update Time : Thu Jan  1 00:32:17 1970
       Checksum : abb96bd9 - correct
         Events : 16

         Layout : left-symmetric
     Chunk Size : 64K

   Device Role : Active device 2
   Array State : AAAAA ('A' == active, '.' == missing)
/dev/sdd2:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 1126e27a:134ee56d:e944b67e:ecaecaf8
           Name : fvdw-sta-kirkwood:0  (local to host fvdw-sta-kirkwood)
  Creation Time : Thu Jan  1 01:15:34 1970
     Raid Level : raid5
   Raid Devices : 5

 Avail Dev Size : 3902745671 (1860.97 GiB 1998.21 GB)
     Array Size : 7805490688 (7443.90 GiB 7992.82 GB)
  Used Dev Size : 3902745344 (1860.97 GiB 1998.21 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 14c9af17:b83b29a5:1d704282:fcb4e94d

    Update Time : Thu Jan  1 00:32:17 1970
       Checksum : 226958ea - correct
         Events : 16

         Layout : left-symmetric
     Chunk Size : 64K

   Device Role : Active device 3
   Array State : AAAAA ('A' == active, '.' == missing)
/dev/sde2:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x2
     Array UUID : 1126e27a:134ee56d:e944b67e:ecaecaf8
           Name : fvdw-sta-kirkwood:0  (local to host fvdw-sta-kirkwood)
  Creation Time : Thu Jan  1 01:15:34 1970
     Raid Level : raid5
   Raid Devices : 5

 Avail Dev Size : 3902745671 (1860.97 GiB 1998.21 GB)
     Array Size : 7805490688 (7443.90 GiB 7992.82 GB)
  Used Dev Size : 3902745344 (1860.97 GiB 1998.21 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
Recovery Offset : 174162120 sectors
          State : clean
    Device UUID : 2e4781e2:ab50d463:591fc7d2:0ae7223c

    Update Time : Thu Jan  1 00:32:17 1970
       Checksum : f5054e0d - correct
         Events : 16

         Layout : left-symmetric
     Chunk Size : 64K

   Device Role : Active device 4
   Array State : AAAAA ('A' == active, '.' == missing)


[fvdw]

Probably the raid array contains an xfs file system, and that may use a different blocksize

Does command

Code: Select all

dmesg

gives some info about md4 after you have given the mount command?

And what is output of this command

Code: Select all

cat /proc/filesystems