"Missing" RAID filesystem

    • OMV 4.x (stable)

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

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

      Source Code

      1. # smartctl -a /dev/sde
      2. smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.13.0-0.bpo.1-amd64] (local build)
      3. Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
      5. === START OF INFORMATION SECTION ===
      6. Model Family: Western Digital Green
      7. Device Model: WDC WD20EZRX-00D8PB0
      8. Serial Number: WD-WCC4M0ZYTJH8
      9. LU WWN Device Id: 5 0014ee 20b50d5a6
      10. Firmware Version: 80.00A80
      11. User Capacity: 2,000,398,934,016 bytes [2.00 TB]
      12. Sector Sizes: 512 bytes logical, 4096 bytes physical
      13. Rotation Rate: 5400 rpm
      14. Device is: In smartctl database [for details use: -P show]
      15. ATA Version is: ACS-2 (minor revision not indicated)
      16. SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
      17. Local Time is: Tue Dec 19 22:40:05 2017 CET
      18. SMART support is: Available - device has SMART capability.
      19. SMART support is: Enabled
      23. smartctl -a /dev/sdd
      24. smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.13.0-0.bpo.1-amd64] (local build)
      25. Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
      27. === START OF INFORMATION SECTION ===
      28. Model Family: Western Digital Green
      29. Device Model: WDC WD20EZRX-00D8PB0
      30. Serial Number: WD-WCC4M5LES82D
      31. LU WWN Device Id: 5 0014ee 2b5fc2975
      32. Firmware Version: 80.00A80
      33. User Capacity: 2,000,398,934,016 bytes [2.00 TB]
      34. Sector Sizes: 512 bytes logical, 4096 bytes physical
      35. Rotation Rate: 5400 rpm
      36. Device is: In smartctl database [for details use: -P show]
      37. ATA Version is: ACS-2 (minor revision not indicated)
      38. SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
      39. Local Time is: Tue Dec 19 22:42:42 2017 CET
      40. SMART support is: Available - device has SMART capability.
      41. SMART support is: Enabled
      Display All

    • macom wrote:

      Is it advisable to down grade to an earlier kernel as the issue started with 4.13?
      This should workaround the problem according to those bug reports that took a deeper look. But of course it would be better if the problem would be identified and solved with recent kernel versions so the fix can be backported to 4.13 later.

      Threads/reports to watch:
      Besides that I've no idea whether a workaround in OMV is possible (not relying on blkid output -- but if I understood the bug reports correctly the problem is more severe than just cosmetical issues with one tool)

    • Just upgraded last night from a stable 3.x build (running for a LONG time with no issues) to 4.1.0.1).

      As others have stated - my md0 partition is not mounted or recognized.

      It is comprised of Qty 4 - WDC-WD30EFRX-68E drives.

      Output of udevadm info --query=property --name=/dev/md0

      DEVLINKS=/dev/disk/by-id/md-uuid-de9ec887:074a453e:f6ad3e13:8e8d12a6 /dev/disk/by-id/md-name-OMV2:HULK
      DEVNAME=/dev/md0
      DEVPATH=/devices/virtual/block/md0
      DEVTYPE=disk
      MAJOR=9
      MD_DEVICES=4
      MD_DEVICE_sdb_DEV=/dev/sdb
      MD_DEVICE_sdb_ROLE=0
      MD_DEVICE_sdc_DEV=/dev/sdc
      MD_DEVICE_sdc_ROLE=1
      MD_DEVICE_sdd_DEV=/dev/sdd
      MD_DEVICE_sdd_ROLE=2
      MD_DEVICE_sde_DEV=/dev/sde
      MD_DEVICE_sde_ROLE=3
      MD_LEVEL=raid5
      MD_METADATA=1.2
      MD_NAME=OMV2:HULK
      MD_UUID=de9ec887:074a453e:f6ad3e13:8e8d12a6
      MINOR=0
      SUBSYSTEM=block
      SYSTEMD_WANTS=mdmonitor.service
      TAGS=:systemd:
      USEC_INITIALIZED=6271534


      output of lsblk

      NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
      sda 8:0 0 37.3G 0 disk
      |-sda1 8:1 0 35.7G 0 part /
      |-sda2 8:2 0 1K 0 part
      `-sda5 8:5 0 1.6G 0 part [SWAP]
      sdb 8:16 0 2.7T 0 disk
      `-md0 9:0 0 8.2T 0 raid5
      sdc 8:32 0 2.7T 0 disk
      `-md0 9:0 0 8.2T 0 raid5
      sdd 8:48 0 2.7T 0 disk
      `-md0 9:0 0 8.2T 0 raid5
      sde 8:64 0 2.7T 0 disk
      `-md0 9:0 0 8.2T 0 raid5


      Has anyone come up with a fix or this???

      The information appears to still be there - and I do not want to risk losing everything - - any thoughts?

      results from "fsck /dev/md0"
      fsck from util-linux 2.29.2
      e2fsck 1.43.4 (31-Jan-2017)
      HULK: clean, 448820/274702336 files, 554503719/2197601280 blocks

      TIA

      George.

      The post was edited 1 time, last by ggibeau ().

    • You have a backup right? I would try reinstall with the drives in place. Be sure to let the install reboot on it's own, don't force it. Seems there are scripts running that if they don't finish can cause random problems.

      If you don't have space to do a backup and it is raid 1, you should be able to do the install with only one drive in the machine. Once it is up and working you can add the other drive back.

      Good luck
      If you make it idiot proof, somebody will build a better idiot.

    • It is Raid 5 with 4 drives. I do have a backup (I have this sync to another NAS for most of the files - but not all - - I know, bad planning on my part)

      I reinstalled with version 3.x - Array was still there - re-created SMB shares and added them as shared folders - and can access everything.

      Thanks

      The post was edited 1 time, last by ggibeau ().