Hello,
Thank you for providing more information.
The error message is generated by a component (a library named libparted2) used by the partman program to handle disk partitioning on behalf the debian installer; the involved source code is:
Further analysis is required to reproduce the problem.
Thank you for providing more information.
The error message is generated by a component (a library named libparted2) used by the partman program to handle disk partitioning on behalf the debian installer; the involved source code is:
- sources / parted / 3.5-3 / libparted / arch / linux.c al line 3226 in the function named _disk_sync_part_table:
Code:
/* * Sync the partition table in two step process: * 1. Remove all of the partitions from the kernel's tables, but do not attempt * removal of any partition for which the corresponding ioctl call fails. * 2. Add all the partitions that we hold in disk, throwing a warning * if we cannot because step 1 failed to remove it and it is not being * added back with the same start and length. * * To achieve this two step process we must calculate the minimum number of * maximum possible partitions between what linux supports and what the label * type supports. EX: * * number=MIN(max_parts_supported_in_linux,max_parts_supported_in_msdos_tables) */static int_disk_sync_part_table (PedDisk* disk){[..] if (bad_part_list == NULL) ret = 1; else { bad_part_list[strlen (bad_part_list) - 2] = 0; if (ped_exception_throw ( PED_EXCEPTION_ERROR, PED_EXCEPTION_IGNORE_CANCEL, _("Partition(s) %s on %s have been written, but we have " "been unable to inform the kernel of the change, " "probably because it/they are in use. As a result, " "the old partition(s) will remain in use. You " "should reboot now before making further changes."), bad_part_list, disk->dev->path) == PED_EXCEPTION_IGNORE) ret = 1; free (bad_part_list); }
Further analysis is required to reproduce the problem.
Statistics: Posted by Aki — 2024-10-15 21:12 — Replies 8 — Views 370