Hi! > On Mon, Nov 03, 2008 at 04:44:16PM +0100, Michael Tautschnig wrote: > > > It still is broken for some disks: > > > > > > (CMD) parted -s /dev/sdb unit TiB print 1> /tmp/h7McmrDIeR 2> > > > /tmp/bnYHpUowLU > > > Executing: parted -s /dev/sdb unit TiB print > > > Command parted -s /dev/sdb unit TiB print had exit code 1 > > > Parted was unable to read the partition table > > > (STDOUT) No Implementation: Partition 1 isn't aligned to cylinder > > > boundaries. This is still unsupported. > > > > [...] > > > > Is this supposed to be a brand new/blank disk, or what has happended to > > that one > > before? I didn't expect this error to occur at that stage, so it's > > currently not > > handled by setup-storage. Did you see it on a single disk only, or multiple > > times? > > It was a used disk and I don't know how it got formatted this way, > but IMHO when the config tells setup-storage to write a new disklabel, > which will erase all existing partition information anyhow, you > shouldn't try to read anything at all from that disk beforehand.
This should finally be fixed in 3.2.17+experimental1. It would be great if you could try that one, but probably you don't have a disk with a bad configuration anymore :-) Best, Michael
pgp0gL1lL4h9H.pgp
Description: PGP signature
