All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco Tomadin <inamaru94@gmail.com>
To: linux-raid@vger.kernel.org
Subject: WD nas broke can't accessmy files on RAID 1
Date: Sat, 21 Oct 2017 12:46:36 +0200	[thread overview]
Message-ID: <CAKNaYNuY8gNn+u4uMK8U+AnnYMmH8GNPDJGWTG1SNrQpDG4kjA@mail.gmail.com> (raw)

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.

             reply	other threads:[~2017-10-21 10:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-21 10:46 Francesco Tomadin [this message]
2017-10-21 11:25 ` WD nas broke can't accessmy files on RAID 1 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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKNaYNuY8gNn+u4uMK8U+AnnYMmH8GNPDJGWTG1SNrQpDG4kjA@mail.gmail.com \
    --to=inamaru94@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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.