summaryrefslogtreecommitdiffstats
path: root/mdk-stage1
diff options
context:
space:
mode:
authorThierry Vignaud <thierry.vignaud@gmail.com>2017-02-25 08:07:36 +0100
committerThierry Vignaud <thierry.vignaud@gmail.com>2017-02-25 08:40:42 +0100
commit72f762b72f81f033a2cf999cb2353d611e4ba44d (patch)
treed40d4fcecd5c405542daa912d79489cfc0b6036b /mdk-stage1
parent67d8f423c623740a1118b80d2c5e4489d432cc26 (diff)
downloaddrakx-72f762b72f81f033a2cf999cb2353d611e4ba44d.tar
drakx-72f762b72f81f033a2cf999cb2353d611e4ba44d.tar.gz
drakx-72f762b72f81f033a2cf999cb2353d611e4ba44d.tar.bz2
drakx-72f762b72f81f033a2cf999cb2353d611e4ba44d.tar.xz
drakx-72f762b72f81f033a2cf999cb2353d611e4ba44d.zip
Revert "- Add 60-block.rules in the installer (mga#20074)"
This reverts commit bdac0595323a6417fb7365038c9777cde0060f58. Many testers are seeing the "I cannot read the partition table of device sda, it's too corrupted for me:(" message when the installer first examines the disks. It's likely that when the installer examines the partition table on the disk, that triggers the udev rule and causes the kernel to rescan the partition table. Unfortunately this coincides with the installer reading /proc/partitions to verify the kernel has the same view of the partitions, which can catch /proc/partitions in a partially updated state. After patching the ISO to remove the 60-block.rules file from stage 2, no failures happen in the installer.
Diffstat (limited to 'mdk-stage1')
0 files changed, 0 insertions, 0 deletions