I'm having some troubles with a SuSE install. I used Acronis Disk Director's partitioning thing(I use AcronisOS Selector to boot either to ntldr or GRUB, and you can get to Disk Director right from the boot menu) to expand an ext3 partition(with / on it, including the /boot directory). If it matters, I expanded it forward(I deleted a partition that was in front of it and used that space). SuSE is the last partition on my HDD. I knew that I would have to change grub's configuration, but I really needed the extra space, so I did it anyway. The partition in front of SuSE is used for swap.

So once it was finished, I edited menu.lst via the SuSE rescue disk. I also reinstalled grub. So, I restarted and booted into SuSE from Acronis. GRUB appeared fine, and I just let it time out and boot to the default entry.

When my system boots, I get an error message saying
When I run fsck /dev/hda6(the new partition/device #), it says
If I run the code that it says to remount the partition as rw, I can start kdm and get into Gnome. Everything seems fine, except the ACPI stuff(applets showing battery charge; this is on a laptop), though I admit that I did not spend more than a minute or so looking around.

If it matters, I have a P4 w/ HT, though HT is disabled in BIOS so ACPI will word with SuSE. I originally installed it before I did that, so SuSE is using the smp kernel, though it worked fine after I changed the HT settings(until now).

My laptop is a Toshiba A75-S206.


Any ideas of what to do here?
And secondly, if I were to use LVM(SuSE supports this, right?), would it be less of a hassle to resize/move partitions?

Thanks.

OK, I think I figured it out. Because I moved the partitions around, the device name for the root partition changed. I changed it in the GRUB stuff, but didn't think about changing it in fstab and mtab. Seems to work now.

I too had a similar problem with SuSE 9.1.

fsck failed. Please repair manually and reboot. The root file system is currently mounted read-only. To remount it read-write.....

At first I tried:

mount -n -o remount,rw / - this didn't work

then I tried:

e2fsck /dev/hde3 - this didn't work either, no permission

so I tried:

chmod 777 /dev/hde3 then: e2fsck /dev/hde3 - no good, same problem

Then I saw your article:

OK, I think I figured it out. Because I moved the partitions around, the device name for the root partition changed. I changed it in the GRUB stuff, but didn't think about changing it in fstab and mtab. Seems to work now.

I'm trying to perfect a backup system with ARCserve for Linux and I'm trying to backup onto a USB drive. I partitioned the USB drive and formatted it as Reiserfs and set it as the primary partition(bad mistake). So it got me to wondering if maybe I'd stuffed up the boot sequence??? I went to /etc and checked out the fstab. The USB device was sda1 and at the end of the line there was two numbers: 1 2.
The hde3 had a setting of 1 1 and all other devices had a setting of: 0 0, so I changed the settings for sda1 to: 0 0

This has fixed the problem as far as I can tell. The OS boots to GUI mode as normal and all my previous settings are still the same.

I was also checking out "rsync" at the time so I'm not sure if that had anything to do with my problem. I think it was just the partitioning and primary drive setting.

Still working out how to change the media for ARCserve from tape to file or USB drive...