unable to mount raid set after power los and reinstall

1. offizieller Beitrag

    hello,


    I had a power issue in my house and the openmediavault was booting in a rescue mode.

    decided to install openmediavault on e fresh new disk, all works and a am able to see the raid set , but i cannot mount it.


    What do i need to do to active , import or enable the raid set?


    thanks for taking the time to help me


    ,

    thank you for replying

    sda is my hardware raid 6.4 8 1tb disks in raid 5 but i am unable to mount it, or i don't know how to mount it from the command line interface, i am new to unix/ linux.


    i reinstalled Openmediavault on new disk everything works, except mounting my old raid , all my photos and movies are on it :(


    yes i know raid is no back up ;(

    • Offizieller Beitrag
    Zitat von Canardo

    sda is my hardware raid 6.4 8 1tb disks in raid 5 but i am unable to mount it

    You have no way of knowing if any of the drives have failed unless you can check the hardware raid settings within the raid card, a hardware raid presents itself to OMV as a single drive. When you say you cannot mount it /dev/sda, you select the drive under file systems click mount on the menu and nothing happens.

    hello,

    my raid set is perfectly OK , its the newly installed Openmediavault who is unable to mount the existing raid volume , how do i mount it?


    i don't see the disk in filesystems to mount it.


    hope you can help me please




    root@openmediavault:~# blkid

    /dev/sda1: UUID="7b5738d5-fef3-4245-a5c8-068421d79852" TYPE="ext4" PARTUUID="01e8731b-b7fe-4aa0-b514-fc9e6c742589"

    /dev/sdb1: UUID="a3b1fab1-100e-4a95-aa67-10fa8f0e15e0" TYPE="ext4" PARTUUID="9df377c1-01"

    /dev/sdb5: UUID="2655b01a-b177-4e4e-9e29-3e1d4636b619" TYPE="swap" PARTUUID="9df377c1-05"

    root@openmediavault:~# cat /etc/mdadm/mdadm.conf

    # mdadm.conf

    #

    # !NB! Run update-initramfs -u after updating this file.

    # !NB! This will ensure that initramfs has an uptodate copy.

    #

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

    #


    # by default (built-in), scan all partitions (/proc/partitions) and all

    # containers for MD superblocks. alternatively, specify devices to scan, using

    # wildcards if desired.

    #DEVICE partitions containers


    # automatically tag new arrays as belonging to the local system

    HOMEHOST <system>


    # instruct the monitoring daemon where to send mail alerts

    MAILADDR root


    # definitions of existing MD arrays


    # This configuration was auto-generated on Wed, 25 Mar 2020 16:23:07 +0000 by mkconf

    root@openmediavault:~# mdadm --detail --scan --verbose

    root@openmediavault:~# blkid

    /dev/sda1: UUID="7b5738d5-fef3-4245-a5c8-068421d79852" TYPE="ext4" PARTUUID="01e8731b-b7fe-4aa0-b514-fc9e6c742589"

    /dev/sdb1: UUID="a3b1fab1-100e-4a95-aa67-10fa8f0e15e0" TYPE="ext4" PARTUUID="9df377c1-01"

    /dev/sdb5: UUID="2655b01a-b177-4e4e-9e29-3e1d4636b619" TYPE="swap" PARTUUID="9df377c1-05"

    root@openmediavault:~# 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).

    #

    # <file system> <mount point> <type> <options> <dump> <pass>

    # / was on /dev/sdb1 during installation

    UUID=a3b1fab1-100e-4a95-aa67-10fa8f0e15e0 / ext4 errors=remount-ro 0 1

    # swap was on /dev/sdb5 during installation

    UUID=2655b01a-b177-4e4e-9e29-3e1d4636b619 none swap sw 0 0

    root@openmediavault:~# 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).

    #

    # <file system> <mount point> <type> <options> <dump> <pass>

    # / was on /dev/sdb1 during installation

    UUID=a3b1fab1-100e-4a95-aa67-10fa8f0e15e0 / ext4 errors=remount-ro 0 1

    # swap was on /dev/sdb5 during installation

    UUID=2655b01a-b177-4e4e-9e29-3e1d4636b619 none swap sw 0 0

    root@openmediavault:~#

    • Offizieller Beitrag
    Zitat von Canardo

    my raid set is perfectly ok

    According to that output it says it's checking

    Zitat von Canardo

    existing raid volume

    It's not a raid volume OMV sees this as a drive, but you could try this


    mount /dev/sda /srv if that works you'll need to run an fstab config but you've not mentioned what version of OMV

    yes it is always checking when it boots up


    root@openmediavault:~# mount /dev/sda /srv

    mount: /srv: wrong fs type, bad option, bad superblock on /dev/sda, missing codepage or helper program, or other error.


    root@openmediavault:~# blkid

    /dev/sda1: UUID="7b5738d5-fef3-4245-a5c8-068421d79852" TYPE="ext4" PARTUUID="01e8731b-b7fe-4aa0-b514-fc9e6c742589"

    /dev/sdb1: UUID="a3b1fab1-100e-4a95-aa67-10fa8f0e15e0" TYPE="ext4" PARTUUID="9df377c1-01"

    /dev/sdb5: UUID="2655b01a-b177-4e4e-9e29-3e1d4636b619" TYPE="swap" PARTUUID="9df377c1-05"

    root@openmediavault:~#

    root@openmediavault:~# fsck /dev/sda

    fsck from util-linux 2.33.1

    e2fsck 1.44.5 (15-Dec-2018)

    ext2fs_open2: Bad magic number in super-block

    fsck.ext2: Superblock invalid, trying backup blocks...

    fsck.ext2: Bad magic number in super-block while trying to open /dev/sda


    The superblock could not be read or does not describe a valid ext2/ext3/ext4

    filesystem. If the device is valid and it really contains an ext2/ext3/ext4

    filesystem (and not swap or ufs or something else), then the superblock

    is corrupt, and you might try running e2fsck with an alternate superblock:

    e2fsck -b 8193 <device>

    or

    e2fsck -b 32768 <device>


    Found a gpt partition table in /dev/sda

    root@openmediavault:~# mount -t ext4 /dev/sda /srv

    mount: /srv: wrong fs type, bad option, bad superblock on /dev/sda, missing codepage or helper program, or other error.

    root@openmediavault:~#

    root@openmediavault:~# sudo fdisk -l

    Disk /dev/sda: 6.4 TiB, 6999997677568 bytes, 13671870464 sectors

    Disk model: ARC-1222-VOL#000

    Units: sectors of 1 * 512 = 512 bytes

    Sector size (logical/physical): 512 bytes / 512 bytes

    I/O size (minimum/optimal): 512 bytes / 512 bytes

    Disklabel type: gpt

    Disk identifier: 46572EDF-A2AC-4470-B478-FC441CC51520


    Device Start End Sectors Size Type

    /dev/sda1 2048 13671870430 13671868383 6.4T Linux filesystem



    Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors

    Disk model: WDC WD10JPVX-75J

    Units: sectors of 1 * 512 = 512 bytes

    Sector size (logical/physical): 512 bytes / 4096 bytes

    I/O size (minimum/optimal): 4096 bytes / 4096 bytes

    Disklabel type: dos

    Disk identifier: 0x9df377c1


    Device Boot Start End Sectors Size Id Type

    /dev/sdb1 * 2048 1937272831 1937270784 923.8G 83 Linux

    /dev/sdb2 1937274878 1953523711 16248834 7.8G 5 Extended

    /dev/sdb5 1937274880 1953523711 16248832 7.8G 82 Linux swap / Solaris


    Partition 2 does not start on physical sector boundary.

    root@openmediavault:~#

    root@openmediavault:~# fsck /dev/sda

    fsck from util-linux 2.33.1

    e2fsck 1.44.5 (15-Dec-2018)

    ext2fs_open2: Bad magic number in super-block

    fsck.ext2: Superblock invalid, trying backup blocks...

    fsck.ext2: Bad magic number in super-block while trying to open /dev/sda


    The superblock could not be read or does not describe a valid ext2/ext3/ext4

    filesystem. If the device is valid and it really contains an ext2/ext3/ext4

    filesystem (and not swap or ufs or something else), then the superblock

    is corrupt, and you might try running e2fsck with an alternate superblock:

    e2fsck -b 8193 <device>

    or

    e2fsck -b 32768 <device>


    Found a gpt partition table in /dev/sda

    • Offizieller Beitrag

    Sorry there's nothing else that I can think of to check the state of your data other than perhaps running a live distro or systemrescuecd, or to search for something like repair superblock as usually backups are stored on the drive and one of those has to be restored.

    thank you for taken the time to help me.

    it is an gpt partion, does that makes a difference?


    Model: Areca ARC-1222-VOL#000 (scsi)

    Disk /dev/sda: 7000GB

    Sector size (logical/physical): 512B/512B

    Partition Table: gpt

    Disk Flags:


    Number Start End Size File system Name Flags

    1 1049kB 7000GB 7000GB ext4



    root@openmediavault:~# sudo fdisk -l /dev/sda

    Disk /dev/sda: 6.4 TiB, 6999997677568 bytes, 13671870464 sectors

    Disk model: ARC-1222-VOL#000

    Units: sectors of 1 * 512 = 512 bytes

    Sector size (logical/physical): 512 bytes / 512 bytes

    I/O size (minimum/optimal): 512 bytes / 512 bytes

    Disklabel type: gpt

    Disk identifier: 46572EDF-A2AC-4470-B478-FC441CC51520


    Device Start End Sectors Size Type

    /dev/sda1 2048 13671870430 13671868383 6.4T Linux filesystem

    root@openmediavault:~# sudo parted /dev/sda print

    Model: Areca ARC-1222-VOL#000 (scsi)

    Disk /dev/sda: 7000GB

    Sector size (logical/physical): 512B/512B

    Partition Table: gpt

    Disk Flags:


    Number Start End Size File system Name Flags

    1 1049kB 7000GB 7000GB ext4

    i fixed it myself!


    it was gpt disk so i needed to use sfdisk



    Code
    $ sudo sfdisk -l

    This will list all the GPT devices & partitions. You can create a partition using sfdisk as well.

    Code
    $ sudo sfdisk /dev/sda

    After you've created a partition using sfdisk you'll want to format it:

    Code
    $ mkfs.ext4 /dev/sda1

Jetzt mitmachen!

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

Benutzerkonto erstellen Anmelden