Bugzilla – Bug 231887
Error during install: can't set swap partition type to 82
Last modified: 2007-03-19 15:49:43 UTC
I installed openSUSE 10.2 64-bit on my laptop. Then I found that certain things only work well under 32-bit, so I did a new install in 32-bit mode. During both installations, I used the manual partitioning tool in the installer (to shrink the Windows partition, set up an encrypted home partition, etc.). I also choose an install type of "New Installation" both times. The original 64-bit installation succeeded. The subsequent 32-bit installation failed while applying the disk partitioning settings. The error was something like "could not set type to 82 for /dev/sda6" which was my swap partition. I rebooted and tried again, and got the same error in the same place. That time, I switched to the console (Alt-F2 or whatever) and ran fisk manually. I found that not all the partitions I had selected in the partition tool had been created, but the swap partition it was complaining about *had* been created and its type *was* set to 82. I manually created the rest of the partitions. Then I went back to the installer (Alt-F7), and back in the text mode "install failed what do you want to do now" screen I selected to restart the installation. This time I still used the manual partitioning tool but only had to edit existing partitions (not create new ones). This time the installation succeeded. I'm not sure why I got the type 82 error, especially since after the second time I got the error fdisk reported that the type was already set to 82. I don't know what might account for the fact that I didn't get the error during the first installation, other than that the first time I was only consuming space previously used by Windows, and the second time I was deleting an existing extended partition (with existing Linux partitions) and creating a new extended partition with new Linux partitions in its place.
Can you please attach y2logs from this failed installation. If you are in doubt, here is small how to obtain this logs: http://en.opensuse.org/Bugs/YaST. Thanks!
Created attachment 111901 [details] /var/log/YaST2/* I only have the YaST2 logs from the final installation on this machine. Since I didn't reboot between the failed install and the time I told it to restart the install process and it worked, perhaps this will have the data from both passes through the installer? Anyway, it's what I have. :)
Parted complains about partition /dev/sda5 being in use by the kernel, this causes parted return code being non-zero which causes YaST2 to assume parted having failed. /usr/sbin/parted -s /dev/sda set 6 type 130 Error informing the kernel about modifications to partition /dev/sda5 -- Device or resource busy. This means Linux won't know about any changes you made to /dev/sda5 until you reboot -- so you shouldn't mount it or use it in any way before rebooting. Warning: The kernel was unable to re-read the partition table on /dev/sda (Device or resource busy). This means Linux won't know anything about the modifications you made until you reboot. You should reboot your computer before doing anything with /dev/sda. 2007-01-02 16:19:56 <3> linux(3350) [libstorage] Disk.cc(checkSystemError):523 retcode:1 Did yoo do anything outside of YaST2 with sda5 while installing? Maybe mount it and look something up? This would be the only possible explanation I can thing of for the strange parted error message.
I'm pretty sure I did not do anything outside of YaST2 *during* the installations that failed (at least, I can't think of what I would have done -- I didn't use a USB key which is the only thing I've done in the past). After the first failed install I rebooted. After the second failed install, I switched to a text console, ran fdisk, and created all the partitions as I wanted them to appear (and that's when I saw that the type of the swap partition *was* 82, and that it had created some but not all of my specified partitions). Then I used the curses interface that comes up after the install failure to restart the installation, and that time it worked (though that time all the partitions were already in place so I just had to supply the mount points and formatting info).
Thanks, maybe it was an interference with hal daemon, it also fiddles around with disk devices. I will change YaST2 to ignore this special error message when setting the partition id.
YaST2 for SL 10.3 is now changed to ignore this error message by parted when parted changes only partition type.
*** Bug 253393 has been marked as a duplicate of this bug. ***
For FAT partitions this is similar, but the workaround does not work: I try to format it: It complains about not being able to change the partition type. Then I restart Yast: The partition type is changed to FAT. I try to format the partition again: Here, it tries to change the partition type again, and it fails.