Posts by Mat-Moo

That worked for me as well after replacing 2TB drives (1 at a time then rebuilding) with 4TB, but didn't get any extra space - Thanks, not have 7.28TB instead of 3.1TB! Woohoo

Think I have this sorted - first fail the dick

mdadm --manage /dev/mdXXX --fail /dev/sdX

Where XXX is the raid IS and X is the disk ID - in my case "127" and "d" - This put the raid into a failed state, shut down the system, replaced the disk, then ran the recovery to rebuild.

I've got a Raid 5, which originally was 3 x 2TB disks - One disk failed, so I replaced it with a 4TB thinking thinking that at some stage I could upgrade the others to give me more space. I bought a couple of new disks about 6 months ago so thought about time to upgrade another disk, then after rebuild the last disk and then grow it. Problem is, if I just rip out the disk then the raid management then shows nothing at all, so I can't rebuild or do anything? After some advise - Current detail of raid below:-

Version : 1.2
Creation Time : Mon Dec 31 11:54:40 2012
Raid Level : raid5
Array Size : 3907025920 (3726.03 GiB 4000.79 GB)
Used Dev Size : 1953512960 (1863.02 GiB 2000.40 GB)
Raid Devices : 3
Total Devices : 3
Persistence : Superblock is persistent


Update Time : Wed Oct 21 21:26:44 2020
State : clean
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0


Layout : left-symmetric
Chunk Size : 512K


Name : CowShed:Udders
UUID : 1c5ae26a:1c6abeac:888454b5:02badf80
Events : 19847

Number Major Minor RaidDevice State

0 8 16 0 active sync /dev/sdb

3 8 32 1 active sync /dev/sdc

2 8 48 2 active sync /dev/sdd

So didn't get anywhere with this, so ended up disabling onboard raid... then it worked fine!!! Using software raid anyway so no loss, but still don't know why it changed.

A Picture tells a thousand words (so they say) - So my OMV won't boot, so I created a rescue USB http://www.system-rescue-cd.org/ and booted off of that. I can then mount and view the disk and it looks fine, even reinstall grub and check the boot partition... but still refusing to boot. Any ideas?

I't s HP Gen 8 microserver, first bay is 250gb disk for boot / system then other 3 disks are data (currently removed just in case!!)

Hmmm at a loss disk is there I can boot of a livecd and see everything but not booting from it at all. And all I get when I try a livecd is that the grub commands don't exist. ALmost quicker to just reinstall!

No bootable media...

Not really sure what's happened, but had some funnies so did an update and all seemed ok (except my xbox wouldn't talk to plex) so rebooted.... but it won't reboot, looks like grub is missing or something as disk seems ok. How do I sort/fix/repair the grub?

OK well, went for it, moved all 3 raid disks from one to the other, keeping them in the same order, and raid was seen all correctly on the gen 8! However 1 disk has now decided it doesn't like working any more... grrr.

I've had a Gen 8 micro server sitting around for a couple of months due to no time, but today was a day I had time!
Current NL54 setup - 30GB ssd boot/os drive (sda) , 3 x 2TB disks in raid 5, running OMV 2.
New Gen8 - 256GB HDD (sda, might swap to the above ssd once all running) running OMV 3. The Gen8 is a far more complex BIOS then the NL54 (which is just a PC), and I don't have the capacity to backup 4TB of data at present unless I buy a 4TB drive just to backup on. I had to make a single disk raid just to see a boot disk!

Whats the best way to move and rebuild the array without losing anything?

All advise welcome

So I’ve just bought. Hp gen8 server to replace my old nl54 (decided on 8 as I can upgrade cpu)... I’ve had a quick search and the impression I can get is that I can swap all the disks around and should be good? Seems a bit too easy? Currently I’ve a ssd boot drive in the nl54 and 4 x 1tb drives running as 1 (software raid I think).

Advice welcome before I lose everything

Plexmediaserver update problems
This worked for me as well!

Ok, so been able to play less and less recently with my plex media server (1.03.2461) so ran "Sudo apt-get update/upgrade" to update and got to version 1.5... but still had a DEB download of 1.8 I could access. So downloaded this to the server and ran sudo dpkg -i plexmediaserver... and chose to keep my current config, and it all died and I don't know what to do ? SOS!:)

I can't seem to get or see any upgrades from the OMV web portal? Is there anything on command line I can do to kick an upgrade or clear cache for updates to latest 2.x?

Wiped and re-installed, quicker

So? Just re-install from USB? Or any chance of getting this running?

8.2
(Thanks)

Was paying a quick visit to my parents to copy a few bits *cough* and decided to do an upgrade while I was there.... bad move I've tried lots of stuff and now if I use apt-get install openmediavault it fails with unmet dependencies :-
php5-pam
proftpd-mod-vroot
php-proctitle

Unable to correct problems, you have broken packages

Really ballsed this up HELP! (Please)

Used the uninstall - log
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be REMOVED:
avahi-utils* openmediavault-plexmediaserver* plexmediaserver*
0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
After this operation, 234 kB disk space will be freed.
(Reading database ... 30544 files and directories currently installed.)
Removing openmediavault-plexmediaserver ...
Purging configuration files for openmediavault-plexmediaserver ...
Removing plexmediaserver ...
Plex Media Server is not running (no process found)...
update-rc.d: using dependency based boot sequencing
Purging configuration files for plexmediaserver ...
Removing user `plex' ...
Warning: group `nogroup' has no more members.
Done.
Removing avahi-utils ...
Processing triggers for openmediavault ...
Restarting engine daemon ...
Processing triggers for man-db ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
Creating index of upgradeable packages ...
Creating index of OpenMediaVault plugins ...
Done ...

Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
avahi-utils plexmediaserver
The following NEW packages will be installed:
avahi-utils openmediavault-plexmediaserver plexmediaserver
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 108 MB of archives.
After this operation, 234 kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
avahi-utils plexmediaserver openmediavault-plexmediaserver
Authentication warning overridden.
Get:1 http://dh2k.omv-extras.org/debian/ plex-wheezy-mirror/main plexmediaserver i386 0.9.11.7.803-87d0708-debian [108 MB]
Get:2 http://packages.omv-extras.org/debian/ kralizec-plex/main openmediavault-plexmediaserver all 1.0.9 [21.0 kB]
Get:3 http://ftp.uk.debian.org/debian/ stable/main avahi-utils i386 0.6.31-2 [56.9 kB]
Fetched 108 MB in 27s (3882 kB/s)
Selecting previously unselected package avahi-utils.
(Reading database ... 26528 files and directories currently installed.)
Unpacking avahi-utils (from .../avahi-utils_0.6.31-2_i386.deb) ...
Selecting previously unselected package plexmediaserver.
Unpacking plexmediaserver (from .../plexmediaserver_0.9.11.7.803-87d0708-debian_i386.deb) ...
Selecting previously unselected package openmediavault-plexmediaserver.
Unpacking openmediavault-plexmediaserver (from .../openmediavault-plexmediaserver_1.0.9_all.deb) ...
Processing triggers for man-db ...
Processing triggers for openmediavault ...
Restarting engine daemon ...
Setting up avahi-utils (0.6.31-2) ...
Setting up plexmediaserver (0.9.11.7.803-87d0708-debian) ...
update-rc.d: using dependency based boot sequencing
Plex Media Server is not running (no process found)...
Starting Plex Media Server: done
Setting up openmediavault-plexmediaserver (1.0.9) ...
Initialize configuration
Processing triggers for openmediavault ...
Updating locale files ...
Updating file permissions ...
Purging internal cache ...
Restarting engine daemon ...
Creating index of upgradeable packages ...
Creating index of OpenMediaVault plugins ...
Done ...

All working fine this time?!!

As to what I did before, I did have some issues as I ran the installer off an old build and had no network, so took a while to get it all updated and running. But then simply installed 3rd party plugins and installed as usual The only other thing was that when I installed it I had no 3tb drive in there, only an os drive... maybe I started plex to early and the media library failed or got confused as there was no save location, not sure.

Just states "Starting plex media server: done" - but the services tab shows a red dot, and /etc/init/d/plexmediaserver status says it's not running... even the logs are not updating - I must of screwed something up, might need to remove it and reinstall.