Beiträge von ArmandH

    ok i have solved it partly as i seem to have another broken disk, so two out of 4 :( luckily i was still in test fase and no data loss.
    When i use the two good disk i can make a partition without errors and mount it as well.


    I was reading another post as well about name change and i cleared all the disks as well


    mdadm --stop /dev/md127
    mdadm --remove /dev/md127
    mdadm --zero-superblock /dev/sda
    mdadm --zero-superblock /dev/sdb
    mdadm --zero-superblock /dev/sdd


    That helped in getting a new RAID again with name /dev/md0 instead of the /dev/md127 is this a bug?


    Now i have another issue and that is the name of the mount point is the UUID can i change this to a normal name?


    mount
    /dev/sdc1 on / type ext4 (rw,errors=remount-ro)
    tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
    proc on /proc type proc (rw,noexec,nosuid,nodev)
    sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
    udev on /dev type tmpfs (rw,mode=0755)
    tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
    devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
    tmpfs on /tmp type tmpfs (rw)
    nfsd on /proc/fs/nfsd type nfsd (rw)
    /dev/md0 on /media/f43344e6-c6a3-4546-a0ed-4ea76c9c02ba type ext4 (rw,noexec,acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0)


    Thanks

    Something went completely wrong with building this through the GUI


    when i look at the ARRAY with mdadm:


    mdadm -Esc partition | grep ARRAY
    ARRAY /dev/md/A3B metadata=1.2 UUID=4c09949f:56ba2772:2d19298c:f138dc4e name=openmediavault:A3B


    So why does my mdadm.conf file show


    # definitions of existing MD arrays
    ARRAY /dev/md0 metadata=1.2 name=openmediavault:A3B UUID=4c09949f:56ba2772:2d192
    98c:f138dc4e


    Questions that come out of this is, if working in the GUI really does everything needed to build the array good and put the right config files into place?
    When having a disk fault and reboot changes the disk order, means missing config files?

    blkid
    /dev/sda: UUID="4c09949f-56ba-2772-2d19-298cf138dc4e" LABEL="openmediavault:A3B" TYPE="linux_raid_member"
    /dev/sdb: UUID="4c09949f-56ba-2772-2d19-298cf138dc4e" LABEL="openmediavault:A3B" TYPE="linux_raid_member"
    /dev/sdd: UUID="4c09949f-56ba-2772-2d19-298cf138dc4e" LABEL="openmediavault:A3B" TYPE="linux_raid_member"
    /dev/sdc1: UUID="ca235527-ce21-4d1e-8307-3e165a050efd" TYPE="ext4"
    /dev/sdc5: UUID="8034f2d6-77dd-4e49-99f5-f7c304b6635b" TYPE="swap"
    /dev/md127: LABEL="STORAGE" UUID="bc3e3727-15eb-4dd7-8eb9-75cf2c5ce44b" TYPE="ext4"



    I am trying to understand it better myself as well and what i find weird is the mdadm.conf file as well


    root@openmediavault:/etc/mdadm# more 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=openmediavault:A3B UUID=4c09949f:56ba2772:2d192
    98c:f138dc4e


    # instruct the monitoring daemon where to send mail alerts



    Why do i see there /dev/md0 ?


    Can i control the disk list with the mdadm.conf file as i also noticed that the disk (usb sata drive) i use internal with the OS has changed id when the RAID disk failed


    I had the following
    /dev/sda
    /dev/sdb
    /dev/sdc
    /dev/sdd



    In RAID 10 then /dev/sdd failed, i pulled it out and


    /dev/sde internal usb disk moved to /dev/sdc ???? and /dev/sdc became /dev/sdd which is very confusing

    Hi,


    I recently build a server (OMV 0.4.6 64 bits) with RAID 10 (4X2Tb) and ext4 and i am trying to mount it from the gui and i am getting the following error


    The configuration object is not unique: A mount point already exists for the given filesystem


    clicking on details i see:


    Error #3005:
    exception 'OMVException' with message 'The configuration object is not unique: A mount point already exists for the given filesystem' in /var/www/openmediavault/rpc/filesystemmgmt.inc:675
    Stack trace:
    #0 [internal function]: FileSystemMgmtRpc->mount(Array)
    #1 /usr/share/php/openmediavault/rpc.inc(265): call_user_func_array(Array, Array)
    #2 /usr/share/php/openmediavault/rpc.inc(98): OMVRpc::exec('FileSystemMgmt', 'mount', Array)
    #3 /var/www/openmediavault/rpc.php(44): OMVJsonRpcServer->handle()
    #4 {main}


    But i have not made any mount point before, so how could it exist?


    Checking shell:


    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>
    proc /proc proc defaults 0 0
    # / was on /dev/sda1 during installation
    UUID=ca235527-ce21-4d1e-8307-3e165a050efd / ext4 errors=remount-ro 0 1
    # swap was on /dev/sda5 during installation
    UUID=8034f2d6-77dd-4e49-99f5-f7c304b6635b none swap sw 0 0
    /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
    /dev/sda1 /media/usb0 auto rw,user,noauto 0 0
    /dev/sda2 /media/usb1 auto rw,user,noauto 0 0
    /dev/sda5 /media/usb2 auto rw,user,noauto 0 0
    tmpfs /tmp tmpfs defaults 0 0
    # >>> [openmediavault]
    UUID=bc3e3727-15eb-4dd7-8eb9-75cf2c5ce44b /media/bc3e3727-15eb-4dd7-8eb9-75cf2c5ce44b ext4 defaults,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0 0 2
    # <<< [openmediavault]
    root@openmediavault:~#


    Why is openmediavault using this UUID as mountpoint?


    mdstat:


    root@openmediavault:~# cat /proc/mdstat
    Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
    md127 : active raid10 sda[0] sdd[2](F) sdb[1]
    3907025920 blocks super 1.2 512K chunks 2 near-copies [4/2] [UU__]

    unused devices: <none>


    Yes i know i have a failed RAID one disk failed and i pulled it already but that should not prevent me from mounting?


    root@openmediavault:/media# ls
    bc3e3727-15eb-4dd7-8eb9-75cf2c5ce44b cdrom cdrom0 usb usb0 usb1 usb2
    root@openmediavault:/media# ls -lrt
    total 20
    lrwxrwxrwx 1 root root 6 Dec 15 16:13 cdrom -> cdrom0
    drwxr-xr-x 2 root root 4096 Dec 15 16:13 cdrom0
    lrwxrwxrwx 1 root root 4 Dec 15 16:13 usb -> usb0
    drwxr-xr-x 2 root root 4096 Dec 15 16:13 usb0
    drwxr-xr-x 2 root root 4096 Dec 15 16:13 usb1
    drwxr-xr-x 2 root root 4096 Dec 15 16:13 usb2
    drwxr-xr-x 2 root root 4096 Dec 17 16:09 bc3e3727-15eb-4dd7-8eb9-75cf2c5ce44b
    root@openmediavault:/media# mkdir A3B
    root@openmediavault:/media# ls -lrt
    total 24
    lrwxrwxrwx 1 root root 6 Dec 15 16:13 cdrom -> cdrom0
    drwxr-xr-x 2 root root 4096 Dec 15 16:13 cdrom0
    lrwxrwxrwx 1 root root 4 Dec 15 16:13 usb -> usb0
    drwxr-xr-x 2 root root 4096 Dec 15 16:13 usb0
    drwxr-xr-x 2 root root 4096 Dec 15 16:13 usb1
    drwxr-xr-x 2 root root 4096 Dec 15 16:13 usb2
    drwxr-xr-x 2 root root 4096 Dec 17 16:09 bc3e3727-15eb-4dd7-8eb9-75cf2c5ce44b
    drwxr-xr-x 2 root root 4096 Dec 17 16:40 A3B


    root@openmediavault:/media# mount -t ext4 /dev/md127 /media/A3B
    mount: wrong fs type, bad option, bad superblock on /dev/md127,
    missing codepage or helper program, or other error
    In some cases useful info is found in syslog - try
    dmesg | tail or so


    root@openmediavault:/media#


    root@openmediavault:/media# mount -t ext4 /dev/md127 bc3e3727-15eb-4dd7-8eb9-75cf2c5ce44b
    mount: wrong fs type, bad option, bad superblock on /dev/md127,
    missing codepage or helper program, or other error
    In some cases useful info is found in syslog - try
    dmesg | tail or so


    root@openmediavault:/media#



    Does not seem to work, can someone please tell me what i do wrong thanks