Open GoogleCodeExporter opened 9 years ago
I'm having a similar issue. I have an external hard disk which I've partitioned
into
Windows (sdb1) and Linux (sdb2) partitions.
Only the sdb1 (Windows) partition is selectable as a backup device in flyback,
but I
would like to backup to the sdb2 Linux partition.
gdi2k@x200:~$ sudo fdisk -l /dev/sdb
Disk /dev/sdb: 499.4 GB, 499405291520 bytes
255 heads, 63 sectors/track, 60715 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00021968
Device Boot Start End Blocks Id System
/dev/sdb1 1 20643 165814866 b W95 FAT32
/dev/sdb2 20644 60715 321878340 83 Linux
Running Ubuntu Karmic 64-bit.
Original comment by gd...@gmx.net
on 16 Mar 2010 at 4:09
Apologies, it seems my issue has to do with the fact that I do not have write
permissions on the newly created ext4 Linux partition. Fixing that allows me to
select the partition from flyback.
Sorry for the noise.
Original comment by gd...@gmx.net
on 16 Mar 2010 at 4:23
I have the exact same problem -- my USB disk actually shows up as a selectable
"to be
backed up" file system, but is not selectable as a back-up destination.
Original comment by LazyGu...@gmail.com
on 17 Mar 2010 at 12:07
Same probleme here. But figured out that the hdd has to be FAT not EXT
Original comment by germar.r...@gmail.com
on 5 Apr 2010 at 10:06
It isn't the file system that matters (FAT, EXT, etc.). For local disks the only
qualifier is that Flyback has write permissions at the root of the mount. So if
you
have a USB disk mounted at /media/usbdrive, but you only have write permission
at
/media/usbdrive/myaccount/, Flyback will ignore it.
For network mapped drives, you have to make a connection with GVFS, and you
MUST be
part of the FUSE group in order for an entry to be created in ~/.gvfs. Same
rules
apply as above, you'll need write access to the root of the networked mount.
Once all
that is satisfied, Flyback will allow backups.
This information should be written up a little better and put in to a FAQ, it
would
eliminate a lot of headaches.
Original comment by specopsa...@gmail.com
on 6 May 2010 at 3:26
I just stepped through the code on my ubuntu 10.10 installation what I found
was that the issue appears to be in device matching between the output of
"mount" and "udevadm". The string comparison in get_mount_points_for_uuid was
checking the output from mount which on my machine was "/dev/sda1" and
"/dev/sdb1" against the output from udevadm which on my machine was "sda1" and
"sdb1". To fix this I hacked backup.get_dev_paths_for_uuid in an ugly way:
if line.startswith('E: DEVNAME='):
tmp_path = line[line.index('=')+1:].strip()
if "dev" not in tmp_path:
tmp_path = "/dev/" + tmp_path
dev_paths.add( tmp_path )
Once I did this my external drive showed up just fine.
Aloha,
paddy hannon
Original comment by pap...@gmail.com
on 14 Oct 2010 at 6:29
[deleted comment]
Hi Paddy Hannon,
Thanks a lot! In order to simply the patching process. I have made a patch
based on your code:
--- a/src/backup.py Wed May 05 11:17:53 2010 -0500
+++ b/src/backup.py Sun Oct 30 19:40:58 2011 +0800
@@ -106,7 +106,10 @@
dev_paths = set()
for line in s.split('\n'):
if line.startswith('E: DEVNAME='):
- dev_paths.add( line[line.index('=')+1:].strip() )
+ tmp_path = line[line.index('=')+1:].strip()
+ if "dev" not in tmp_path:
+ tmp_path = "/dev/" + tmp_path
+ dev_paths.add( tmp_path )
if line.startswith('E: DEVLINKS='):
for path in line[line.index('=')+1:].strip().split():
dev_paths.add(path)
Original comment by xben...@gmail.com
on 30 Oct 2011 at 11:43
Attachments:
Just an observation -- this is a critical bug, and that's the way it should be
treated. If a user has an external drive with a USB connection, and it's
visible in Ubuntu's "Places" folders, and (in my case) has 2TB of free space --
and Flyback can't find it -- there's something structurally wrong with the
application. Users should not have to enter complex code and spend hours
trying to get it to work. It's this kind of stuff that continues to give Linux
a black eye.
Original comment by ken...@gmail.com
on 30 Nov 2011 at 2:56
Original issue reported on code.google.com by
cuor...@gmail.com
on 14 Mar 2010 at 5:49