Noob how to backup and replace OS drive

1. Quite a number of users have their boot drive on a 16gig stick with plenty of change left over. If you can’t keep your boot drive on a 32gig stick, you’re doing something wrong.
2. I am not sure what you mean by backing up your operating system to your RAID array. The best and easiest OS backup involves two 32gig USB thumb drives and the dd command.

Zitat von Agricola

1. Quite a number of users have their boot drive on a 16gig stick with plenty of change left over. If you can’t keep your boot drive on a 32gig stick, you’re doing something wrong.
2. I am not sure what you mean by backing up your operating system to your RAID array. The best and easiest OS backup involves two 32gig USB thumb drives and the dd command.

I would 100% agree w/ this. I have quite a bit going on on my server and my root partition is about 3 gigs.

Zitat von CraigG

Please can someone give me a total Noddy guide as to how to:-

a:- clone my OS drive so that I can swap out for a larger card

There's a little primer on preparing flash media to be a boot drive - here. Then look - here for guidance on cloning boot drives. You may find other topics useful in this guide as well.

I'm sorry. I could have been a bit more helpful above. There may very well be issues with your boot drive filling up with docker files or a rsync job going to the boot drive because of a missing data drive, etc. You might describe what you are doing with your OMV install, and what kind of hardware you are using. But crashtest is on target just above. Verifying the integrity of your media before you commit your operating system to it, and backing up your system as soon as you get it up and running, and then at every major os update is a must if you want to avoid headaches later on. Both Mac and Linux there are tons of guides on the internet for using the dd command to backup a sd card or usb thumb drive. Here are a couple: Mac   Linux For Windows It's something else. crashtest has a good guide for that in his Getting Started guide in the guides section of the forum. Hope that helps.

Zitat von CraigG

Thank you all. Some more info. I have a HP DL380P its an old 12 bay server with 2 xeon processors. It has 12 disks in forming a snapraid array with unionfilesystem to make it 1 drive. All of the familys photos, music, movies and images of laptops are stored on it. It is also running plex.

OMV is running from a 32GB high endurance SD card. The flash memory plugin has also been used.

When I look in "File Systems" I can see /dev/sdo1 in ext4 filesystem which is my SD card, with Total space 21.29GiB; 7.39GiB available and 12.79GiB used. I can also see /dev/sdo5 which is swap file system.

I've used the du command to look at folder sizes.

My /var/log folder is 5.4G which I'm guessing it rather large and ./daemon.log.1 is 3.8G on its own. with /daemon.log being 805M and /syslog.1 being 555M.

My /var/folder2ram is 6.8G. Digging down this a little the /var/folder2ram/var/log folder is all of this.

Do I have a logging problem, can I clear all the logs? How do I clear all the logs?

Thank you all

Alles anzeigen

I'd be looking at your logs. Something is obviously getting written a LOT to have a log folder that size.

Some perspective....

Filesystem Size Used Avail Use% Mounted on

/dev/sdc1 51G 3.7G 45G 8% /

root@openmediavault:~#

I have to say, I haven't heard of or seen or a case with "gig's of log files". That's a LOT of logs. On the other hand, if you haven't relocated the Plex metadata base, several gig's of metadata is not uncommon.

Deleting Logs? Never had to do it but the deamon.log appears to have entries RE mounting hard drives and, with 12 drives, you have a lot going on. Here's a -> command line method but that may be a bit complicated.

I believe the easiest way to purge old logs would be to use the GUI:

Under Diagnostics, System Logs, in the Logs tab, there's a drop down arrow on the right. Select the Daemon log and click the Clear button. (Given the size of your logs, it might take some time to complete.)

Run du again to check it out. (The Daemon log will, pretty much, instantly begin to repopulate but it should far smaller.)

You can do the same to trim a number of other logs, in this location. I'd start with this first.

Have you changed your docker storage path from the default?

In folder-to-ram (or any log file), there's no penalty for deleting compressed log file archives. *log.gz

If you have big primary log files *.log or *.log1, and if you have WinSCP installed, you can open the file by double clicking it. Once inside the file, Cntrl+A selects all, the delete key clears it, then save it (upper left hand corner).