bug#25718: parted on Ubuntu16.04

Peter Bot <[email protected]>
Newsgroups gmane.comp.gnu.parted.bugs
Message-ID <[email protected]>
hello,
- using parted to initialize/partition a SDHC 64GB; interactive mode 
used; results as follows:


INPUT -IN ; OUTPUT -OUT

IN     (parted) print devices
OUT  /dev/sda (500GB)
/dev/sdb (500GB)
/dev/sdc (1000GB)
/dev/sdd (32.3GB)
/dev/sde (750GB)
/dev/sdf (640GB)
/dev/sdg (1000GB)
/dev/sdh (63.3GB)

IN    (parted) select /dev/sdh
OUT  Using /dev/sdh

IN    (parted) rescue START END
OUT  Error: /dev/sdh: unrecognised disk label

IN  (parted) mklabel
OUT   New disk label type? msdos
OUT    Error: Input/output error during read on /dev/sdh
Retry/Ignore/Cancel? Retry

IN    (parted) print free space
OUT    Error: /dev/sdh: unrecognised disk label
Model: Multiple Card Reader (scsi)
Disk /dev/sdh: 63.3GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown

IN    (parted) disk_toggle
OUT  Error: /dev/sdh: unrecognised disk label
Backtrace has 9 calls on stack:
   9: /lib/x86_64-linux-gnu/libparted.so.2(ped_assert+0x44) [0x7fe6817dcea4]
   8: /lib/x86_64-linux-gnu/libparted.so.2(+0xe023) [0x7fe6817e0023]
   7: parted(command_line_get_disk_flag+0x37) [0x55e06dca4df7]
   6: parted(+0x68d0) [0x55e06dc9f8d0]
   5: parted(+0x69d3) [0x55e06dc9f9d3]
   4: parted(interactive_mode+0x120) [0x55e06dca5ff0]
   3: parted(main+0x1386) [0x55e06dc9f176]
   2: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) 
[0x7fe680faa830]
   1: parted(_start+0x29) [0x55e06dc9f1d9]


You found a bug in GNU Parted! Here's what you have to do:

Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:
.....
for further information.

Your report should contain the version of this release (3.2)
....

Question please - is there any chance that /dev/sdh SDHC could be 
rescued somehow? or just ... chuck it?.

thank you. peter. [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.