RualM  Freshman Member

Recovery has been finished, everything is ok. Thanks again for your help! :)

Well, I've started the actions above, and now it's in recovering status :) I think all of your advices were missing from my toolbox.... Thank you!

Hmm, interesting... I removed one the disks, and now the state is degraded... I found the faulty disk. Do I have to delete the faulty volume, and after that try to rebuild the raid, as a newly inserted disk?

I repeated the process, and after the mount I got a littlebit different messages: ~ # mkdir /mnt/mountpoint~ # mount /dev/md0 /mnt/mountpoint~ # dmesg | tailUncached vma de8b11d8 (addr 40ad4000 flags 080000ff phy 1edcb000) from pid 2767Uncached vma de8b11d8 (addr 40651000 flags 080000ff phy 1edcb000) from pid 1371Uncached…

There weren't errors, but no changes after restart. Does the below is usable for further investigation? ~ # dmesg | tailxHCI xhci_check_bandwidth called for root hubhub 2-0:1.0: USB hub foundhub 2-0:1.0: 4 ports detectedAdding 514040k swap on /dev/sda1. Priority:-1 extents:1 across:514040kGbE port 0: TxEnable WA - Enabled,…

Yes, it was restarted. Both the log message and the symptom are the same :(

Nice... Results below. Internal volume still in down :( ~ # e2fsck.new /dev/md0e2fsck 1.41.14 (22-Dec-2010)/dev/md0: recovering journal/dev/md0 has been mounted 118 times without being checked, check forced.Pass 1: Checking inodes, blocks, and sizesPass 2: Checking directory structurePass 3: Checking directory…

hi, Sorry, I'm totally rookie in this... I've typed, but ~ # e2fsck /dev/md0-sh: e2fsck: not found~ #