Beiträge von mateuxp

mateuxp · 19. Dezember 2017

I've misunderstand your previous question. Take a look:

Code

# smartctl -a /dev/sde
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.13.0-0.bpo.1-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org


=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Green
Device Model:     WDC WD20EZRX-00D8PB0
Serial Number:    WD-WCC4M0ZYTJH8
LU WWN Device Id: 5 0014ee 20b50d5a6
Firmware Version: 80.00A80
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Tue Dec 19 22:40:05 2017 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled






smartctl -a /dev/sdd
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.13.0-0.bpo.1-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org


=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Green
Device Model:     WDC WD20EZRX-00D8PB0
Serial Number:    WD-WCC4M5LES82D
LU WWN Device Id: 5 0014ee 2b5fc2975
Firmware Version: 80.00A80
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Tue Dec 19 22:42:42 2017 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Alles anzeigen

mateuxp · 18. Dezember 2017

Zitat von tkaiser

Similar issues only occurring with 4.13: https://ubuntuforums.org/showthread.php?t=2376227&page=3

Which drives are these two?

/dev/sde & /dev/sdd

mateuxp · 12. Dezember 2017

Zitat von votdev
Is it listed in
Bash
# cat /proc/partitions

it is:

Code

cat /proc/partitions
major minor  #blocks  name


   8        0  500107608 sda
   8        1  500106584 sda1
   8       16  250059096 sdb
   8       17       1024 sdb1
   8       18  239899648 sdb2
   8       19   10157056 sdb3
   8       32  250059096 sdc
   8       33  250058055 sdc1
   8       48 1953514584 sdd
   9        0 1953383488 md0
   8       64 1953514584 sde

Alles anzeigen

mateuxp · 12. Dezember 2017

Anyone any ideas? Maybe I should create a bug in some system?

mateuxp · 10. Dezember 2017

Command lsblk is displaying md0 raid array, look at row 12 & 14:

Code

# lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda      8:0    0   477G  0 disk
`-sda1   8:1    0   477G  0 part  /srv/dev-disk-by-id-usb-JMicron_Tech_DB12345681BC-0-0-part1
sdb      8:16   0 238.5G  0 disk
|-sdb1   8:17   0     1M  0 part
|-sdb2   8:18   0 228.8G  0 part  /
`-sdb3   8:19   0   9.7G  0 part  [SWAP]
sdc      8:32   0 238.5G  0 disk
`-sdc1   8:33   0 238.5G  0 part  /srv/dev-disk-by-label-DataSSD
sdd      8:48   0   1.8T  0 disk
`-md0    9:0    0   1.8T  0 raid1 /srv/dev-disk-by-id-md-name-nas-Matrix
sde      8:64   0   1.8T  0 disk
`-md0    9:0    0   1.8T  0 raid1 /srv/dev-disk-by-id-md-name-nas-Matrix

Alles anzeigen

Don't think there is problem with /dev/md0 but I don't have proofs yet as well as OMV 4 broke something during upgrade, interesting issue

df -kh shows /dev/md0 also correctly

Code

# df -kh
Filesystem      Size  Used Avail Use% Mounted on
udev            7.8G     0  7.8G   0% /dev
tmpfs           1.6G  149M  1.5G  10% /run
/dev/sdb2       226G  7.9G  206G   4% /
tmpfs           7.8G     0  7.8G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           7.8G     0  7.8G   0% /sys/fs/cgroup
tmpfs            50G  3.9M   50G   1% /tmp
/dev/sda1       469G   47G  399G  11% /srv/dev-disk-by-id-usb-JMicron_Tech_DB12345681BC-0-0-part1
/dev/md0        1.8T  269G  1.6T  15% /srv/dev-disk-by-id-md-name-nas-Matrix
/dev/sdc1       234G   16G  218G   7% /srv/dev-disk-by-label-DataSSD
overlay         226G  7.9G  206G   4% /var/lib/docker/overlay2/8d82d021a383e5eee56aa9e7b6abf22e6549d9e25048aadcf83222ba26e0fa66/merged
shm              64M     0   64M   0% /var/lib/docker/containers/1c34752954b20f230bdf18296ef6490d1ad1fa23a8bfab79a5a026150b159823/shm

Alles anzeigen

mateuxp · 9. Dezember 2017

I've found something else related to this issue. When I tried to add Shared folder I get following error:

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; blkid -p -o full '/dev/md0' 2>&1' with exit code '8': /dev/md0: ambivalent result (probably more filesystems on the device, use wipefs(8) to see more details)


Error #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; blkid -p -o full '/dev/md0' 2>&1' with exit code '8': /dev/md0: ambivalent result (probably more filesystems on the device, use wipefs(8) to see more details) in /usr/share/php/openmediavault/system/process.inc:175
Stack trace:
#0 /usr/share/php/openmediavault/system/filesystem/filesystem.inc(115): OMV\System\Process->execute(Array)
#1 /usr/share/php/openmediavault/system/filesystem/filesystem.inc(757): OMV\System\Filesystem\Filesystem->getData()
#2 /usr/share/openmediavault/engined/rpc/sharemgmt.inc(97): OMV\System\Filesystem\Filesystem->getDescription()
#3 [internal function]: OMVRpcServiceShareMgmt->getCandidates(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#5 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getCandidates', Array, Array)
#6 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('ShareMgmt', 'getCandidates', Array, Array, 1)
#7 {main}

Alles anzeigen

I can't chose "Device" to add "Shared folder" due to this error. Totally confused, how is that possible to get two filesystems on array, I think that is not true

fdisk -l

Code

# fdisk -l
Disk /dev/sdb: 238.5 GiB, 256060514304 bytes, 500118192 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
Disklabel type: gpt
Disk identifier: 28024B9D-9A47-4130-9349-83B733347DCF


Device     Start       End   Sectors   Size Type
/dev/sdb1   2048 500118158 500116111 238.5G Linux filesystem




Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 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
Disklabel type: gpt
Disk identifier: 0EBBA207-0B19-4F27-8BEC-70088765E75B


Device         Start       End   Sectors   Size Type
/dev/sda1       2048      4095      2048     1M BIOS boot
/dev/sda2       4096 479803391 479799296 228.8G Linux filesystem
/dev/sda3  479803392 500117503  20314112   9.7G Linux swap




Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 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 /dev/md0: 1.8 TiB, 2000264691712 bytes, 3906766976 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 /dev/sdd: 1.8 TiB, 2000398934016 bytes, 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 /dev/sde: 477 GiB, 512110190592 bytes, 1000215216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
Disklabel type: dos
Disk identifier: 0x893c809b


Device     Boot Start        End    Sectors  Size Id Type
/dev/sde1        2048 1000215215 1000213168  477G 83 Linux

Alles anzeigen

mateuxp · 9. Dezember 2017

Zitat von votdev
What is the output of
Bash
# udevadm info --query=property --name=/dev/md0

please find output below:

Code

# udevadm info --query=property --name=/dev/md0
DEVLINKS=/dev/disk/by-id/md-name-nas:Matrix /dev/disk/by-id/md-uuid-df704e6d:b0ecd791:5d0909cd:b0c6a6c3
DEVNAME=/dev/md0
DEVPATH=/devices/virtual/block/md0
DEVTYPE=disk
MAJOR=9
MD_DEVICES=2
MD_DEVICE_sdc_DEV=/dev/sdc
MD_DEVICE_sdc_ROLE=0
MD_DEVICE_sdd_DEV=/dev/sdd
MD_DEVICE_sdd_ROLE=1
MD_LEVEL=raid1
MD_METADATA=1.2
MD_NAME=nas:Matrix
MD_UUID=df704e6d:b0ecd791:5d0909cd:b0c6a6c3
MINOR=0
SUBSYSTEM=block
SYSTEMD_WANTS=mdmonitor.service
TAGS=:systemd:
USEC_INITIALIZED=3549891

Alles anzeigen

mateuxp · 8. Dezember 2017

Let me ask in correct way after macom:"

Is this a bug in OMV4 or what should I do to get my RAID visible in OMV GUI?

Thanks!

mateuxp · 8. Dezember 2017

Hi,

I've upgraded my OMV 3 to newest 4.0.14-1 Arrakis. After that I've noticed that filesystem of RAID 1 is missing in "Filesystem" tab:

RAID1 labeled Matrix is mounted and in clean state:

also I've checked that by ssh, I can see files on Matrix raid.
Basic commands to troubleshoot problem:

cat /proc/mdstat

Code

Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sde[1] sdd[0]
      1953383488 blocks super 1.2 [2/2] [UU]
      bitmap: 0/15 pages [0KB], 65536KB chunk


unused devices: <none>

blkid

Code

root@secure:/# blkid
/dev/sda1: LABEL="CACHE" UUID="a08721ac-0b40-4d34-8508-7550b76a803d" TYPE="ext4" PARTUUID="893c809b-01"
/dev/sdb2: UUID="d7446739-3636-4258-acef-4e44c1a374e2" TYPE="ext4" PARTUUID="64a507c7-361e-4c04-b4e2-aed8becdcb4c"
/dev/sdc1: LABEL="DataSSD" UUID="c26c316d-7469-45f0-b509-58eb516654bd" TYPE="ext4" PARTUUID="bff87c46-2a18-401f-a560-9d4e24208c4d"
/dev/sdd: UUID="df704e6d-b0ec-d791-5d09-09cdb0c6a6c3" UUID_SUB="17fdb3c3-ae58-f912-c38f-a3b06d0f7a24" LABEL="nas:Matrix" TYPE="linux_raid_member"
/dev/sde: UUID="df704e6d-b0ec-d791-5d09-09cdb0c6a6c3" UUID_SUB="a28b7c92-e3ed-1bbb-0467-55016d663085" LABEL="nas:Matrix" TYPE="linux_raid_member"
/dev/sdb1: PARTUUID="0cb69419-e832-4e3f-8f2d-7fd377871fc4"

fdisk -l | grep "Disk "

Code

root@secure:/# fdisk -l | grep "Disk "
Disk /dev/sda: 477 GiB, 512110190592 bytes, 1000215216 sectors
Disk identifier: 0x893c809b
Disk /dev/sdb: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Disk identifier: 0EBBA207-0B19-4F27-8BEC-70088765E75B
Disk /dev/sdc: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Disk identifier: 28024B9D-9A47-4130-9349-83B733347DCF
Disk /dev/sdd: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk /dev/md0: 1.8 TiB, 2000264691712 bytes, 3906766976 sectors
Disk /dev/sde: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors

cat /etc/mdadm/mdadm.conf

Code

root@secure:/# 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=nas:Matrix UUID=df704e6d:b0ecd791:5d0909cd:b0c6a6c3


# instruct the monitoring daemon where to send mail alerts
MAILADDR monitoring.backup.cloud@gmail.com
MAILFROM root

Alles anzeigen

mdadm --detail --scan --verbose

Code

root@secure:/# mdadm --detail --scan --verbose
ARRAY /dev/md0 level=raid1 num-devices=2 metadata=1.2 name=nas:Matrix UUID=df704e6d:b0ecd791:5d0909cd:b0c6a6c3
   devices=/dev/sdd,/dev/sde

uname -a

Code

root@secure:/# uname -a
Linux secure 4.13.0-0.bpo.1-amd64 #1 SMP Debian 4.13.13-1~bpo9+1 (2017-11-22) x86_64 GNU/Linux

omv-sysinfo

Code

= OS/Debian information
================================================================================
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 9.2 (stretch)
Release: 9.2
Codename: stretch


================================================================================
= openmediavault information
================================================================================
Release: 4.0.14-1
Codename: Arrakis

Alles anzeigen

Please help me to resolve this issue,
thank you in advance for every reply!

Mateusz

Beiträge von mateuxp

"Missing" RAID filesystem

"Missing" RAID filesystem

"Missing" RAID filesystem

"Missing" RAID filesystem

"Missing" RAID filesystem

"Missing" RAID filesystem

"Missing" RAID filesystem

"Missing" RAID filesystem

"Missing" RAID filesystem