Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: ber on August 26, 2011, 01:56:19 AM
-
Hi All, been scratching my head and going round and round in circles- need another look at this can someone revisit my work and see where I've gone wrong. :-?
My SME 7.5.1 is backed up on a 80GB USB external device- backup files are appx 16GB.
The system was running fine, then I had a problem with the previous backup disk so I replaced it and now cant get the backups running due to the mounting problem.
Server runs two 80GB disks in RAID 1- all current updates are installed.
I run the backups through the browser and configure the available disks for backup from there.
The new disks that have been added do show up as i beleive they are correct configured.
I also have a USB disk contrib on the server that monitors the USB disks and enables manual mounting etc..all these run as expected.
Ive gone through the how to many times with different disks and still keep getting the same problem-
Backup started at Fri Aug 26 11:32:04 2011 Backup of mysql databases has been done Mounting backup shared directory localhost/media/80GB
*** No backup allowed or error during backup *** Error while mounting /media/80GB
:
mount: can't find /media/80GB
in /etc/fstab or /etc/mtab
As mentioned Ive tried different disks and keep getting the same problem- ive done some indepth look at editing fstab and still cant resolve it.
I feel the problem is related somehow to the configuration of my fstab- just cant pinpoint the problem.
The USB backup disk I have is a 80GB ATA disk.(sdd with sdd1 partition) here is my fstab file.
#------------------------------------------------------------
# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/main/root / ext3 usrquota,grpquota $
/dev/md1 /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
/dev/main/swap swap swap defaults 0 0
/dev/sdd1 /media/80GB ext3 defaults 0 0
[ Read 22 lines ]
The disk mounts ok when I run the mount command.
here the list of disks fdisk command.
[root@server ~]# fdisk -l | more
Disk /dev/md1 doesn't contain a valid partition table
Disk /dev/md2 doesn't contain a valid partition table
Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1 doesn't contain a valid partition table
Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 fd Linux raid autodetect
/dev/sda2 14 9729 78043770 fd Linux raid autodetect
Disk /dev/sdb: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 13 104384+ fd Linux raid autodetect
Partition 1 does not end on cylinder boundary.
/dev/sdb2 13 9729 78043807 fd Linux raid autodetect
Disk /dev/md1: 106 MB, 106823680 bytes
2 heads, 4 sectors/track, 26080 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk /dev/md2: 79.9 GB, 79916695552 bytes
2 heads, 4 sectors/track, 19510912 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk /dev/dm-0: 78.0 GB, 78014054400 bytes
2 heads, 4 sectors/track, 19046400 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk /dev/dm-1: 1879 MB, 1879048192 bytes
2 heads, 4 sectors/track, 458752 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk /dev/sdd: 80.0 GB, 80025280000 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdd1 1 9729 78148161 83 Linux
[root@server ~]#
Thanks you. 8-)
-
What is the output of
mount
What is the file system on the new backup drive (fat32, ntfs, ext3)?
-
It's a bug, http://bugs.contribs.org/show_bug.cgi?id=6512 (http://bugs.contribs.org/show_bug.cgi?id=6512). I ran into this also.
-
Hi Curly I'm still new to the bug system and am unclear how to establish whether the bug is fixed or in progress and what the update is regarding the "fix" for that particular "bug". Can you enlighten anymore regarding that particular bug where the solution is for the problem. Thanks
-
I'm not so sure either, but the status of the bug is "verified fixed". I only know it doesn't work for me.
To still make a backup I just added an entry to /etc/fstab, and removed it afterwards. But, be sure to make a backup of that file because that's an essential file.
-
From doing a quick read of that bug, it appears to me that it applies to doing a backup using certain browsers causes the value to be appended with a CL/LF(^M). It also appears that this has been fixed and verified.
The update could be installed using
yum update --enablerepo=smeupdates-testing e-smith-backup
I could be mistaken, but updating this shouldn't create any problem even if this isn't your issue.