My system disk is full again

patrick168 · 14. März 2015

The system disk of my backup machine is full again - the second time. I found that it was caused the data disk couldn't be mounted at startup, and so backup files were copied directly to system disk under /media/<uuid>.

Is there a way that I can make a small media partition say 2G in the disk and have the /media directory directed to this partition as OMV's mounting points? In case the data disk cannot be mounted the next time, it will only fill up the 2G media partition and won't affect the system disk.

Suggestion would be appreciated, thanks.

subzero79 · 14. März 2015

Never though of this. But I have no idea how to make it in order so that media mounts first then the data disks.

Whats the reason of the disk not mounting at startup? i would try to debug that first

davidh2k · 14. März 2015

Zitat von subzero79

But I have no idea how to make it in order so that media mounts first then the data disks.

Thats no problem, the entry just has to be above the entries generated by OpenMediaVault.

Also, very good idea. I'll play around with that idea...

Edit: Is that an external drive?

Greetings
David

davidh2k · 14. März 2015

Code

root@Chap ~ # df -h
Dateisystem                                            Größe Benutzt Verf. Verw% Eingehängt auf
rootfs                                                   28G     16G   12G   58% /
udev                                                     10M       0   10M    0% /dev
tmpfs                                                   390M    516K  389M    1% /run
/dev/disk/by-uuid/acb181a6-f386-4cf4-af60-fa153067f727   28G     16G   12G   58% /
tmpfs                                                   5,0M    4,0K  5,0M    1% /run/lock
tmpfs                                                   1,6G    836K  1,6G    1% /run/shm
/dev/sda3                                               434G    293G  142G   68% /opt
/dev/loop0                                              454M     12M  415M    3% /media
[...]
/dev/sdb1                                                11T     11T  102G  100% /media/d3c21c66-af4b-41d4-b098-462e83fa641d
/dev/sdc1                                               1,4T    471G  926G   34% /media/ca425484-1be3-47f1-b7bb-8f0785c9ea5b
/dev/sdb1                                                11T     11T  102G  100% /export/Comedy
/dev/sdb1                                                11T     11T  102G  100% /export/Filme
/dev/sdb1                                                11T     11T  102G  100% /export/Serien
/dev/sdc1                                               1,4T    471G  926G   34% /export/Sammy1
root@Chap ~ #

Alles anzeigen

Greetings
David

patrick168 · 14. März 2015

Hi Subzero, it should be a contact problem, I cleaned the SATA sockets with alcohol this time but I just want to prevent it from filling up the system disk in case it happens again.

Hi David, please let me know if you have a solution on this? Thanks.

davidh2k · 14. März 2015

@patrick168 look at the output above.

Greetings
David

subzero79 · 14. März 2015

Then you should work around systemrescuecd to make the partition and modify fstab as @davidh2k points to assign media path to a partition on startup

davidh2k · 14. März 2015

We need to do a little more than just that. Gimme a couple of minutes to write it down.

Greetings
David

patrick168 · 14. März 2015

Sorry that I ain't very good at programming, should I be using "mount -o loop /dev/sdc2 /media" to mount assuming that the media partition is sdc2. Also where should this command be saved if it has to be auto-mounted at startup. Thanks.

Code

root@N40L-B:~# df -h
Filesystem                                              Size  Used Avail Use% Mounted on
rootfs                                                  144G  1.1G  135G   1% /
udev                                                     10M     0   10M   0% /dev
tmpfs                                                   189M  808K  188M   1% /run
/dev/disk/by-uuid/b7c8b35a-d94c-4791-9a89-385a7ca2c56d  144G  1.1G  135G   1% /
tmpfs                                                   5.0M     0  5.0M   0% /run/lock
tmpfs                                                   1.2G     0  1.2G   0% /run/shm
tmpfs                                                   943M   24K  943M   1% /tmp
/dev/sda1                                               688G  366G  323G  54% /media/39a94a18-44d1-41af-8e8e-8abb8adb7691
/dev/sdb1                                               2.7T  1.4T  1.2T  55% /media/d737aac9-fd54-4238-9a2a-540a03712ac6

Alles anzeigen

patrick168 · 14. März 2015

Okay, I will wait for you David.

davidh2k · 14. März 2015

Zitat von patrick168

/dev/sdc2

You would use the UUID, not /dev/sdc2. Also, I have it running without need to repartition (I just created a 500MB file, partitioned it and loop mounted it to /media)

Zitat von patrick168

Also where should this command be saved if it has to be auto-mounted at startup. Thanks.

/etc/fstab

Zitat von patrick168

Okay, I will wait for you David.

I need to figure out how to recreate the folder structure under /media to the new /media partition. Once I found a proper solution for that, you'll have it.

Greetings
David

davidh2k · 14. März 2015

First part (Aaron looks into a proper way to rebuild folder structure, wait for him until you do try it).

Code

fallocate -l 500M rootfsprotect.img
dd if=/dev/zero of=rootfsprotect.img bs=1MB count=500
mkfs -t ext4 rootfsprotect.img
mount -t auto -o loop rootfsprotect.img /mnt
cd /mnt

Third part

nano /etc/fstab

Make it look like this:

Code

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=acb181a6-f386-4cf4-af60-fa153067f727 /               ext4    errors=remount-ro 0       1
# /opt was on /dev/sda3 during installation
UUID=b09c9c6d-edd8-4c2f-86e0-a9edd81f9b23 /opt            xfs     defaults        0       2
# swap was on /dev/sda2 during installation
UUID=af9b1ebe-3c2e-4d61-b067-3664151bebf1 none            swap    sw              0       0
/root/rootfsprotect.img /media auto loop 0 0
/dev/sdc1       /media/usb0     auto    rw,user,noauto  0       0
/dev/sdd1       /media/usb1     auto    rw,user,noauto  0       0
tmpfs           /tmp            tmpfs   defaults        0       0
# >>> [openmediavault]
UUID=d3c21c66-af4b-41d4-b098-462e83fa641d /media/d3c21c66-af4b-41d4-b098-462e83fa641d xfs defaults,nofail,noexec,usrquota,grpquota 0 2
UUID=ca425484-1be3-47f1-b7bb-8f0785c9ea5b /media/ca425484-1be3-47f1-b7bb-8f0785c9ea5b xfs defaults,nofail,noexec,usrquota,grpquota 0 2
/media/d3c21c66-af4b-41d4-b098-462e83fa641d//Comedy /export/Comedy none bind 0 0
/media/d3c21c66-af4b-41d4-b098-462e83fa641d//Filme /export/Filme none bind 0 0
/media/d3c21c66-af4b-41d4-b098-462e83fa641d//Serien /export/Serien none bind 0 0
/media/ca425484-1be3-47f1-b7bb-8f0785c9ea5b// /export/Sammy1 none bind 0 0
# <<< [openmediavault]

Alles anzeigen

Make sure that the protection is mounted before everything else that wants to be in /media/.

Greetings
David

tekkb · 15. März 2015

Zitat von subzero79

Whats the reason of the disk not mounting at startup?

Did not read all this but surely get this straightened out first. Even if a drive had to be replaced.
He may just need a root fs delay for the usb drive.

http://phpbb.openmediavault.org/viewtopic.php?f=3&t=1465

In one case a person needed a delay as high as 15 for a usb drive.

patrick168 · 15. März 2015

Zitat von tekkb

Did not read all this but surely get this straightened out first. Even if a drive had to be replaced.
He may just need a root fs delay for the usb drive.

http://phpbb.openmediavault.org/viewtopic.php?f=3&t=1465

In one case a person needed a delay as high as 15 for a usb drive.

I think it should be a contact problem, so I cleaned the SATA sockets with alcohol this time. But who knows the real cause, it is in essence a trial and error process.

This happens in my backup machine that wakes up every night for backup and all disks are internal instead of USB drive.

tekkb · 15. März 2015

It takes a bit of time for the usb drives to become available. I think you should try to increase the delay of the root fs a bit. We've seen this a lot.

patrick168 · 20. März 2015

I mounted the rootfsprotect.img and changed the /etc/fstab according to David's suggestion for some days, it is working fine. Thank you all, especially to David.

Jetzt mitmachen!