Hi,
I have been running suse 13.1 on a 32 bit laptop. It finally appeared to die last week. My root partition is corrupted. I have backed up my home partition. So I have downloaded tumbleweed as it has 32 bit. I have checked the download and verified the burned DVD.
I would like to keep my home partition.
I would like my boot partition to be bigger
And to install root in the same place.
Boot to your gparted live
Do the following in your gparted live
Identify your /home partition (it’s generally sda2). The usual easiest way is to know the size of your /home partition and look for the partition which displays the same size.
Remove all your partitions other than /home
Re-size if you like and move your /home partition to the end of the disk.
Do not create swap and root partitions, it’s easier to do those during the new openSUSE install.
Reboot to your TW install.
Do not do an “use all defaults” install, when you arrive at your disk layout, choose “Edit layout”
Modify the /home partition to point to your existing partition (If you don’t do this, a new /home partition will be created in your disk free space).
Review the proposed disk layout and accept if OK.
Continue, and install the same Desktop you were running in your old openSUSE.
When installation is complete,
Check whether anything needs to be fixed.
When things are working as well as you can determine, do a system dup (because you are running TW). I would expect that you should allow vendor changes, so don’t specify “no vendor change.”
Reboot.
Fingers crossed, you should have a brand new install while preserving your personal files with many of your Desktop settings imported.
The bold part is absolutely wrong. You have two disks, so /home could be on /dev/sda as well as on /dev/sdb. Qiestions are: how did the rootfilesystem get corrupted. If it’s caused by bad blocks, replace the disk, reuse is asking for more trouble. If it’s OK, use the expert partioner from the installer and make sure your old /home partition is indeed mounted on /home.
Thank you for your assistance, I am beginning to believe the hard drive has had it. I now have another issue, so will make a different post. I may not be up to the task.