All of lore.kernel.org
 help / color / mirror / Atom feed
* WD nas broke can't accessmy files on RAID 1
@ 2017-10-21 10:46 Francesco Tomadin
  2017-10-21 11:25 ` Anthony Youngman
  0 siblings, 1 reply; 7+ messages in thread
From: Francesco Tomadin @ 2017-10-21 10:46 UTC (permalink / raw)
  To: linux-raid

As title says, due to a bug in the WD nas, it started creating
infinite shares folder.
At the moment I can't access my NAS anymore, so I decided to try
ubuntu to recover my data.
I tried to follow some guides and to check stuff but seems like
(especially for my NAS) stuff like this doesn't exist.
I don't even wanna try to do stuff on my own since as you can clearly
see I'm not a linux user I don't even understand what's going on.

PS: My nas had 4 slot, one of them was in JBOD format, and with ubuntu
I could easily access the data without problem.

Tried to use some mdadm command but It gave me some "strange" errors
which I would ever try to "fix" on my own.
Tried to give a last chance to my nas yesterday but it's stuck at boot.
Please if someone could really help me task to task because I really
really don't know what to do anymore.

Sorry for my poor english It's not my first language.

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: WD nas broke can't accessmy files on RAID 1
  2017-10-21 10:46 WD nas broke can't accessmy files on RAID 1 Francesco Tomadin
@ 2017-10-21 11:25 ` Anthony Youngman
  2017-10-21 12:22   ` Francesco Tomadin
  0 siblings, 1 reply; 7+ messages in thread
From: Anthony Youngman @ 2017-10-21 11:25 UTC (permalink / raw)
  To: Francesco Tomadin, linux-raid

On 21/10/17 11:46, Francesco Tomadin wrote:
> As title says, due to a bug in the WD nas, it started creating
> infinite shares folder.
> At the moment I can't access my NAS anymore, so I decided to try
> ubuntu to recover my data.
> I tried to follow some guides and to check stuff but seems like
> (especially for my NAS) stuff like this doesn't exist.
> I don't even wanna try to do stuff on my own since as you can clearly
> see I'm not a linux user I don't even understand what's going on.
> 
> PS: My nas had 4 slot, one of them was in JBOD format, and with ubuntu
> I could easily access the data without problem.
> 
> Tried to use some mdadm command but It gave me some "strange" errors
> which I would ever try to "fix" on my own.
> Tried to give a last chance to my nas yesterday but it's stuck at boot.
> Please if someone could really help me task to task because I really
> really don't know what to do anymore.

Have you read the raid wiki? Is there any chance you could run the 
--detail and --examine commands? (Yes I get you may have problem finding 
the disks to be able to run the commands on them! :-)

https://raid.wiki.kernel.org/index.php/Linux_Raid

You might have to take the disks out of the NAS, or force the whole 
thing into JBOD mode, but again if it won't boot, that might not be 
possible ...
> 
> Sorry for my poor english It's not my first language.

Better than my foreign languages! If you can't express yourself clearly 
in English, then post bi-lingual. I'm guessing your first language is 
Spanish or Italian, which I don't understand, but there are probably 
people who do. But you need to use as much English as possible to get 
the best help.

Cheers,
Wol

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: WD nas broke can't accessmy files on RAID 1
  2017-10-21 11:25 ` Anthony Youngman
@ 2017-10-21 12:22   ` Francesco Tomadin
  2017-10-21 13:17     ` Francesco Tomadin
  0 siblings, 1 reply; 7+ messages in thread
From: Francesco Tomadin @ 2017-10-21 12:22 UTC (permalink / raw)
  To: Anthony Youngman; +Cc: linux-raid

Thanks for the reply!
First of all, I'll try to express myself in the best way I can :) (I'm
actually impressed that you realized my main language)

As you said, the nas won't boot up, it's stuck from yesterday. I'll
probably have to plug out the electricity since it doesn't work at
all. At the moment when I try to log in in the control panel it says
is performing file system consistency check. I'm not even sure if
unplugging right now will make the things even worse.

When you ask me to run those commands, to be honest I wouldn't even
know where to start, from what I tried to do in the last 2 days, I was
only able to see the disk partitions, and nothing more.


2017-10-21 13:25 GMT+02:00 Anthony Youngman <antmbox@youngman.org.uk>:
> On 21/10/17 11:46, Francesco Tomadin wrote:
>>
>> As title says, due to a bug in the WD nas, it started creating
>> infinite shares folder.
>> At the moment I can't access my NAS anymore, so I decided to try
>> ubuntu to recover my data.
>> I tried to follow some guides and to check stuff but seems like
>> (especially for my NAS) stuff like this doesn't exist.
>> I don't even wanna try to do stuff on my own since as you can clearly
>> see I'm not a linux user I don't even understand what's going on.
>>
>> PS: My nas had 4 slot, one of them was in JBOD format, and with ubuntu
>> I could easily access the data without problem.
>>
>> Tried to use some mdadm command but It gave me some "strange" errors
>> which I would ever try to "fix" on my own.
>> Tried to give a last chance to my nas yesterday but it's stuck at boot.
>> Please if someone could really help me task to task because I really
>> really don't know what to do anymore.
>
>
> Have you read the raid wiki? Is there any chance you could run the --detail
> and --examine commands? (Yes I get you may have problem finding the disks to
> be able to run the commands on them! :-)
>
> https://raid.wiki.kernel.org/index.php/Linux_Raid
>
> You might have to take the disks out of the NAS, or force the whole thing
> into JBOD mode, but again if it won't boot, that might not be possible ...
>>
>>
>> Sorry for my poor english It's not my first language.
>
>
> Better than my foreign languages! If you can't express yourself clearly in
> English, then post bi-lingual. I'm guessing your first language is Spanish
> or Italian, which I don't understand, but there are probably people who do.
> But you need to use as much English as possible to get the best help.
>
> Cheers,
> Wol

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: WD nas broke can't accessmy files on RAID 1
  2017-10-21 12:22   ` Francesco Tomadin
@ 2017-10-21 13:17     ` Francesco Tomadin
  2017-10-21 14:17       ` Anthony Youngman
  0 siblings, 1 reply; 7+ messages in thread
From: Francesco Tomadin @ 2017-10-21 13:17 UTC (permalink / raw)
  To: Anthony Youngman; +Cc: linux-raid

Okay with some troubles, I managed to understand something.
What I did after installing mbadm is using the command sudo fdisk -l
After that i got a bunch of data, but I guess this is what I needed to know.

Disk /dev/sdc: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
Disklabel type: gpt
Disk identifier: 560070A2-CB61-4416-BC11-E4F7C2E28388

Device          Start        End    Sectors  Size Type
/dev/sdc1        2048    4196351    4194304    2G Linux swap
/dev/sdc2     6293504 7811938303 7805644800  3.7T Microsoft basic data
/dev/sdc3  7811938304 7814037134    2098831    1G Microsoft basic data
/dev/sdc4     4196352    6293503    2097152    1G Microsoft basic data


After this I tried to run --examine:

ubuntu@ubuntu:~$ sudo mdadm --examine /dev/sdc
/dev/sdc:
   MBR Magic : aa55
Partition[0] :   4294967295 sectors at            1 (type ee)


ubuntu@ubuntu:~$ sudo mdadm --examine /dev/sdc1
/dev/sdc1:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 2da381ee:0105a2ee:40130e04:e0c90235
  Creation Time : Fri Oct 20 16:57:14 2017
     Raid Level : raid1
  Used Dev Size : 2097088 (2048.28 MiB 2147.42 MB)
     Array Size : 2097088 (2048.28 MiB 2147.42 MB)
   Raid Devices : 4
  Total Devices : 3
Preferred Minor : 0

    Update Time : Fri Oct 20 16:57:32 2017
          State : clean
Internal Bitmap : present
 Active Devices : 3
Working Devices : 3
 Failed Devices : 1
  Spare Devices : 0
       Checksum : aca4dbd2 - correct
         Events : 6


      Number   Major   Minor   RaidDevice State
this     1       8       33        1      active sync   /dev/sdc1

   0     0       8       17        0      active sync
   1     1       8       33        1      active sync   /dev/sdc1
   2     2       8        1        2      active sync   /dev/sda1
   3     3       0        0        3      faulty removed


ubuntu@ubuntu:~$ sudo mdadm --examine /dev/sdc2
/dev/sdc2:
          Magic : a92b4efc
        Version : 1.0
    Feature Map : 0x1
     Array UUID : 4bc3cfef:db0ae9ef:2bceeae9:ac2bbee2
           Name : 1
  Creation Time : Mon Nov  7 13:04:44 2016
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 7805644528 (3722.02 GiB 3996.49 GB)
     Array Size : 3902822264 (3722.02 GiB 3996.49 GB)
   Super Offset : 7805644784 sectors
   Unused Space : before=0 sectors, after=256 sectors
          State : clean
    Device UUID : d23ca413:64d7dec5:d938d9d6:b11d2d26

Internal Bitmap : 2 sectors from superblock
    Update Time : Fri Oct 20 08:43:02 2017
       Checksum : 5124c394 - correct
         Events : 3


   Device Role : Active device 1
   Array State : AA ('A' == active, '.' == missing, 'R' == replacing)

ubuntu@ubuntu:~$ sudo mdadm --examine /dev/sdc3
mdadm: No md superblock detected on /dev/sdc3.
ubuntu@ubuntu:~$ sudo mdadm --examine /dev/sdc4
mdadm: No md superblock detected on /dev/sdc4.
ubuntu@ubuntu:~$

2017-10-21 12:22 GMT+00:00 Francesco Tomadin <inamaru94@gmail.com>:
> Thanks for the reply!
> First of all, I'll try to express myself in the best way I can :) (I'm
> actually impressed that you realized my main language)
>
> As you said, the nas won't boot up, it's stuck from yesterday. I'll
> probably have to plug out the electricity since it doesn't work at
> all. At the moment when I try to log in in the control panel it says
> is performing file system consistency check. I'm not even sure if
> unplugging right now will make the things even worse.
>
> When you ask me to run those commands, to be honest I wouldn't even
> know where to start, from what I tried to do in the last 2 days, I was
> only able to see the disk partitions, and nothing more.
>
>
> 2017-10-21 13:25 GMT+02:00 Anthony Youngman <antmbox@youngman.org.uk>:
>> On 21/10/17 11:46, Francesco Tomadin wrote:
>>>
>>> As title says, due to a bug in the WD nas, it started creating
>>> infinite shares folder.
>>> At the moment I can't access my NAS anymore, so I decided to try
>>> ubuntu to recover my data.
>>> I tried to follow some guides and to check stuff but seems like
>>> (especially for my NAS) stuff like this doesn't exist.
>>> I don't even wanna try to do stuff on my own since as you can clearly
>>> see I'm not a linux user I don't even understand what's going on.
>>>
>>> PS: My nas had 4 slot, one of them was in JBOD format, and with ubuntu
>>> I could easily access the data without problem.
>>>
>>> Tried to use some mdadm command but It gave me some "strange" errors
>>> which I would ever try to "fix" on my own.
>>> Tried to give a last chance to my nas yesterday but it's stuck at boot.
>>> Please if someone could really help me task to task because I really
>>> really don't know what to do anymore.
>>
>>
>> Have you read the raid wiki? Is there any chance you could run the --detail
>> and --examine commands? (Yes I get you may have problem finding the disks to
>> be able to run the commands on them! :-)
>>
>> https://raid.wiki.kernel.org/index.php/Linux_Raid
>>
>> You might have to take the disks out of the NAS, or force the whole thing
>> into JBOD mode, but again if it won't boot, that might not be possible ...
>>>
>>>
>>> Sorry for my poor english It's not my first language.
>>
>>
>> Better than my foreign languages! If you can't express yourself clearly in
>> English, then post bi-lingual. I'm guessing your first language is Spanish
>> or Italian, which I don't understand, but there are probably people who do.
>> But you need to use as much English as possible to get the best help.
>>
>> Cheers,
>> Wol

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: WD nas broke can't accessmy files on RAID 1
  2017-10-21 13:17     ` Francesco Tomadin
@ 2017-10-21 14:17       ` Anthony Youngman
       [not found]         ` <CAKNaYNugRX-kRZOLdE57gFnPyuLgDtVMbPp5qk_2CzZdUJqW4g@mail.gmail.com>
  0 siblings, 1 reply; 7+ messages in thread
From: Anthony Youngman @ 2017-10-21 14:17 UTC (permalink / raw)
  To: Francesco Tomadin; +Cc: linux-raid

On 21/10/17 14:17, Francesco Tomadin wrote:
> Okay with some troubles, I managed to understand something.
> What I did after installing mbadm is using the command sudo fdisk -l
> After that i got a bunch of data, but I guess this is what I needed to know.
> 
It's getting me a little confused too - I tend to be a "first responder" 
and pick up the easy stuff, complicated stuff waits for people who've 
done far more digging than I have :-)

This actually looks like it'll be a dead easy recovery, but there's too 
many little "gotchas" for me to want to do more than explain what's 
happened, and let someone else fix it.

> Disk /dev/sdc: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 4096 bytes
> I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
> Disklabel type: gpt
> Disk identifier: 560070A2-CB61-4416-BC11-E4F7C2E28388
> 
> Device          Start        End    Sectors  Size Type
> /dev/sdc1        2048    4196351    4194304    2G Linux swap
> /dev/sdc2     6293504 7811938303 7805644800  3.7T Microsoft basic data
> /dev/sdc3  7811938304 7814037134    2098831    1G Microsoft basic data
> /dev/sdc4     4196352    6293503    2097152    1G Microsoft basic data
> 
Okay. Does this mean your NAS had four 4TB drives in it?

You said one drive was in JBOD mode. Did you set it up this way, or is 
this how it ended up after the failure? It looks to me as though this 
drive failed, was kicked out of the array, and that's why you can access 
it in JBOD. Any chance of you running "smartctl -x" on it? I strongly 
suspect that will come back with "SCT/ERC not supported" :-( If it does 
that's great news for recovering your array, but maybe bad news for your 
wallet :-)
> 
> After this I tried to run --examine:
> 
> ubuntu@ubuntu:~$ sudo mdadm --examine /dev/sdc
> /dev/sdc:
>     MBR Magic : aa55
> Partition[0] :   4294967295 sectors at            1 (type ee)
> 
> 
> ubuntu@ubuntu:~$ sudo mdadm --examine /dev/sdc1
> /dev/sdc1:
>            Magic : a92b4efc
>          Version : 0.90.00
>             UUID : 2da381ee:0105a2ee:40130e04:e0c90235
>    Creation Time : Fri Oct 20 16:57:14 2017
>       Raid Level : raid1
>    Used Dev Size : 2097088 (2048.28 MiB 2147.42 MB)
>       Array Size : 2097088 (2048.28 MiB 2147.42 MB)
>     Raid Devices : 4
>    Total Devices : 3
> Preferred Minor : 0
> 
>      Update Time : Fri Oct 20 16:57:32 2017
>            State : clean
> Internal Bitmap : present
>   Active Devices : 3
> Working Devices : 3
>   Failed Devices : 1
>    Spare Devices : 0
>         Checksum : aca4dbd2 - correct
>           Events : 6
> 
> 
>        Number   Major   Minor   RaidDevice State
> this     1       8       33        1      active sync   /dev/sdc1
> 
>     0     0       8       17        0      active sync
>     1     1       8       33        1      active sync   /dev/sdc1
>     2     2       8        1        2      active sync   /dev/sda1
>     3     3       0        0        3      faulty removed
> 
> 
> ubuntu@ubuntu:~$ sudo mdadm --examine /dev/sdc2
> /dev/sdc2:
>            Magic : a92b4efc
>          Version : 1.0
>      Feature Map : 0x1
>       Array UUID : 4bc3cfef:db0ae9ef:2bceeae9:ac2bbee2
>             Name : 1
>    Creation Time : Mon Nov  7 13:04:44 2016
>       Raid Level : raid1
>     Raid Devices : 2
> 
>   Avail Dev Size : 7805644528 (3722.02 GiB 3996.49 GB)
>       Array Size : 3902822264 (3722.02 GiB 3996.49 GB)
>     Super Offset : 7805644784 sectors
>     Unused Space : before=0 sectors, after=256 sectors
>            State : clean
>      Device UUID : d23ca413:64d7dec5:d938d9d6:b11d2d26
> 
> Internal Bitmap : 2 sectors from superblock
>      Update Time : Fri Oct 20 08:43:02 2017
>         Checksum : 5124c394 - correct
>           Events : 3
> 
> 
>     Device Role : Active device 1
>     Array State : AA ('A' == active, '.' == missing, 'R' == replacing)
> 
Okay. I'm puzzled. sdc1, the "linux swap" array, is clearly broken. 
Hopefully, this is what's causing the whole thing to fall over, because 
if we lose the contents of that we couldn't care less.

sdc2, which I'm guessing is your data, looks healthy. Get the NAS 
working properly, and that will just come straight back.

As I say, try and get a "smartctl -x", but at this point I'll bow out 
and let somebody who knows more than I do take over. But it does look 
VERY promising.

Cheers,
Wol


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: WD nas broke can't accessmy files on RAID 1
       [not found]         ` <CAKNaYNugRX-kRZOLdE57gFnPyuLgDtVMbPp5qk_2CzZdUJqW4g@mail.gmail.com>
@ 2017-10-21 15:43           ` Francesco Tomadin
  2017-10-21 16:11             ` Anthony Youngman
  0 siblings, 1 reply; 7+ messages in thread
From: Francesco Tomadin @ 2017-10-21 15:43 UTC (permalink / raw)
  To: Anthony Youngman; +Cc: linux-raid

Thanks to a guy on IRC after some check he told me to use

mdadm --assemble --scan
and IT worked! I can access again my drive!

Thanks for everythiing!

2017-10-21 14:38 GMT+00:00 Francesco Tomadin <inamaru94@gmail.com>:
>> Okay. Does this mean your NAS had four 4TB drives in it?
>>
>> You said one drive was in JBOD mode. Did you set it up this way, or is this
>> how it ended up after the failure? It looks to me as though this drive
>> failed, was kicked out of the array, and that's why you can access it in
>> JBOD. Any chance of you running "smartctl -x" on it? I strongly suspect that
>> will come back with "SCT/ERC not supported" :-( If it does that's great news
>> for recovering your array, but maybe bad news for your wallet :-)
>
> What you're seeing right now is one of the disk that were in RAID 1,
> with the jbod disk it's a different story, I just had to plug and play
> on linux and I could recover my data easily.
>
>> Okay. I'm puzzled. sdc1, the "linux swap" array, is clearly broken.
>> Hopefully, this is what's causing the whole thing to fall over, because if
>> we lose the contents of that we couldn't care less.
>>
>> sdc2, which I'm guessing is your data, looks healthy. Get the NAS working
>> properly, and that will just come straight back.
>>
>
> I would if I could but trust me I CAN'T! The nas just got a bug who
> made the cpu working like crazy and creating infinite folder, I could
> access that 2 days ago, but not anymore! it's just stuck! That's why I
> hoped I could mount the drive if someway.
>
>> As I say, try and get a "smartctl -x", but at this point I'll bow out and
>> let somebody who knows more than I do take over. But it does look VERY
>> promising.
>>
>
> Thanks a lot for trying! And thanks for your kind words :D
> I'll wait an answer from someone else.

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: WD nas broke can't accessmy files on RAID 1
  2017-10-21 15:43           ` Francesco Tomadin
@ 2017-10-21 16:11             ` Anthony Youngman
  0 siblings, 0 replies; 7+ messages in thread
From: Anthony Youngman @ 2017-10-21 16:11 UTC (permalink / raw)
  To: Francesco Tomadin; +Cc: linux-raid

On 21/10/17 16:43, Francesco Tomadin wrote:
> Thanks to a guy on IRC after some check he told me to use
> 
> mdadm --assemble --scan
> and IT worked! I can access again my drive!
> 
> Thanks for everythiing!

Do still do that "smartctl -x"! If your NAS dos have the wrong sort of 
drives in it, this is just going to happen again ... If it comes back 
and says SCT/ERC *is* supported, then your disks are good and you're fine.

Cheers,
Wol

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2017-10-21 16:11 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-10-21 10:46 WD nas broke can't accessmy files on RAID 1 Francesco Tomadin
2017-10-21 11:25 ` Anthony Youngman
2017-10-21 12:22   ` Francesco Tomadin
2017-10-21 13:17     ` Francesco Tomadin
2017-10-21 14:17       ` Anthony Youngman
     [not found]         ` <CAKNaYNugRX-kRZOLdE57gFnPyuLgDtVMbPp5qk_2CzZdUJqW4g@mail.gmail.com>
2017-10-21 15:43           ` Francesco Tomadin
2017-10-21 16:11             ` Anthony Youngman

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.