File system suddenly disappeared

Meguinness · 15. November 2023

Guys suddenly while streaming a movie everything stopped, the file system as disappeared, the HDs still showing on the DISK section and on the DEVICES ..

But not showing on the SOFTWARE RAID even if trying to CREATE .

In file system it shows as MISSING.

Any help would be appreciated to understand what is happening and how to solve it please.

Omv6 6.4.7-1

Nov 15 21:51:26 omv6 monit[1235]: 'mountpoint_srv_dev-disk-by-uuid-3E3ECF883ECF37A3' status failed (1) -- /srv/dev-disk-by-uuid-3E3ECF883ECF37A3 is not a mountpoint

I have managed to unmount the drives that was showing missing....but when trying to mount them again they will not show on the mount window....but if I choose CREATE new file system all 3x hdds will show 😞, have I lost all my data then as I guess will wipe everything if I choose to CREATE a new file system?

How can 3x HDDs loose their file system at the same time? could the raid card be the problem?

Thank you

Meguinness · 16. November 2023

Come on guys ..surely someone can help me out

Soma · 16. November 2023

Zitat von Meguinness

How can 3x HDDs loose their file system at the same time? could the raid card be the problem?

What do you mean by RAID?

The drives have different FS on them: ext4 and NTFS(bad but yeah...)

post each output inside CODE boxes (not pictures) of:

blkid

lsblk

cat /etc/fstab

sudo omv-showkey fstab

sudo omv-showkey mntent

mount -a

Meguinness · 16. November 2023

is been RAID 5 for the past 2 years with 3xhhds with ext4 file system, suddenly everthing went wrong while watching a movie using EMBY. i was surpriced to see NTFS on the File Systems window...like WHATTTT?

as requested.....thanx

Code

root@omv6:~# blkid
/dev/sdd1: UUID="0CAB-3F74" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="40269dac-cd9c-4cc5-b2b2-162d4cde2a03"
/dev/sdd2: UUID="08741bf8-2513-4bbd-b6bb-ed02780efe40" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="0c824677-61af-4e75-b777-55744d9904f9"
/dev/sdd3: UUID="fb7d6bb7-0d3e-4cb2-b18a-0c350a82070e" TYPE="swap" PARTUUID="dd77bc96-405d-438f-8927-6f54f7df4181"
/dev/sdc: UUID="d5ebc81d-a902-7e4a-54da-4f64ecfefb6d" UUID_SUB="426e5355-fce1-6172-7aa2-3c447450809e" LABEL="openmediavault.local:myraid" TYPE="linux_raid_member"
/dev/sda: UUID="d5ebc81d-a902-7e4a-54da-4f64ecfefb6d" UUID_SUB="57cd1ef8-85b1-054a-777c-7b9f251045d6" LABEL="openmediavault.local:myraid" TYPE="linux_raid_member"
/dev/sdb1: PARTUUID="04836865-407d-4f6c-943e-762d5969fd14"
root@omv6:~#

Code

root@omv6:~#
lsblk
-bash: root@omv6:~#: command not found
-bash: /dev/sdd1:: No such file or directory
-bash: /dev/sdd2:: No such file or directory
-bash: /dev/sdd3:: No such file or directory
-bash: /dev/sdc:: No such file or directory
-bash: /dev/sda:: No such file or directory
-bash: /dev/sdb1:: No such file or directory
-bash: root@omv6:~#: command not found
-bash: root@omv6:~#: command not found
-bash: /dev/sdd1:: No such file or directory
-bash: /dev/sdd2:: No such file or directory
-bash: /dev/sdd3:: No such file or directory
-bash: /dev/sdc:: No such file or directory
-bash: /dev/sda:: No such file or directory
-bash: /dev/sdb1:: No such file or directory
-bash: root@omv6:~#: command not found
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0   5.5T  0 disk
sdb      8:16   0   5.5T  0 disk
└─sdb1   8:17   0   5.5T  0 part
sdc      8:32   0   5.5T  0 disk
sdd      8:48   0 232.9G  0 disk
├─sdd1   8:49   0   512M  0 part /boot/efi
├─sdd2   8:50   0 231.4G  0 part /
└─sdd3   8:51   0   977M  0 part [SWAP]
sr0     11:0    1  1024M  0 rom

Alles anzeigen

Code

root@omv6:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda2 during installation
UUID=08741bf8-2513-4bbd-b6bb-ed02780efe40 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda1 during installation
UUID=0CAB-3F74  /boot/efi       vfat    umask=0077      0       1
# swap was on /dev/sda3 during installation
UUID=fb7d6bb7-0d3e-4cb2-b18a-0c350a82070e none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
# >>> [openmediavault]

Alles anzeigen

Code

sudo omv-showkey fstab
    <fstab>
      <!--
                        <mntent>
                                <uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid>
                                <fsname>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx|xxxx-xxxx|/dev/xxx</fsname>
                                <dir>/xxx/yyy/zzz</dir>
                                <type>none|ext2|ext3|ext4|xfs|jfs|iso9660|udf|...</type>
                                <opts></opts>
                                <freq>0</freq>
                                <passno>0|1|2</passno>
                                <hidden>0|1</hidden>
                                <usagewarnthreshold>xxx</usagewarnthreshold>
                                <comment>xxx</comment>
                        </mntent>
                        -->
      <mntent>
        <uuid>79684322-3eac-11ea-a974-63a080abab18</uuid>
        <fsname>/dev/disk/by-uuid/08741bf8-2513-4bbd-b6bb-ed02780efe40</fsname>
        <dir>/</dir>
        <type>ext4</type>
        <opts>errors=remount-ro</opts>
        <freq>0</freq>
        <passno>1</passno>
        <hidden>1</hidden>
      </mntent>
    </fstab>

Alles anzeigen

Code

root@omv6:~# sudo omv-showkey mntent
                        <mntent>
                                <uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid>
                                <fsname>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx|xxxx-xxxx|/dev/xxx</fsname>
                                <dir>/xxx/yyy/zzz</dir>
                                <type>none|ext2|ext3|ext4|xfs|jfs|iso9660|udf|...</type>
                                <opts></opts>
                                <freq>0</freq>
                                <passno>0|1|2</passno>
                                <hidden>0|1</hidden>
                                <usagewarnthreshold>xxx</usagewarnthreshold>
                                <comment>xxx</comment>
                        </mntent>
      <mntent>
        <uuid>79684322-3eac-11ea-a974-63a080abab18</uuid>
        <fsname>/dev/disk/by-uuid/08741bf8-2513-4bbd-b6bb-ed02780efe40</fsname>
        <dir>/</dir>
        <type>ext4</type>
        <opts>errors=remount-ro</opts>
        <freq>0</freq>
        <passno>1</passno>
        <hidden>1</hidden>
      </mntent>
root@omv6:~#

Alles anzeigen

Code

root@omv6:~#
mount -a
-bash: root@omv6:~#: command not found
-bash: syntax error near unexpected token `newline'
-bash: syntax error near unexpected token `newline'
-bash: syntax error near unexpected token `newline'
-bash: syntax error near unexpected token `newline'
-bash: syntax error near unexpected token `newline'
-bash: syntax error near unexpected token `<'
-bash: syntax error near unexpected token `0'
-bash: syntax error near unexpected token `newline'
-bash: syntax error near unexpected token `newline'
-bash: syntax error near unexpected token `newline'
-bash: syntax error near unexpected token `newline'
-bash: syntax error near unexpected token `newline'
-bash: syntax error near unexpected token `newline'
-bash: syntax error near unexpected token `newline'
-bash: syntax error near unexpected token `newline'
-bash: syntax error near unexpected token `newline'
-bash: syntax error near unexpected token `newline'
-bash: syntax error near unexpected token `newline'
-bash: syntax error near unexpected token `0'
-bash: syntax error near unexpected token `1'
-bash: syntax error near unexpected token `1'
-bash: syntax error near unexpected token `newline'
-bash: root@omv6:~#: command not found
root@omv6:~#

Alles anzeigen

Soma · 16. November 2023

You copy/pasted the commands wrong.

Just write, lsblk on the CLI. No break line.

Same with mount -a

chente · 16. November 2023

Zitat von Meguinness

could the raid card be the problem?

It could be. Please give us hardware details, where are the hard drives connected?

Meguinness · 16. November 2023

sorry ..learning,

mount -a does nothing

Zitat von Soma

You copy/pasted the commands wrong.

Just write, lsblk on the CLI. No break line.

Same with mount -a

Code

root@omv6:~# lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0   5.5T  0 disk
sdb      8:16   0   5.5T  0 disk
└─sdb1   8:17   0   5.5T  0 part
sdc      8:32   0   5.5T  0 disk
sdd      8:48   0 232.9G  0 disk
├─sdd1   8:49   0   512M  0 part /boot/efi
├─sdd2   8:50   0 231.4G  0 part /
└─sdd3   8:51   0   977M  0 part [SWAP]
sr0     11:0    1  1024M  0 rom
root@omv6:~#

Alles anzeigen

Code

root@omv6:~# mount -a
root@omv6:~#

Meguinness · 16. November 2023

Zitat von chente

It could be. Please give us hardware details, where are the hard drives connected?

the 3x drives are attached to a Fujitsu D2607 IT P20 raid card, i added a spare hhd to check if i was able to create a file system and then mount ...and it worked ok so i belive the card is working

Soma · 16. November 2023

Meguinness

According the outputs, one of the drives is simply not showing as a linux raid member (sdb) since it's showing a partition.

sda && sdc are OK (as for RAID ident goes)

As chente said, hardware details are needed and also, how was the RAID created since neither showkey command nor fstab shows any reference to it.

Since this is RAID, I'll ask geaves for some input but you can start by posting (in CODE boxes) the outputs of:

cat /proc/mdstat

fdisk -l | grep "Disk "

cat /etc/mdadm/mdadm.conf

mdadm --detail --scan --verbose

Degraded or missing raid array questions - RAID - openmediavault

Meguinness · 16. November 2023

thanx ..as requested

RAID was created using the raid setup in OMV6 on a different system but same raid card,i then build new NAS and moved hdds across and mount them and the RAID was automaticaly done if i remember correctly , i only had a hdd failing 6 months ago and replaced with a new hdd by formating it to ext4 ..then mount it and added to the RAID.

the 3x drives are attached to a Fujitsu D2607 IT P20 raid card, i added a spare hhd to check if i was able to create a file system and then mount ...and it worked ok so i belive the card is working

Zitat von Soma

According the outputs, one of the drives is simply not showing as a linux raid member (sdb) since it's showing a partition.
sda && sdc are OK (as for RAID ident goes)

As chente said, hardware details are needed and also, how was the RAID created since neither showkey command nor fstab shows any reference to it.

Since this is RAID, I'll ask geaves for some input but you can start by posting (in CODE boxes) the outputs of:
cat /proc/mdstat
fdisk -l | grep "Disk "
cat /etc/mdadm/mdadm.conf
mdadm --detail --scan --verbose

Degraded or missing raid array questions - RAID - openmediavault

Alles anzeigen

Code

root@omv6:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md127 : inactive sda[3](S) sdc[1](S)
      11720784048 blocks super 1.2

unused devices: <none>

Code

root@omv6:~# fdisk -l | grep "Disk "
Disk /dev/sdd: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Fanxiang S101 25
Disk identifier: CF6F2BD1-E831-4851-946D-88B76BE26C09
Disk /dev/sdb: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: WDC WD60EFRX-68L
Disk identifier: 9941E4F0-C8DE-471D-B8BD-1C47BEF4F872
Disk /dev/sdc: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: WDC WD60EFRX-68L
Disk /dev/sda: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: WDC WD60EFAX-68J
root@omv6:~#

Alles anzeigen

Code

root@omv6:~# cat /etc/mdadm/mdadm.conf
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.

# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR salvatorebarrile@gmail.com
MAILFROM root

# definitions of existing MD arrays
ARRAY /dev/md/openmediavault.local:myraid metadata=1.2 name=openmediavault.local:myraid UUID=d5ebc81d:a9027e4a:54da4f64:ecfefb6d
root@omv6:~#

Alles anzeigen

Code

root@omv6:~# mdadm --detail --scan --verbose
INACTIVE-ARRAY /dev/md127 num-devices=2 metadata=1.2 name=openmediavault.local:myraid UUID=d5ebc81d:a9027e4a:54da4f64:ecfefb6d
   devices=/dev/sda,/dev/sdc
root@omv6:~#

Soma · 16. November 2023

Meguinness

Don't do anything else until someone ( geaves , sorry for constantly poking you) give you other instructions.

I reached my knowledge on this matter.

geaves · 21. November 2023

The array is inactive,

mdadm --stop /dev/md127

mdadm --assemble --force --verbose /dev/md127 /dev/sd[ac]

this should rebuild the array in a clean/degraded state, what's odd here is that blkid does not see /dev/sdb and fstab shows no reference to an array and it appears some of the output is missing

Initially resync the array when it's finished reboot and come back

Meguinness · 23. November 2023

Zitat von geaves

The array is inactive,

mdadm --stop /dev/md127

mdadm --assemble --force --verbose /dev/md127 /dev/sd[ac]

this should rebuild the array in a clean/degraded state, what's odd here is that blkid does not see /dev/sdb and fstab shows no reference to an array and it appears some of the output is missing

Initially resync the array when it's finished reboot and come back

Alles anzeigen

hi, i have inserted those commands as you requested geaves ..no luck...,what next ,thank you

Code

root@omv6:~# mdadm --stop /dev/md127
mdadm: stopped /dev/md127
root@omv6:~# mdadm --assemble --force --verbose /dev/md127 /dev/sd[ac]
mdadm: looking for devices for /dev/md127
mdadm: Cannot assemble mbr metadata on /dev/sda
mdadm: /dev/sda has no superblock - assembly aborted
root@omv6:~#

geaves · 23. November 2023

Nothing the array appears to be toast, so, assuming the 3 x 6TB drives are/were part of the array post the output of the following for each drive;

mdadm --examine /dev/sd? replace the ? with each drives reference e.g. mdadm --examine /dev/sda etc

Meguinness · 23. November 2023

Zitat von geaves

Nothing the array appears to be toast, so, assuming the 3 x 6TB drives are/were part of the array post the output of the following for each drive;

mdadm --examine /dev/sd? replace the ? with each drives reference e.g. mdadm --examine /dev/sda etc

here you go as requested, thanx geaves

Code

root@omv6:~# mdadm --examine /dev/sda
/dev/sda:
   MBR Magic : aa55
Partition[0] :   4294967295 sectors at            1 (type ee)
root@omv6:~# mdadm --examine /dev/sdb
/dev/sdb:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : d5ebc81d:a9027e4a:54da4f64:ecfefb6d
           Name : openmediavault.local:myraid
  Creation Time : Sun Mar 15 01:03:15 2020
     Raid Level : raid5
   Raid Devices : 4

 Avail Dev Size : 11720784048 (5588.91 GiB 6001.04 GB)
     Array Size : 17581171200 (16766.71 GiB 18003.12 GB)
  Used Dev Size : 11720780800 (5588.90 GiB 6001.04 GB)
    Data Offset : 261120 sectors
   Super Offset : 8 sectors
   Unused Space : before=261040 sectors, after=3248 sectors
          State : clean
    Device UUID : 57cd1ef8:85b1054a:777c7b9f:251045d6

Internal Bitmap : 8 sectors from superblock
    Update Time : Wed Nov 15 21:39:53 2023
  Bad Block Log : 512 entries available at offset 32 sectors
       Checksum : 9d322405 - correct
         Events : 1849367

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 3
   Array State : AA.A ('A' == active, '.' == missing, 'R' == replacing)
root@omv6:~# mdadm --examine /dev/sdd
/dev/sdd:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : d5ebc81d:a9027e4a:54da4f64:ecfefb6d
           Name : openmediavault.local:myraid
  Creation Time : Sun Mar 15 01:03:15 2020
     Raid Level : raid5
   Raid Devices : 4

 Avail Dev Size : 11720784048 (5588.91 GiB 6001.04 GB)
     Array Size : 17581171200 (16766.71 GiB 18003.12 GB)
  Used Dev Size : 11720780800 (5588.90 GiB 6001.04 GB)
    Data Offset : 261120 sectors
   Super Offset : 8 sectors
   Unused Space : before=261040 sectors, after=3248 sectors
          State : clean
    Device UUID : 426e5355:fce16172:7aa23c44:7450809e

Internal Bitmap : 8 sectors from superblock
    Update Time : Wed Nov 15 21:40:01 2023
  Bad Block Log : 512 entries available at offset 32 sectors
       Checksum : 8fbf5bbe - correct
         Events : 1849367

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 1
   Array State : AA.A ('A' == active, '.' == missing, 'R' == replacing)
root@omv6:~# root@omv6:~# mdadm --examine /dev/sda
/dev/sda:
   MBR Magic : aa55
Partition[0] :   4294967295 sectors at            1 (type ee)
root@omv6:~# mdadm --examine /dev/sdb
/dev/sdb:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : d5ebc81d:a9027e4a:54da4f64:ecfefb6d
           Name : openmediavault.local:myraid
  Creation Time : Sun Mar 15 01:03:15 2020
     Raid Level : raid5
   Raid Devices : 4

 Avail Dev Size : 11720784048 (5588.91 GiB 6001.04 GB)
     Array Size : 17581171200 (16766.71 GiB 18003.12 GB)
  Used Dev Size : 11720780800 (5588.90 GiB 6001.04 GB)
    Data Offset : 261120 sectors
   Super Offset : 8 sectors
   Unused Space : before=261040 sectors, after=3248 sectors
          State : clean
    Device UUID : 57cd1ef8:85b1054a:777c7b9f:251045d6

Internal Bitmap : 8 sectors from superblock
    Update Time : Wed Nov 15 21:39:53 2023
  Bad Block Log : 512 entries available at offset 32 sectors
       Checksum : 9d322405 - correct
         Events : 1849367

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 3
   Array State : AA.A ('A' == active, '.' == missing, 'R' == replacing)
root@omv6:~# mdadm --examine /dev/sdd
/dev/sdd:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : d5ebc81d:a9027e4a:54da4f64:ecfefb6d
           Name : openmediavault.local:myraid
  Creation Time : Sun Mar 15 01:03:15 2020
     Raid Level : raid5
   Raid Devices : 4

 Avail Dev Size : 11720784048 (5588.91 GiB 6001.04 GB)
     Array Size : 17581171200 (16766.71 GiB 18003.12 GB)
  Used Dev Size : 11720780800 (5588.90 GiB 6001.04 GB)
    Data Offset : 261120 sectors
   Super Offset : 8 sectors
   Unused Space : before=261040 sectors, after=3248 sectors
          State : clean
root@omv6:~#te : AA.A ('A' == active, '.' == missing, 'R' == replacing)

Alles anzeigen

geaves · 23. November 2023

This still makes no sense!! The --examine output says there should be 4 devices in that Raid5 and you've run the --examine on /sdb and /sdd twice!!

Do not shutdown or restart the machine the drive references can change, post the output again of the following;

fdisk -l | grep "Disk "

blkid

if the system fails to locate at least 3 of those drives in the array and mdadm fails to rebuild the array with 3 of the 4 drives in the array, the array is toast, Raid5 allows for ONE drive failure only

Meguinness · 23. November 2023

geaves

i have 3x 6tb hdds for data and 1x ssd for the OS.

i only replaced 1x hdd after failing 4 month ago and added it in to the RAID5. thanx

Code

root@omv6:~# mdadm --examine /dev/sda
/dev/sda:
   MBR Magic : aa55
Partition[0] :   4294967295 sectors at            1 (type ee)
root@omv6:~# mdadm --examine /dev/sdb
/dev/sdb:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : d5ebc81d:a9027e4a:54da4f64:ecfefb6d
           Name : openmediavault.local:myraid
  Creation Time : Sun Mar 15 01:03:15 2020
     Raid Level : raid5
   Raid Devices : 4

 Avail Dev Size : 11720784048 (5588.91 GiB 6001.04 GB)
     Array Size : 17581171200 (16766.71 GiB 18003.12 GB)
  Used Dev Size : 11720780800 (5588.90 GiB 6001.04 GB)
    Data Offset : 261120 sectors
   Super Offset : 8 sectors
   Unused Space : before=261040 sectors, after=3248 sectors
          State : clean
    Device UUID : 57cd1ef8:85b1054a:777c7b9f:251045d6

Internal Bitmap : 8 sectors from superblock
    Update Time : Wed Nov 15 21:39:53 2023
  Bad Block Log : 512 entries available at offset 32 sectors
       Checksum : 9d322405 - correct
         Events : 1849367

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 3
   Array State : AA.A ('A' == active, '.' == missing, 'R' == replacing)
root@omv6:~# mdadm --examine /dev/sdd
/dev/sdd:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : d5ebc81d:a9027e4a:54da4f64:ecfefb6d
           Name : openmediavault.local:myraid
  Creation Time : Sun Mar 15 01:03:15 2020
     Raid Level : raid5
   Raid Devices : 4

 Avail Dev Size : 11720784048 (5588.91 GiB 6001.04 GB)
     Array Size : 17581171200 (16766.71 GiB 18003.12 GB)
  Used Dev Size : 11720780800 (5588.90 GiB 6001.04 GB)
    Data Offset : 261120 sectors
   Super Offset : 8 sectors
   Unused Space : before=261040 sectors, after=3248 sectors
          State : clean
    Device UUID : 426e5355:fce16172:7aa23c44:7450809e

Internal Bitmap : 8 sectors from superblock
    Update Time : Wed Nov 15 21:40:01 2023
  Bad Block Log : 512 entries available at offset 32 sectors
       Checksum : 8fbf5bbe - correct
         Events : 1849367

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 1
   Array State : AA.A ('A' == active, '.' == missing, 'R' == replacing)
root@omv6:~# mdadm --examine /dev/sdc
/dev/sdc:
   MBR Magic : aa55
Partition[0] :    488397167 sectors at            1 (type ee)
root@omv6:~#

Alles anzeigen

Code

root@omv6:~# fdisk -l | grep "Disk "
Disk /dev/sdc: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Fanxiang S101 25
Disk identifier: CF6F2BD1-E831-4851-946D-88B76BE26C09
Disk /dev/sdb: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: WDC WD60EFAX-68J
Disk /dev/sda: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: WDC WD60EFRX-68L
Disk identifier: 9941E4F0-C8DE-471D-B8BD-1C47BEF4F872
Disk /dev/sdd: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: WDC WD60EFRX-68L
root@omv6:~# blkid
/dev/sdc1: UUID="0CAB-3F74" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="40269dac-cd9c-4cc5-b2b2-162                                  d4cde2a03"
/dev/sdc2: UUID="08741bf8-2513-4bbd-b6bb-ed02780efe40" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID=                                  "0c824677-61af-4e75-b777-55744d9904f9"
/dev/sdc3: UUID="fb7d6bb7-0d3e-4cb2-b18a-0c350a82070e" TYPE="swap" PARTUUID="dd77bc96-405d-438                                  f-8927-6f54f7df4181"
/dev/sdb: UUID="d5ebc81d-a902-7e4a-54da-4f64ecfefb6d" UUID_SUB="57cd1ef8-85b1-054a-777c-7b9f25                                  1045d6" LABEL="openmediavault.local:myraid" TYPE="linux_raid_member"
/dev/sdd: UUID="d5ebc81d-a902-7e4a-54da-4f64ecfefb6d" UUID_SUB="426e5355-fce1-6172-7aa2-3c4474                                  50809e" LABEL="openmediavault.local:myraid" TYPE="linux_raid_member"
/dev/sda1: PARTUUID="04836865-407d-4f6c-943e-762d5969fd14"
root@omv6:~#

Alles anzeigen

geaves · 23. November 2023

OK I don't know why you run mdadm --examine again, but let me clarify;

this line -> Raid Devices : 4 from mdadm --examine is looking for/wanting 4 drives within that array,

blkid can only find 2

fdisk and your image can find 3 x 6TB, so unless those drives can assemble without error in a clean/degraded state, there's nothing to be done

post the output of mdadm --detail /dev/md127

Meguinness · 23. November 2023

here it is

Code

root@omv6:~# mdadm --detail /dev/md127
/dev/md127:
           Version : 1.2
        Raid Level : raid0
     Total Devices : 2
       Persistence : Superblock is persistent

             State : inactive
   Working Devices : 2

              Name : openmediavault.local:myraid
              UUID : d5ebc81d:a9027e4a:54da4f64:ecfefb6d
            Events : 1849367

    Number   Major   Minor   RaidDevice

       -       8       48        -        /dev/sdd
       -       8       16        -        /dev/sdb
root@omv6:~#

Alles anzeigen

geaves · 23. November 2023

That's the output I expected, there's nothing to be done, the output from --examine wants 4 devices you only have 2 that mdadm recognises as being part of an array, the array could be assembled with 3 out of 4 drives as Raid5 allows one drive failure

File system suddenly disappeared

geaves 21. November 2023

Jetzt mitmachen!

Ähnliche Themen

RAID 5 missing after power loss

quotacheck error and missing aquota files.