plugout.net

Posted: **Sat Jun 20, 2015 1:26 pm**

Dear all,

I'm new - though as obviously for some others a LACIE firmware upgrade went terribly wrong:
- does not boot-up correctly - blue LED keeps on blinking
- cannot connect to the amin page, tells me that the NAS is powering on

Happy when I came across the forum and the console.

My technical knowledge is limited and when it comes to UNIX basically non-existent... This is what I did so far:

Code: Select all: root@fvdw-sta-kirkwood:/ # mdadm --examine /dev/sd[abcde]2 /dev/sda2: Magic : a92b4efc Version : 1.0 Feature Map : 0x0 Array UUID : 30013b20:2c54f06f:414b95ea:3d526820 Name : LaCie-5big:4 Creation Time : Sat Jan 19 12:40:59 2013 Raid Level : raid5 Raid Devices : 4 Avail Dev Size : 3903007536 (1861.10 GiB 1998.34 GB) Array Size : 5854510080 (5583.30 GiB 5995.02 GB) Used Dev Size : 3903006720 (1861.10 GiB 1998.34 GB) Super Offset : 3903007792 sectors State : clean Device UUID : 21a95fb0:fbbd0b7a:ac957c18:46b0341a Update Time : Sat May 23 13:42:53 2015 Checksum : 17c807e - correct Events : 1244753 Layout : left-symmetric Chunk Size : 512K Device Role : Active device 0 Array State : A.AA ('A' == active, '.' == missing) /dev/sdb2: Magic : a92b4efc Version : 1.0 Feature Map : 0x0 Array UUID : 30013b20:2c54f06f:414b95ea:3d526820 Name : LaCie-5big:4 Creation Time : Sat Jan 19 12:40:59 2013 Raid Level : raid5 Raid Devices : 4 Avail Dev Size : 3903007536 (1861.10 GiB 1998.34 GB) Array Size : 5854510080 (5583.30 GiB 5995.02 GB) Used Dev Size : 3903006720 (1861.10 GiB 1998.34 GB) Super Offset : 3903007792 sectors State : clean Device UUID : 3be13552:41ea0f09:f3b1414c:a90dae9f Update Time : Mon Jun 15 20:46:21 2015 Checksum : ebb8d6b7 - correct Events : 1294531 Layout : left-symmetric Chunk Size : 512K Device Role : Active device 1 Array State : .AAA ('A' == active, '.' == missing) /dev/sdc2: Magic : a92b4efc Version : 1.0 Feature Map : 0x0 Array UUID : 30013b20:2c54f06f:414b95ea:3d526820 Name : LaCie-5big:4 Creation Time : Sat Jan 19 12:40:59 2013 Raid Level : raid5 Raid Devices : 4 Avail Dev Size : 3903007536 (1861.10 GiB 1998.34 GB) Array Size : 5854510080 (5583.30 GiB 5995.02 GB) Used Dev Size : 3903006720 (1861.10 GiB 1998.34 GB) Super Offset : 3903007792 sectors State : clean Device UUID : 39588c61:1ef77e05:f3960c70:cd5e8a74 Update Time : Mon Jun 15 20:46:21 2015 Checksum : f02590b7 - correct Events : 1294531 Layout : left-symmetric Chunk Size : 512K Device Role : Active device 2 Array State : .AAA ('A' == active, '.' == missing) /dev/sdd2: Magic : a92b4efc Version : 1.0 Feature Map : 0x0 Array UUID : 30013b20:2c54f06f:414b95ea:3d526820 Name : LaCie-5big:4 Creation Time : Sat Jan 19 12:40:59 2013 Raid Level : raid5 Raid Devices : 4 Avail Dev Size : 3903007536 (1861.10 GiB 1998.34 GB) Array Size : 5854510080 (5583.30 GiB 5995.02 GB) Used Dev Size : 3903006720 (1861.10 GiB 1998.34 GB) Super Offset : 3903007792 sectors State : clean Device UUID : cc0f6ea0:a97d7c4f:1430184f:48fbc7bc Update Time : Mon Jun 15 20:46:21 2015 Checksum : a04e0473 - correct Events : 1294531 Layout : left-symmetric Chunk Size : 512K Device Role : Active device 3 Array State : .AAA ('A' == active, '.' == missing) mdadm: No md superblock detected on /dev/sde2.

Do I guess correctly that when there's written "No md superblock detected on /dev/sde2." this is basically my problem?

Tnx in advance...

Posted: **Sat Jun 20, 2015 3:39 pm**

Jocko and mijzelf are the experts wrt raid. Probably they will react soon. But afaik indeed a missing superblock will make assemble the raid array fail. The question is of course why it lost the superblock, in other words is the disk is ok. Probably yes because it happened after your firmware upgrade. If the disk is ok you could assemble the array without sde2, so in degraded state. An then after that add sde2 as new device.
Maybe the experts have an easier solution.

Posted: **Sun Jun 21, 2015 7:30 pm**

fvdw wrote:Jocko and mijzelf are the experts wrt raid. Probably they will react soon. But afaik indeed a missing superblock will make assemble the raid array fail. The question is of course why it lost the superblock, in other words is the disk is ok. Probably yes because it happened after your firmware upgrade. If the disk is ok you could assemble the array without sde2, so in degraded state. An then after that add sde2 as new device.
Maybe the experts have an easier solution.

Thanks fvdw - how to assemble the arrais without sde2? Is it just...

Code: Select all: mdadm --assemble /dev/md4 /dev/sd[abcd]2

...?

If I do so, I get

Code: Select all: mdadm: ignoring /dev/sda2 as it reports /dev/sdb2 as failed mdadm: /dev/md4 has been started with 3 drives (out of 4).

btw:

Code: Select all: # mdadm --examine /dev/sd[abcde]2 /dev/sda2: Magic : a92b4efc Version : 1.0 Feature Map : 0x0 Array UUID : 30013b20:2c54f06f:414b95ea:3d526820 Name : LaCie-5big:4 Creation Time : Sat Jan 19 12:40:59 2013 Raid Level : raid5 Raid Devices : 4 Avail Dev Size : 3903007536 (1861.10 GiB 1998.34 GB) Array Size : 5854510080 (5583.30 GiB 5995.02 GB) Used Dev Size : 3903006720 (1861.10 GiB 1998.34 GB) Super Offset : 3903007792 sectors State : clean Device UUID : 21a95fb0:fbbd0b7a:ac957c18:46b0341a Update Time : Sat May 23 13:42:53 2015 Checksum : 17c807e - correct Events : 1244753 Layout : left-symmetric Chunk Size : 512K Device Role : Active device 0 Array State : A.AA ('A' == active, '.' == missing) /dev/sdb2: Magic : a92b4efc Version : 1.0 Feature Map : 0x0 Array UUID : 30013b20:2c54f06f:414b95ea:3d526820 Name : LaCie-5big:4 Creation Time : Sat Jan 19 12:40:59 2013 Raid Level : raid5 Raid Devices : 4 Avail Dev Size : 3903007536 (1861.10 GiB 1998.34 GB) Array Size : 5854510080 (5583.30 GiB 5995.02 GB) Used Dev Size : 3903006720 (1861.10 GiB 1998.34 GB) Super Offset : 3903007792 sectors State : clean Device UUID : 3be13552:41ea0f09:f3b1414c:a90dae9f Update Time : Mon Jun 15 20:46:21 2015 Checksum : ebb8d6b7 - correct Events : 1294531 Layout : left-symmetric Chunk Size : 512K Device Role : Active device 1 Array State : .AAA ('A' == active, '.' == missing) /dev/sdc2: Magic : a92b4efc Version : 1.0 Feature Map : 0x0 Array UUID : 30013b20:2c54f06f:414b95ea:3d526820 Name : LaCie-5big:4 Creation Time : Sat Jan 19 12:40:59 2013 Raid Level : raid5 Raid Devices : 4 Avail Dev Size : 3903007536 (1861.10 GiB 1998.34 GB) Array Size : 5854510080 (5583.30 GiB 5995.02 GB) Used Dev Size : 3903006720 (1861.10 GiB 1998.34 GB) Super Offset : 3903007792 sectors State : clean Device UUID : 39588c61:1ef77e05:f3960c70:cd5e8a74 Update Time : Mon Jun 15 20:46:21 2015 Checksum : f02590b7 - correct Events : 1294531 Layout : left-symmetric Chunk Size : 512K Device Role : Active device 2 Array State : .AAA ('A' == active, '.' == missing) /dev/sdd2: Magic : a92b4efc Version : 1.0 Feature Map : 0x0 Array UUID : 30013b20:2c54f06f:414b95ea:3d526820 Name : LaCie-5big:4 Creation Time : Sat Jan 19 12:40:59 2013 Raid Level : raid5 Raid Devices : 4 Avail Dev Size : 3903007536 (1861.10 GiB 1998.34 GB) Array Size : 5854510080 (5583.30 GiB 5995.02 GB) Used Dev Size : 3903006720 (1861.10 GiB 1998.34 GB) Super Offset : 3903007792 sectors State : clean Device UUID : cc0f6ea0:a97d7c4f:1430184f:48fbc7bc Update Time : Mon Jun 15 20:46:21 2015 Checksum : a04e0473 - correct Events : 1294531 Layout : left-symmetric Chunk Size : 512K Device Role : Active device 3 Array State : .AAA ('A' == active, '.' == missing) mdadm: No md superblock detected on /dev/sde2.

Posted: **Sun Jun 21, 2015 10:31 pm**

You gave the correct command to build from 4 disks. If you lookbto the examine output then the array state shows that one device of the four is not active. However when it examines sda it. Mentions sdb2 as not active while when it investigates the others it seemsbit mentions sda as not active. You will need to wait for the comments of the realvraid experts.

Posted: **Mon Jun 22, 2015 7:25 am**

Hi turmeric,

I created a new topic for your issue (to avoid confusion, it is best to open its own topic rather than using an existing topic especially as it is still active!).

About your issue, there is some thing that I don't understand.

From your output, it seems that the raid contained only 4 devices (sd[abcd]2). It is why mdadm can not detect superblock on /dev/sde2.

Otherwise, it seems that sda2 has a fail status.

Can you detail your original configuration ?

Posted: **Mon Jun 22, 2015 1:57 pm**

Hi Jocko,

thank you very much for your help and creating a new thread out of my issue - indeed it makes it much less confusing.

I setup my NAS as a Raid 5 split across 4 disks, the 5th disk left empty as a spare in case of emergncy... as the situation now actually. However, not sure which disk I left empty.

Posted: **Mon Jun 22, 2015 3:57 pm**

turmeric wrote:I setup my NAS as a Raid 5 split across 4 disks, the 5th disk left empty as a spare in case of emergncy...

That confirms that you have only a raid5 with 4 disks and I think sde is the unused disk

Code: Select all: mdadm: No md superblock detected on /dev/sde2.

.

So next step valid it is sda2 the failed disk. After assembling the raid

Code: Select all: mdadm --assemble /dev/md4 /dev/sd[abcd]2

which returns a "miswarning" between sda2 and sdb2 can you post the output of

Code: Select all: mdadm --detail /dev/md4

Posted: **Mon Jun 22, 2015 8:12 pm**

Indeed, there is a strange message that I get...

Code: Select all: mdadm: ignoring /dev/sda2 as it reports /dev/sdb2 as failed mdadm: /dev/md4 has been started with 3 drives (out of 4).

What puzzles me a bit is that disk b is reported as failed...(?)

Code: Select all: /dev/md4: Version : 1.0 Creation Time : Sat Jan 19 12:40:59 2013 Raid Level : raid5 Array Size : 5854510080 (5583.30 GiB 5995.02 GB) Used Dev Size : 1951503360 (1861.10 GiB 1998.34 GB) Raid Devices : 4 Total Devices : 3 Persistence : Superblock is persistent Update Time : Mon Jun 15 20:46:21 2015 State : clean, degraded Active Devices : 3 Working Devices : 3 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 512K Name : LaCie-5big:4 UUID : 30013b20:2c54f06f:414b95ea:3d526820 Events : 1294531 Number Major Minor RaidDevice State 0 0 0 0 removed 1 8 18 1 active sync /dev/sdb2 2 8 2 2 active sync /dev/sdc2 3 8 66 3 active sync /dev/sdd2

Nevertheless, here disk be seems to be running.

Posted: **Tue Jun 23, 2015 11:09 am**

All members keep track of the status of the whole array. According to sda2 that was:

Code: Select all: Array State : A.AA ('A' == active, '.' == missing)

while the other 3 members said

Code: Select all: Array State : .AAA ('A' == active, '.' == missing)

So the democratic majority decided that sda2 no longer can join the array. Mdadm mentions that sda2 voted for sdb2, but that's not the real reason. I guess this message was generated because mdadm at first sight had a conflicting situation. sda2 said that sdb2 was missing, and sdb2 said that sda2 was missing. The conflict was solved by asking sdc2 and sdd2, but the original indistinctness survived in that message.

Posted: **Tue Jun 23, 2015 8:14 pm**

So the democratic majority decided that sda2 no longer can join the array. Mdadm mentions that sda2 voted for sdb2, but that's not the real reason. I guess this message was generated because mdadm at first sight had a conflicting situation. sda2 said that sdb2 was missing, and sdb2 said that sda2 was missing. The conflict was solved by asking sdc2 and sdd2, but the original indistinctness survived in that message.

:applause Thank you Mijzelf - your explanation is also for a newbie here perfectly understandable. And as living in Switzerland, democratic majority is generally acceptable and must be right...

So, I understand then that disk A is 'kaputt', however raid 5 - even though degraded - could be built.

This may sound stupid now: I exactly bought such a device that actually once a disk goes belly up, it would be robust and work nevertheless. Instead, when I run again

mdadm --assemble /dev/md4 /dev/sd[bcd]2

and then, as seen under http://plugout.net/viewtopic.php?f=26&t=1574&start=10

Code: Select all: mkdir /mountpoint mount -o ro /dev/md4 /mountpoint

I get the following output:

Code: Select all: mounting /dev/md4 on /mountpoint failed: Input/output error

Shouldn't this work now?

plugout.net

Issue after upgrading lacie firmware

Issue after upgrading lacie firmware

Re: All Shares Gone - Lacie 5Big Network 2

Re: All Shares Gone - Lacie 5Big Network 2

Re: All Shares Gone - Lacie 5Big Network 2

Re: Issue after upgrading lacie firmware

Re: Issue after upgrading lacie firmware

Re: Issue after upgrading lacie firmware

Re: Issue after upgrading lacie firmware

Re: Issue after upgrading lacie firmware

Re: Issue after upgrading lacie firmware