NSA 325 - internal volume down - No such file or directory: '/i-data/md0/.system'

Options
RualM
RualM Posts: 9  Freshman Member
edited May 2019 in Personal Cloud Storage
Hi,

Yesterday there was a blackout, and now the NAS has a problem. Intrenal volume is down, and in the log I've got an interesting message
  • Cannot init applets: [Errno 2] No such file or directory: '/i-data/md0/.system'
A grab a picture from its current state. Is there any option to restore the NAS?


The "No md superblock detected on /dev/sda1/" message is normal?

Thanks in advance,
RualM

#NAS_May_2019
«1

Comments

  • Mijzelf
    Mijzelf Posts: 2,645  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options
    The raid array is obviously assembled, but it's not mounted. So you have probably a damaged filesystem. The most straightforward solution is to repair it:
    e2fsck /dev/md0

  • RualM
    RualM Posts: 9  Freshman Member
    Options
    hi,

    Sorry, I'm totally rookie in this... I've typed, but

    ~ # e2fsck /dev/md0
    -sh: e2fsck: not found
    ~ #


  • Mijzelf
    Mijzelf Posts: 2,645  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options
    Hm. For some reason ZyXEL decided to rename it to e2fsck.new
  • RualM
    RualM Posts: 9  Freshman Member
    Options
    Nice...

    Results below. Internal volume still in down :(

    ~ # e2fsck.new /dev/md0
    e2fsck 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 sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information

    /dev/md0: ***** FILE SYSTEM WAS MODIFIED *****
    /dev/md0: 121464/122068992 files (5.1% non-contiguous), 461498180/488249472 blocks
  • Mijzelf
    Mijzelf Posts: 2,645  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options
    Internal volume still in down

    Have you rebooted?

  • RualM
    RualM Posts: 9  Freshman Member
    edited May 2019
    Options
    Yes, it was restarted. Both the log message and the symptom are the same :(
  • Mijzelf
    Mijzelf Posts: 2,645  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options
    Try to mount it manually.
    <div>mkdir /mnt/mountpoint</div><div><br></div><div>mount /dev/md0 /mnt/mountpoint</div><div></div>
    If that errors out, have a look at the kernel messages
    dmesg | tail

  • RualM
    RualM Posts: 9  Freshman Member
    Options
    There weren't errors, but no changes after restart.

    Does the below is usable for further investigation?

    ~ # dmesg | tail
    xHCI xhci_check_bandwidth called for root hub
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 4 ports detected
    Adding 514040k swap on /dev/sda1.  Priority:-1 extents:1 across:514040k
    GbE port 0: TxEnable WA - Enabled, deep=1, tx_en_bk=1

    Uncached vma de8b1288 (addr 40ad1000 flags 080000ff phy 1edcb000) from pid 2767
    Uncached vma de8b11d8 (addr 40ad4000 flags 080000ff phy 1edcb000) from pid 2767
    Uncached vma de8b11d8 (addr 40651000 flags 080000ff phy 1edcb000) from pid 1371
    Uncached vma de8b11d8 (addr 40651000 flags 080000ff phy 1edcb000) from pid 1371
  • RualM
    RualM Posts: 9  Freshman Member
    Options
    I repeated the process, and after the mount I got a littlebit different messages:

    ~ # mkdir /mnt/mountpoint
    ~ # mount /dev/md0 /mnt/mountpoint
    ~ # dmesg | tail
    Uncached vma de8b11d8 (addr 40ad4000 flags 080000ff phy 1edcb000) from pid 2767
    Uncached vma de8b11d8 (addr 40651000 flags 080000ff phy 1edcb000) from pid 1371
    Uncached vma de8b11d8 (addr 40651000 flags 080000ff phy 1edcb000) from pid 1371
    EXT4-fs (md0): barriers enabled
    kjournald2 starting: pid 3666, dev md0:8, commit interval 5 seconds
    EXT4-fs (md0): internal journal on md0:8
    EXT4-fs (md0): delayed allocation enabled
    EXT4-fs: file extents enabled
    EXT4-fs: mballoc enabled
    EXT4-fs (md0): mounted filesystem with ordered data mode
    ~ #
  • RualM
    RualM Posts: 9  Freshman Member
    Options
    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?

Consumer Product Help Center