Beiträge von Zerstoerer_

Zerstoerer_ · 6. März 2019

Everything seems to be normal, even after reboot.

@geaves Thank you again! Much appreciated

Zitat von tkaiser

touch /root/.test creates an empty file if not already existing and after a reboot you would check with ls -la /root/.test. We had a similar looking issue recently at a customer using a counterfeit USB pen drive to boot from where all writes went to nowhere. So as long as the server wasn't rebooted it seemed config changes were written to 'disk' but after a reboot everything was gone.
But this shouldn't apply to your M.2 SSD situation. BTW: I have the same Transcend SSD with 128 GB and when using extensively in an USB 'enclosure' like yours it badly overheats and throttles... (SMART temperature check revealed +80°C)

"NAS-only-usage" should be fine temperature-wise (only little writing+reading) ?
Otherweise do you suggest another solution for my OS?

Output of ls -la /root/.test

Code

-rw-r--r-- 1 root root 0 Mär  4 16:54 /root/.test

Seems to be ok !?

Zerstoerer_ · 4. März 2019

Zerstoerer_ · 4. März 2019

Ok, it's recovering now. I hope this resolves the issue.

I will let you know when its done.

Thank you for your time and patience.

Zerstoerer_ · 4. März 2019

wipefs -n /dev/sda

Code

offset               type
----------------------------------------------------------------
0x200                gpt   [partition table]

Zerstoerer_ · 4. März 2019

I might have found the mistake !?

It says sda1 in blkid

Code

/dev/sdb: UUID="430dadae-5f1c-40c9-c3a5-a8d515749f6c" UUID_SUB="945f5477-7c7f-97b5-cf6d-60701af938fb" LABEL="openmediavault:SimonsNAS" TYPE="linux_raid_member"
/dev/sdc: UUID="430dadae-5f1c-40c9-c3a5-a8d515749f6c" UUID_SUB="921d4d34-4ee0-dc0a-1ef0-6c014035953c" LABEL="openmediavault:SimonsNAS" TYPE="linux_raid_member"
/dev/md127: LABEL="Raid5" UUID="4ba52b0b-c03f-4854-964f-a18ca8bcebe4" TYPE="ext4"
/dev/sdd: UUID="430dadae-5f1c-40c9-c3a5-a8d515749f6c" UUID_SUB="177204c9-dfb9-f78c-725b-b9861fe857b6" LABEL="openmediavault:SimonsNAS" TYPE="linux_raid_member"
/dev/sde1: UUID="4bc0abc4-ac0f-4814-a4f4-e51213828b15" TYPE="ext4" PARTUUID="0286303e-01"
/dev/sde5: UUID="02284066-1848-411d-9a57-7d952e67d8a7" TYPE="swap" PARTUUID="0286303e-05"
/dev/sda1: PARTUUID="69221752-7171-483e-a28f-ae7d83f81caf"

Zerstoerer_ · 4. März 2019

mdadm --zero-superblock /dev/sda

Code

mdadm: Unrecognised md component device - /dev/sda

Zerstoerer_ · 4. März 2019

Seemed to work nonetheless!

mdadm --detail /dev/md127

Code

root@openmediavault:~# mdadm --detail /dev/md127
/dev/md127:
        Version : 1.2
  Creation Time : Mon Oct  8 21:07:22 2018
     Raid Level : raid5
     Array Size : 29298917376 (27941.63 GiB 30002.09 GB)
  Used Dev Size : 9766305792 (9313.88 GiB 10000.70 GB)
   Raid Devices : 4
  Total Devices : 3
    Persistence : Superblock is persistent


  Intent Bitmap : Internal


    Update Time : Mon Mar  4 17:27:49 2019
          State : active, degraded
 Active Devices : 3
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 0


         Layout : left-symmetric
     Chunk Size : 512K


           Name : openmediavault:SimonsNAS  (local to host openmediavault)
           UUID : 430dadae:5f1c40c9:c3a5a8d5:15749f6c
         Events : 49241


    Number   Major   Minor   RaidDevice State
       0       8       16        0      active sync   /dev/sdb
       1       8       32        1      active sync   /dev/sdc
       2       8       48        2      active sync   /dev/sdd
       -       0        0        3      removed

Alles anzeigen

Zerstoerer_ · 4. März 2019

Result of omv-mkconf mdadm

and

cat /etc/mdadm/mdadm.conf

Code

# definitions of existing MD arrays
ARRAY /dev/md/SimonsNAS metadata=1.2 name=openmediavault:SimonsNAS UUID=430dadae:5f1c40c9:c3a5a8d5:15749f6c

Doesn't sound like md127 ?

Zerstoerer_ · 4. März 2019

cat /etc/mdadm/mdadm.conf

Code

# 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
INACTIVE-ARRAY /dev/md0 metadata=1.2 name=openmediavault:SimonsNAS UUID=430dadae:5f1c40c9:c3a5a8d5:15749f6c


# instruct the monitoring daemon where to send mail alerts
MAILADDR xxx_xxx@xxx.de

Alles anzeigen

Zerstoerer_ · 4. März 2019

Zitat von tkaiser

Just to be sure. If you create a file with touch /root/.test does this file survive a reboot?

How do i check, if the file has survived ?

Should there be an output after touch /root/.test ?

Zerstoerer_ · 4. März 2019

Yes, should be sda.

But why removed ? I have just shut down my system and then restarted it.

mdadm --zero-superblock /dev/sda

Code

root@openmediavault:~# mdadm --zero-superblock /dev/sda
mdadm: Unknown keyword INACTIVE-ARRAY
mdadm: Unrecognised md component device - /dev/sda

Zerstoerer_ · 4. März 2019

Zitat von tkaiser

Is your OS drive sde an USB thumb drive?

Im using this as OS drive:
https://www.amazon.de/gp/produ…&linkCode=as2&tag=tean-21 https://www.amazon.de/gp/produ…&linkCode=as2&tag=tean-21

https://www.amazon.de/SIENOC-S…lei-Adapter/dp/B00ENH93DQ

Zerstoerer_ · 4. März 2019

Code

root@openmediavault:~# mdadm --detail /dev/md127
mdadm: Unknown keyword INACTIVE-ARRAY
/dev/md127:
        Version : 1.2
  Creation Time : Mon Oct  8 21:07:22 2018
     Raid Level : raid5
     Array Size : 29298917376 (27941.63 GiB 30002.09 GB)
  Used Dev Size : 9766305792 (9313.88 GiB 10000.70 GB)
   Raid Devices : 4
  Total Devices : 3
    Persistence : Superblock is persistent


  Intent Bitmap : Internal


    Update Time : Mon Mar  4 16:10:38 2019
          State : clean, degraded
 Active Devices : 3
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 0


         Layout : left-symmetric
     Chunk Size : 512K


           Name : openmediavault:SimonsNAS  (local to host openmediavault)
           UUID : 430dadae:5f1c40c9:c3a5a8d5:15749f6c
         Events : 36685


    Number   Major   Minor   RaidDevice State
       0       8       16        0      active sync   /dev/sdb
       1       8       32        1      active sync   /dev/sdc
       2       8       48        2      active sync   /dev/sdd
       -       0        0        3      removed

Alles anzeigen

Zerstoerer_ · 4. März 2019

Code

root@openmediavault:~# mdadm --detail /dev/md0
mdadm: Unknown keyword INACTIVE-ARRAY
mdadm: cannot open /dev/md0: No such file or directory

Zerstoerer_ · 4. März 2019

I can't remember if i have wiped the new drive.

1. cat /proc/mdstat

Code

Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md127 : active raid5 sdd[2] sdc[1] sdb[0]
      29298917376 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/3] [UUU_]
      bitmap: 5/73 pages [20KB], 65536KB chunk

2. blkid

Code

/dev/sdb: UUID="430dadae-5f1c-40c9-c3a5-a8d515749f6c" UUID_SUB="945f5477-7c7f-97b5-cf6d-60701af938fb" LABEL="openmediavault:SimonsNAS" TYPE="linux_raid_member"
/dev/sdd: UUID="430dadae-5f1c-40c9-c3a5-a8d515749f6c" UUID_SUB="177204c9-dfb9-f78c-725b-b9861fe857b6" LABEL="openmediavault:SimonsNAS" TYPE="linux_raid_member"
/dev/sdc: UUID="430dadae-5f1c-40c9-c3a5-a8d515749f6c" UUID_SUB="921d4d34-4ee0-dc0a-1ef0-6c014035953c" LABEL="openmediavault:SimonsNAS" TYPE="linux_raid_member"
/dev/sde1: UUID="4bc0abc4-ac0f-4814-a4f4-e51213828b15" TYPE="ext4" PARTUUID="0286303e-01"
/dev/sde5: UUID="02284066-1848-411d-9a57-7d952e67d8a7" TYPE="swap" PARTUUID="0286303e-05"
/dev/md127: LABEL="Raid5" UUID="4ba52b0b-c03f-4854-964f-a18ca8bcebe4" TYPE="ext4"
/dev/sda1: PARTUUID="69221752-7171-483e-a28f-ae7d83f81caf"

Zerstoerer_ · 4. März 2019

GUI Raid state: clean, degraded

Zerstoerer_ · 4. März 2019

I thought I already grew the Raid..

It took about 2 days to grew the Raid after adding the new device...

Zerstoerer_ · 4. März 2019

It worked, ist back up with 3 drives...

Code

mdadm: Unknown keyword INACTIVE-ARRAY
mdadm: looking for devices for /dev/md0
mdadm: Merging with already-assembled /dev/md/SimonsNAS
mdadm: /dev/sdb is identified as a member of /dev/md/SimonsNAS, slot 0.
mdadm: /dev/sdc is identified as a member of /dev/md/SimonsNAS, slot 1.
mdadm: /dev/sdd is identified as a member of /dev/md/SimonsNAS, slot 2.
mdadm: /dev/sdc is already in /dev/md/SimonsNAS as 1
mdadm: added /dev/sdd to /dev/md/SimonsNAS as 2
mdadm: no uptodate device for slot 3 of /dev/md/SimonsNAS
mdadm: /dev/sdb is already in /dev/md/SimonsNAS as 0
mdadm: /dev/md/SimonsNAS has been started with 3 drives (out of 4).

Alles anzeigen

Zerstoerer_ · 4. März 2019

Result of $ omv-mkconf mdadm

Code

update-initramfs: Generating /boot/initrd.img-4.19.0-0.bpo.2-amd64
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.

Zerstoerer_ · 4. März 2019

Hello everyone,

my Raid5 went missing after adding a new disk to it.

Before growing: 3x disk 10TB
After growing: 4x disk 10TB

I added the new disk with
mdadm --add /dev/md0 /dev/sda

--> somehow the new disk showed up as sda !?

and grew the Raid with
mdadm --grow --raid-devices=4

Everything went fine. My Raid grew and the new storage space showed up in the WebGUI.

I copied some files to it an shut it down.

After rebooting my Raid went missing. I have no idea what went wrong.

I hope you can help me. Thank you very much!

Release: 4.1.19-1
Codename: Arrakis

Output results:

1. cat /proc/mdstat

Code

Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : inactive sdb[0](S) sdd[2](S) sdc[1](S)
      29298921984 blocks super 1.2


unused devices: <none>

2. blkid

Code

/dev/sdb: UUID="430dadae-5f1c-40c9-c3a5-a8d515749f6c" UUID_SUB="945f5477-7c7f-97b5-cf6d-60701af938fb" LABEL="openmediavault:SimonsNAS" TYPE="linux_raid_member"
/dev/sdd: UUID="430dadae-5f1c-40c9-c3a5-a8d515749f6c" UUID_SUB="177204c9-dfb9-f78c-725b-b9861fe857b6" LABEL="openmediavault:SimonsNAS" TYPE="linux_raid_member"
/dev/sdc: UUID="430dadae-5f1c-40c9-c3a5-a8d515749f6c" UUID_SUB="921d4d34-4ee0-dc0a-1ef0-6c014035953c" LABEL="openmediavault:SimonsNAS" TYPE="linux_raid_member"
/dev/sde1: UUID="4bc0abc4-ac0f-4814-a4f4-e51213828b15" TYPE="ext4" PARTUUID="0286303e-01"
/dev/sde5: UUID="02284066-1848-411d-9a57-7d952e67d8a7" TYPE="swap" PARTUUID="0286303e-05"
/dev/sda1: PARTUUID="69221752-7171-483e-a28f-ae7d83f81caf"

3. fdisk -l | grep "Disk "

Code

Disk /dev/sdb: 9,1 TiB, 10000831348736 bytes, 19532873728 sectors
Disk /dev/sdd: 9,1 TiB, 10000831348736 bytes, 19532873728 sectors
Disk /dev/sda: 9,1 TiB, 10000831348736 bytes, 19532873728 sectors
Disk identifier: 460B81D3-EA0D-4E21-ABD4-92B84661D883
Disk /dev/sdc: 9,1 TiB, 10000831348736 bytes, 19532873728 sectors
Disk /dev/sde: 59,6 GiB, 64023257088 bytes, 125045424 sectors
Disk identifier: 0x0286303e

4. cat /etc/mdadm/mdadm.conf

Code

#
# 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:SimonsNAS UUID=430dadae:5f1c40c9:c3a5a8d5:15749f6c


# instruct the monitoring daemon where to send mail alerts
MAILADDR *****_******@web.de

Alles anzeigen

5. mdadm --detail --scan --verbose

Code

INACTIVE-ARRAY /dev/md0 num-devices=3 metadata=1.2 name=openmediavault:SimonsNAS UUID=430dadae:5f1c40c9:c3a5a8d5:15749f6c
   devices=/dev/sdb,/dev/sdc,/dev/sdd

Beiträge von Zerstoerer_

RAID5 missing after adding disk

RAID5 missing after adding disk

RAID5 missing after adding disk

RAID5 missing after adding disk

RAID5 missing after adding disk

RAID5 missing after adding disk

RAID5 missing after adding disk

RAID5 missing after adding disk

RAID5 missing after adding disk

RAID5 missing after adding disk

RAID5 missing after adding disk

RAID5 missing after adding disk

RAID5 missing after adding disk

RAID5 missing after adding disk

RAID5 missing after adding disk

RAID5 missing after adding disk

RAID5 missing after adding disk

RAID5 missing after adding disk

RAID5 missing after adding disk

RAID5 missing after adding disk