Hello Michael,
I've been away, so I'm not back to follow up on this.
Quoting Michael Tautschnig <[email protected]>:
Could you do another run and run parted manually from the shell you
should get
dropped into? Like so:
parted -s /dev/sda unit TiB print (should produce said error)
parted -s /dev/sda mklabel msdos
parted -s /dev/sda unit TiB print (should work)
I'm just a bit worried for two reasons: (i) I haven't seen this error before,
blank disks should cause a somewhat different error, and (ii)
depending on your
Xen configuration you may or may not have /dev/sda really available
and only see
/dev/sda1 instead. (I'm using the latter configuration style myself.)
r...@shibidp1:/# parted -s /dev/sda unit TiB print
Error: Error initialising SCSI device /dev/sda - Invalid argument
r...@shibidp1:/# parted -s /dev/sda mklabel msdos
Error: Error initialising SCSI device /dev/sda - Invalid argument
r...@shibidp1:/# parted -s /dev/sda unit TiB print
Error: Error initialising SCSI device /dev/sda - Invalid argument
r...@shibidp1:/# ls -l /dev/sda
brw-rw---- 1 root disk 8, 0 Dec 14 10:46 /dev/sda
r...@shibidp1:/# ls -l /dev/sda1
brw-rw---- 1 root disk 8, 1 Dec 14 10:46 /dev/sda1
I'm exporting a logical volume to the xen vm. This logical volume is
then the disk.
TIA!
--
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Rudy Gevaert [email protected] tel:+32 9 264 4734
Directie ICT, afd. Infrastructuur Direction ICT, Infrastructure dept.
Groep Systemen Systems group
Universiteit Gent Ghent University
Krijgslaan 281, gebouw S9, 9000 Gent, Belgie www.UGent.be
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
