1 (edited by gedakc 2016-05-04 21:44:07)

Topic: [closed] does not recognize the USB stick from this it was started.

If using dd the gparted-live iso will be copied to a USB stick, then after rebooting the system Gparted will be started and will give out  the message “...Invalid partition table...”.
After clicking on “Ignore”, the stick will be displayed as only unallocated space.

If this stick will be insert to a Debian computer, then the Disk Utility is showing the used space beginning not from the left, but from the right side. The name of the saved iso will be displayed too.

It looks funny, if Gparted starts from a USB stick and then says, on this stick there is only unallocated space, and then, the partition table on this stick is invalid too.

Maybe a detection of such USB sticks can be add to the Gparted.

Regards
cvbn

2

Re: [closed] does not recognize the USB stick from this it was started.

It is possible that the USB stick does not contain a partition table.  I'm not sure how ISOHYBRID works so I'm not sure if this is the case.

Currently GParted does not recognize devices that are only formatted with a file system and no partition table.  This has been raised in Bug 683643 - Doesn't properly support partitionless drives.

3

Re: [closed] does not recognize the USB stick from this it was started.

USB stick with copied isohybrid file on it will be recognized by OS (Linux, but not W$) as a CD.
Fs iso9660 will be used, and such stick will be mounted as read only.
The partition starts begining not from 2048, not from 63, not from 1, but from 0, this can confuse a bit.

I made a few fdisk outputs to show details.

- iso file
- sdb is the USB stick with gparted on it
- sr1 is the external USB CD drive with gparted CD in it
all tree have the same disk identifier

- parted output
- sfdisk output

bash-4.2# fdisk -l gparted-live-0.15.0-3-i486.iso

Disk gparted-live-0.15.0-3-i486.iso: 139 MB, 139460608 bytes
64 heads, 32 sectors/track, 133 cylinders, total 272384 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x402288c7

                                           Device   Boot    Start      End             Blocks    Id   System
gparted-live-0.15.0-3-i486.iso1   *           0           272383      136192   17  Hidden HPFS/NTFS


bash-4.2# fdisk -l -u /dev/sdb

Disk /dev/sdb: 4004 MB, 4004511744 bytes
64 heads, 32 sectors/track, 3819 cylinders, total 7821312 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x402288c7

         Device    Boot    Start      End             Blocks     Id   System
/dev/sdb1p1   *           0            272383      136192   17  Hidden HPFS/NTFS


bash-4.2# fdisk -l -u /dev/sr1
Note: sector size is 2048 (not 512)

Disk /dev/sr1: 139 MB, 139767808 bytes
64 heads, 32 sectors/track, 33 cylinders, total 68246 sectors
Units = sectors of 1 * 2048 = 2048 bytes
Sector size (logical/physical): 2048 bytes / 2048 bytes
I/O size (minimum/optimal): 2048 bytes / 2048 bytes
Disk identifier: 0x402288c7

      Device   Boot     Start       End            Blocks      Id  System
/dev/sr1p1   *           0             272383      544768   17  Hidden HPFS/NTFS


bash-4.2# parted /dev/sdb unit s print
Error: Invalid partition table - recursive partition on /dev/sdb.
Ignore/Cancel? i                                                         
Model: SanDisk Cruzer Micro (scsi)
Disk /dev/sdb: 7821312s
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number  Start  End  Size  Type  File system  Flags


bash-4.2# sfdisk -d /dev/sdb > /root/parts
bash-4.2#

# partition table of /dev/sdb
unit: sectors

/dev/sdb1 : start=        0, size=   272384, Id=17, bootable
/dev/sdb2 : start=        0, size=        0, Id= 0
/dev/sdb3 : start=        0, size=        0, Id= 0
/dev/sdb4 : start=        0, size=        0, Id= 0


If you like, use the python script to make your isohybrid stick.

http://meego.gitorious.org/meego-develo … age-writer

Regards
cvbn

4

Re: [closed] does not recognize the USB stick from this it was started.

Thank you cvbn for the extra information.  If you learn more about how to implement this feature request, then please do add to this thread.