Needs to check if target device is big enough for image

Bug #364195 reported by Martin Pitt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
USB ImageWriter
Won't Fix
Medium
Unassigned
usb-imagewriter (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Binary package hint: usb-imagewriter

I used usb-imagewriter to write the current UNR image to my 1 GB usb stick. The details section said "there was an error with dd", and a dialog "There was an error ... (nothing definitive), a log file will be created in your home directory".

However, I do not have any log file in my home directory:

$ ls -l *usb .*usb*
ls: Zugriff auf *usb nicht möglich: No such file or directory
-rw-r--r-- 1 root root 8835 2009-04-16 11:48 .usb-creator.log

.usb-creator.log is unrelated (from usb-creator package).

Revision history for this message
Martin Pitt (pitti) wrote :

Nothing in /root/ either.

Revision history for this message
Oliver Grawert (ogra) wrote :

the log writing function is not implemented yet ...

Changed in usb-imagewriter (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Oliver Grawert (ogra) wrote :

tracking upstream

Changed in usb-imagewriter:
assignee: nobody → ogra
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Martin Pitt (pitti) wrote :

The image does not boot. However, that might be a different bug, since previously I just used dd to copy the image to the usb stick, and it didn't boot either.

(I can boot the .img in kvm, and I can use usb-creator to boot the standard Ubuntu image on the same USB stick on the same computers just fine)

Revision history for this message
Martin Pitt (pitti) wrote :

I can mount the image (well, it automounts)

  /dev/sdb on /media/disk type vfat (rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush)

and cat .disk/info says

  Ubuntu-Netbook-Remix 9.04 "Jaunty Jackalope" - Release i386 (20090420)

$ sudo vol_id /dev/sdb
[sudo] password for martin:
ID_FS_USAGE=filesystem
ID_FS_TYPE=vfat
ID_FS_VERSION=FAT32
ID_FS_UUID=49EB-DB02
ID_FS_UUID_ENC=49EB-DB02
ID_FS_LABEL=
ID_FS_LABEL_ENC=

Revision history for this message
Martin Pitt (pitti) wrote :

Ah, now I know:

  1005M 2009-04-20 17:47 jaunty-netbook-remix-i386.img

The previous image was some 890 MB, and fitted on my 1 GB stick just fine. Now it grew dramatically, and thus simply doesn't fit on my 1 GB stick any more.

Thus usb-imagewriter should check the available space and don't allow me to write the image on it. usb-creator does this well.

Revision history for this message
Oliver Grawert (ogra) wrote :

yes, the size check is a planned feature for karmic

Revision history for this message
Daniel Hollocher (chogydan) wrote :

The original error I believe is cause by a lack of permissions to access the usb drive.

Also, it would be nice if you renamed the executable from imagewriter to usb-imagewriter. IMHO, it makes more sense for the command to match the package name.

Revision history for this message
Martin Pitt (pitti) wrote :

As I already said, the original error is about the target device being too small for the image.

I keep this open because usb-imagewriter should check this in advance, like usb-creator.

summary: - Error dialog at the end: "The dd porcess ended with an error"
+ Needs to check if target device is big enough for image
Revision history for this message
Oliver Grawert (ogra) wrote :

imagewriter is dead, closing ...

Changed in usb-imagewriter (Ubuntu):
status: Confirmed → Won't Fix
Changed in usb-imagewriter:
status: Confirmed → Won't Fix
assignee: Oliver Grawert (ogra) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.