Thank you for looking into this. Unfortunately, I cannot remember 100% how I prepared this disk a few years ago. But most probably, it would have been with cfdisk in Debian 4.
Maybe this WD external disk was originally delivered with a Mac partition? The disk was at a client's site, where they have many Macs. So it is also possible someone once connected it to a Mac. But they certainly didn't "initialize" or "erase" it (to use Macs terminology), because the disk still has all it's data and works as expected as an ext3 partition. So apparently, parted gets mislead in it's partition identification code, in some special case. Hopefully my sample will help correct this glitch. I rely a lot on parted since it seems to be the only tool that allows me to entirely script a partitioning of new disks, and I started to need to do that a lot. In the meantime, maybe it is safer to first zero out the first block(s)? I sometimes do it for the first 512 bytes. Should I do it for all the first 16K? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909424 Title: Parted reports ext3 partition as hfs+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/parted/+bug/909424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
