Beiträge von GTvert90

So I'm changing over from RAID5 to UnionFS and eventually snapraid.
I made a pool from the UFS plugin pooling some empty 4tb drives, copied a bunch of data from my backup drives, and now I added another drive to the pool that has a lot of content on it. I structured the file system the same way, /Media/TV Shows and while the SMB share shows all the data there if I search that drive specifically, The Pool share does not show any of that data from the newly pooled drive.

Is there something I need to do to sync? Should I delete the pool and readd it with all the drives? In the GUI the filesystem shows the proper amount of storage and space used in the pool. I have already rebooted the system to properly remount the drives.

just changing the user for my plex docker was enough to get it going. no idea why it had a mishap after rebooting. I still would like to get my permissions set properly so I don't have issues in the future. I've been meaning to make a thread about it because I played around with the ACL's so much to get plex working the first time.

I'll change my plex to the same user as the files owner. whats the best way to fix this? under the options given under reset permissions I don't see an option to select between directories and files. just shared folders.

and also why did this creep up after the power loss and reboot?

I've always been confused by permissions and such

100 1002 for plex

100 1000 for files

one folder inside my tv sub folder is 2774 another the tv folder is 2774 and the file I'm trying to play is 0777 another file is 0674

I'd like to get this set up properly whats my next step reset acl? reset permissions? Do i need to run plex as 100 1000?

Power went out today and my server ran out of battery. Booted it back up RAID is clean, file systems are all mounted. Plex shows the media but tells me the drive isn't mounted when I go to play it...

it worked just fine before all this. I can access the files via windows explorer and play so the files okay. I'm assuming i'm having a permission issue and honestly I had permission issues when i set up the docker after OMV5 upgrade. I had to reset and play around with permissions and acl's to get it to work properly and I'm pretty sure I have a mess of permissions that I should straighten up.

HELP

Thanks!

From my research the M.2 slot will only with with UEFI and UEFI sometimes causes issues with OMV is this correct? I just put one in my desktop and it may be a placibo affect but i swear boot and loading times are much better.

I really only use OMV for plex. and I partition my SSD for the OS on one part and a data partition for plex and whatever other databases I may encounter. Will a see a big difference between a regular SATA SSD and a M.2 NMVe SSD?

Trying to plan for the upgrade from omv4 to 5. My Biggest thing is I want to keep my plex database in tact. Would I just backup the database, then restore to the new location once the docker is set up? I should be able to keep the files on the data partition of the SSD and only install the update on the os portion right? I of course would have a backup of the whole SSD just in case.

Right now I have my SSD partitioned for my OS and the rest is for docker / plex / whatever.

Yes! IDK how i didn't find that sooner LOL thank you!

I've been messing around with Virtualbox. I've tried installing Windows and Ubuntu. Windows it shows the ISO is running in the preview box.. trouble is clicking on console doesn't do anything but give me a blank popup. Through my searches I've found this is a common problem because java has been depreciated or something of the sort. trouble is i can't remote in to get it installed. I set network up with bridge to bond0 and it won't give it an IP just 127.0.0.1 or something of the sort. I've been searching my butt off. Any ideas?

It will be done rebuilding in about 20 min. It's currently clean degraded and recovering but yes everything is where it should be.

Zitat von geaves

why, I said in post 11 that you cannot hot swap the drives!!

When you say you've got it going can you you explain? That thread is different to what you have done.

I think we were using the term hotswap. I was probably using it wrong. I was using the term as in can I pull the drive out and insert a new one without shutting OMV off. so it didn't even occur to me until it was too late that I might need to remove the disk from the raid before I shut down and pull the disk.

mdadm --assemble --verbose --force /dev/md127 /dev/sd[abcdef] is what got the array to show for me. i then wiped the new drive and rebuilt the array.

got it up and going with this
https://forum.openmediavault.o…er-upgrade-to-OMV-4-1-22/
but I haven't ran any fstab or config to figure out that part. is it necessary ? lol

root@openmediavault:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md127 : inactive sde[7](S) sdb[6](S) sdf[1](S) sda[4](S) sdc[9](S) sdd[8](S)
      23441343504 blocks super 1.2


unused devices: <none>
root@openmediavault:~# blkid
/dev/sdh1: UUID="00891412-6ed1-43cb-8460-761ebfaf9786" TYPE="ext4" PARTUUID="f9c061ab-01"
/dev/sdh3: LABEL="SSD Data" UUID="7a981dd3-4c7d-4f1c-9002-050b1a7a57e0" TYPE="ext4" PARTUUID="f9c061ab-03"
/dev/sdh5: UUID="fbfec248-cf4c-4069-9fa1-49aac24c64fa" TYPE="swap" PARTUUID="f9c061ab-05"
/dev/sdb: UUID="7a39528f-fab6-6321-dc1e-d267566f9251" UUID_SUB="8d952e8f-dc6c-b800-3454-9ffd5769255c" LABEL="openmediavault:Media" TYPE="linux_raid_member"
/dev/sda: UUID="7a39528f-fab6-6321-dc1e-d267566f9251" UUID_SUB="75bdbcd6-6039-80d9-d718-adce02a77dd1" LABEL="openmediavault:Media" TYPE="linux_raid_member"
/dev/sdd: UUID="7a39528f-fab6-6321-dc1e-d267566f9251" UUID_SUB="83372978-ed2d-7122-5ffd-550b979ceefc" LABEL="openmediavault:Media" TYPE="linux_raid_member"
/dev/sde: UUID="7a39528f-fab6-6321-dc1e-d267566f9251" UUID_SUB="6cf55581-47cd-73d4-a16f-48ea65219772" LABEL="openmediavault:Media" TYPE="linux_raid_member"
/dev/sdf: UUID="7a39528f-fab6-6321-dc1e-d267566f9251" UUID_SUB="f5a1474f-cb09-a4a8-72c1-87b2655d31e4" LABEL="openmediavault:Media" TYPE="linux_raid_member"
/dev/sdg2: LABEL="Media" UUID="381CCEC11CCE7A00" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="1c3cd474-4d84-4d90-99e7-ef3414d9e3ef"
/dev/sdc: UUID="7a39528f-fab6-6321-dc1e-d267566f9251" UUID_SUB="161974ea-c3a4-5990-9357-f1e19ee4834f" LABEL="openmediavault:Media" TYPE="linux_raid_member"
/dev/sdg1: PARTLABEL="Microsoft reserved partition" PARTUUID="e547ec55-66dc-458a-b5a6-f0e1f495511f"
root@openmediavault:~# fdisk -l | grep "Disk "
Partition 1 does not start on physical sector boundary.
Disk /dev/sdh: 223.6 GiB, 240057409536 bytes, 468862128 sectors
Disk identifier: 0xf9c061ab
Disk /dev/sdb: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk /dev/sda: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk /dev/sdd: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk /dev/sde: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk /dev/sdf: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk /dev/sdg: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk identifier: CEFD4E7C-3CBB-4C51-9BFE-04C2E0F38E82
Disk /dev/sdc: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
root@openmediavault:~# 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/md127 metadata=1.2 name=openmediavault:Media UUID=7a39528f:fab66321:dc1ed267:566f9251


# instruct the monitoring daemon where to send mail alerts
MAILADDR droptopfox90@gmail.com
MAILFROM rootroot@openmediavault:~# mdam --detail --scan --verbose
-bash: mdam: command not found
root@openmediavault:~# mdadm --detail --scan --verbose
INACTIVE-ARRAY /dev/md127 num-devices=6 metadata=1.2 name=openmediavault:Media UUID=7a39528f:fab66321:dc1ed267:566f9251
   devices=/dev/sda,/dev/sdb,/dev/sdc,/dev/sdd,/dev/sde,/dev/sdf
root@openmediavault:~#

Here's all this info for you. should I make a new thread? I feel like I'm a simple command away from it working. lol

I've shut down the system for now.

Zitat von geaves

No, not with mdadm, there are a few threads on the forum where users have 'tested' a failure by simply pulling a drive, on reboot the raid comes back as inactive and has to be reassembled, then it will appear as clean degraded, they have to go through the process that you have just done.
Sorry yes the info looks OK the raid is back to normal.

So I shut down. removed the bad drive, put a good drive in powered it on and it shows all my disks but I have nothing under RAID. It doesn't show any arrays Ideas?

Thank you! I'll swap the failing drive out later. I appreciate the help

Sent from my Pixel 3 XL using Tapatalk

Zitat von geaves

Ah! it could be one of these they can cause havoc sometimes

Turn off the Raid notification, Save, Apply, then re enable it see if that sorts it out.

Done. Ill let you know.

everything in the info looks good? Can drives be hot swapped?

sdg is throwing a smart error and needs to be swapped out. I'm just nervous to do so without knowing the array is stable