Joined: Dec. 2005
||Posted: Dec. 14 2006,17:36
So qemu now recognizes my entire flashdrive as hdb, which I think is really cool because that makes the 60mb 'harddrive' file a thing of the past.
Now, my flashdrive is the G: drive on my computer, so qemu sees G: as hdb1, which dsl then mounts under /cdrom. If I chose to backup to hdb1, it writes backup.tar.gz to /cdrom. I see it under dsl, but when I look at the G: drive in Windows, it's not there. When I shut down and unmount and halt dsl, it writes to backup.tar.gz and thinks it's writing to disk, but again, there is no actual backup file in real life. Is this a unionfs thing?
The only clue I can offer is this snippet I get each time I shutdown.
|Code Sample |
|cloop: losetup_file: 264 blocks, 65536 bytes/block, largest block is 65490 bytes.|
cloop: final offset wrong (9624394 not 2239378)
isofs_read_super: bread failed, dev=f0:03, iso_blknum=16, block=32
ioctl: LOOP_CLR_FD: Invalid argument
mount: wrong fs type, bad option, bad superblock on /dev/cloop3,
or too many mounted file systems
Please mount media containing optional dir and try again.
I have emailed backup.tar.gz to myself from dsl, downloaded it in Windows to the G: drive so I have all my config files and what not, but I lack the ability to save anything new without going through that bally hoo.
Heavens to Murgatroid!