Raid 0 SW missing after reboot

  • Hi,


    I'm beginners on linux/OMV, but after some days, my Nas are UP.
    My problem, i have 2X4To WD RED NAS edition, i create Raid 0 SW Ext4, and make som share (SMB/CIFS, NFS...)


    Problem, when i reboot my Nas, May Raid 0 SW are disapear!
    I need to recreate new Raid 0 SW, new Share, again and again, perhaps, i lost all data on the Raid 0.


    Anyone can help me?
    (sorry for my bad english, i'm french).
    Thanks by advance.


    Information from my configuration HDD :


    login as: root
    root@192.168.1.38's password:
    Linux omv-nas 3.16.0-0.bpo.4-amd64 #1 SMP Debian 3.16.7-ckt25-2~bpo70+1 (2016-04-12) x86_64


    The programs included with the Debian GNU/Linux system are free software;
    the exact distribution terms for each program are described in the
    individual files in /usr/share/doc/*/copyright.


    Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
    permitted by applicable law.
    Last login: Sun May 29 11:17:52 2016 from pc-david.home
    root@omv-nas:~# cat /proc/mdstat
    Personalities :
    unused devices: <none>
    root@omv-nas:~# blkid
    /dev/sda5: UUID="9440963a-1599-4d3d-a73a-72af685e51f1" TYPE="swap"
    /dev/sda1: UUID="7e3a8d3b-2f41-4c4f-9f34-19432743295a" TYPE="ext4"
    /dev/sdd2: LABEL="500Go-2-USB" UUID="64FE2C09FE2BD25A" TYPE="ntfs"
    /dev/sde2: LABEL="500Go-1-USB" UUID="580621C90621A8C8" TYPE="ntfs"
    /dev/sdf1: LABEL="SSHD-2To" UUID="2E5224655224344D" TYPE="ntfs"
    root@omv-nas:~# fdisk -l


    Disk /dev/sda: 256.1 GB, 256060514304 bytes
    255 heads, 63 sectors/track, 31130 cylinders, total 500118192 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disk identifier: 0x000b739a


    Device Boot Start End Blocks Id System
    /dev/sda1 * 2048 479801343 239899648 83 Linux
    /dev/sda2 479803390 500117503 10157057 5 Extended
    Partition 2 does not start on physical sector boundary.
    /dev/sda5 479803392 500117503 10157056 82 Linux swap / Solaris


    WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.


    Disk /dev/sdc: 4000.8 GB, 4000787030016 bytes
    256 heads, 63 sectors/track, 484501 cylinders, total 7814037168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disk identifier: 0x50bafe80


    Device Boot Start End Blocks Id System
    /dev/sdc1 1 4294967295 2147483647+ ee GPT
    Partition 1 does not start on physical sector boundary.


    WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


    Disk /dev/sdb: 4000.8 GB, 4000787030016 bytes
    256 heads, 63 sectors/track, 484501 cylinders, total 7814037168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disk identifier: 0xb90e1ab0


    Device Boot Start End Blocks Id System
    /dev/sdb1 1 4294967295 2147483647+ ee GPT
    Partition 1 does not start on physical sector boundary.


    WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted.


    Disk /dev/sdd: 500.1 GB, 500107862016 bytes
    256 heads, 63 sectors/track, 60563 cylinders, total 976773168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x397eba02


    Device Boot Start End Blocks Id System
    /dev/sdd1 1 4294967295 2147483647+ ee GPT


    WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util fdisk doesn't support GPT. Use GNU Parted.


    Disk /dev/sde: 500.1 GB, 500107862016 bytes
    256 heads, 63 sectors/track, 60563 cylinders, total 976773168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0xa4b57300


    Device Boot Start End Blocks Id System
    /dev/sde1 1 4294967295 2147483647+ ee GPT


    Disk /dev/sdf: 2000.4 GB, 2000398934016 bytes
    255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x53e66a9d


    Device Boot Start End Blocks Id System
    /dev/sdf1 2048 3907026943 1953512448 7 HPFS/NTFS/exFAT
    root@omv-nas:~# cat /etc/mdadm/mdadm.conf
    # 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>


    # definitions of existing MD arrays
    ARRAY /dev/md0 metadata=1.2 name=omv-nas:8To UUID=d7af1aef:7044584f:16f56c11:6f15eb60
    root@omv-nas:~# mdadm --detail --scan --verbose
    root@omv-nas:~#

    • Offizieller Beitrag

    mdadm --assemble --force --verbose /dev/md127 /dev/sd[bc]
    update-initramfs -u

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Thanks ryecoaarn,


    here's what I get like message via SSH terminal


    login as: root
    root@192.168.1.38's password:
    Linux omv-nas 3.16.0-0.bpo.4-amd64 #1 SMP Debian 3.16.7-ckt25-2~bpo70+1 (2016-04 -12) x86_64


    The programs included with the Debian GNU/Linux system are free software;
    the exact distribution terms for each program are described in the
    individual files in /usr/share/doc/*/copyright.


    Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
    permitted by applicable law.
    Last login: Sun May 29 18:13:22 2016 from pc-david.home
    root@omv-nas:~# mdadm --assemble --force --verbose /dev/md127 /dev/sd[bc]
    mdadm: looking for devices for /dev/md127
    mdadm: Cannot assemble mbr metadata on /dev/sdb
    mdadm: /dev/sdb has no superblock - assembly aborted

    • Offizieller Beitrag

    Something is wrong with that drive and with raid 0, you have no redundancy. Not much you can do.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • In Syslog i have this message :
    May 30 18:18:18 omv-nas collectd[11812]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
    May 30 18:18:21 omv-nas kernel: [ 1436.513191] md: bind<sdb>
    May 30 18:18:21 omv-nas kernel: [ 1436.513505] md: bind<sdc>
    May 30 18:18:21 omv-nas kernel: [ 1436.515746] md/raid0:md0: md_size is 15628072960 sectors.
    May 30 18:18:21 omv-nas kernel: [ 1436.515754] md: RAID0 configuration for md0 - 1 zone
    May 30 18:18:21 omv-nas kernel: [ 1436.515758] md: zone0=[sdb/sdc]
    May 30 18:18:21 omv-nas kernel: [ 1436.515766] zone-offset= 0KB, device-offset= 0KB, size=7814036480KB
    May 30 18:18:21 omv-nas kernel: [ 1436.515769]
    May 30 18:18:21 omv-nas kernel: [ 1436.515793] md0: detected capacity change from 0 to 8001573355520
    May 30 18:18:21 omv-nas kernel: [ 1436.516331] md0: unknown partition table
    May 30 18:07:58 omv-nas collectd[11812]: rrdcached plugin: rrdc_update (/var/lib/rrdcached/db/localhost/df-root/df_complex-free.rrd, [1464624478:226786021376.000000], 1) failed with status -1.


    And this when i create my Raid 0 :


    Version : 1.2
    Creation Time : Mon May 30 17:56:02 2016
    Raid Level : raid0
    Array Size : 7814036480 (7452.05 GiB 8001.57 GB)
    Raid Devices : 2
    Total Devices : 2
    Persistence : Superblock is persistent


    Update Time : Mon May 30 17:56:02 2016
    State : clean
    Active Devices : 2
    Working Devices : 2
    Failed Devices : 0
    Spare Devices : 0


    Chunk Size : 512K


    Name : omv-nas:8ToHDD (local to host omv-nas)
    UUID : 3fbba2fd:c0d243c6:8e090b36:2e3cc048
    Events : 0


    Number Major Minor RaidDevice State
    0 8 16 0 active sync /dev/sdb
    1 8 32 1 active sync /dev/sdc

    • Offizieller Beitrag

    Looks fine when you create a new array.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    Still? Not sure what is wrong. Are these drives connected via sata or usb?

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Hi,


    I found!


    I reformat using BTFRS, I created my Raid 0, created my shares, and everything seems to work!
    I can restart my my NAS RAID 0 BTFRS is always present.
    it seems that I have an incompatibility between my drive and EXT file system 4 in Raid 0.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!