Error Writing Partition Changes to DASD

[Rod Clayton]

I am trying to do a network install of Etch in a 31 bit VM guest. It
goes well till I get to writing the automatically generated partition
layouts to disk and I get the error:

Error informing the kernel about modifications to partition
/dev/dasda5 -- Invalid argument. This means Linux won't know about
any changes you made to /dev/dasda5 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.

When I re-boot, It says it can't determine how the disk is formatted
and asks me to do it again.

Any ideas?

Thanks,
Rod

[Adam Thornton]

Post by Rod Clayton
I am trying to do a network install of Etch in a 31 bit VM guest. It
goes well till I get to writing the automatically generated partition
Error informing the kernel about modifications to partition
/dev/dasda5 -- Invalid argument. This means Linux won't know about
any changes you made to /dev/dasda5 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
When I re-boot, It says it can't determine how the disk is formatted
and asks me to do it again.
Any ideas?

AFAIK, the CKD driver only supports 4 devices per partition. In the
S/390 world, you generally use 1 per partition and define additional
devices, particularly under VM.

I would try defining more smaller minidisks and then putting one
partition on each of them.

Adam

[Frans Pop]

Post by Adam Thornton

Post by Rod Clayton
Error informing the kernel about modifications to partition
/dev/dasda5 -- Invalid argument. This means Linux won't know about
any changes you made to /dev/dasda5 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.

AFAIK, the CKD driver only supports 4 devices per partition. In the
S/390 world, you generally use 1 per partition and define additional
devices, particularly under VM.

Please file a bug report against partman-base for this issue.
It should probably check that the maximum number of partitions supported
by the disk label/partition table is not being exceeded. Not sure yet if
this is an issue in partman or libparted.

[Adam Thornton]

Post by Frans Pop

Post by Adam Thornton

Post by Rod Clayton
Error informing the kernel about modifications to partition
/dev/dasda5 -- Invalid argument. This means Linux won't know about
any changes you made to /dev/dasda5 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.

AFAIK, the CKD driver only supports 4 devices per partition. In the
S/390 world, you generally use 1 per partition and define additional
devices, particularly under VM.

Please file a bug report against partman-base for this issue.
It should probably check that the maximum number of partitions
supported
by the disk label/partition table is not being exceeded. Not sure yet if
this is an issue in partman or libparted.

Also, read "partitions per device" rather than the other way round.
Sorry.

Adam