Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi, I stopped playing with Linux a while ago after I almost lost everything due to a partitioning error, but I want to try again. Apparently, the problem was that with the newest Linux Kernel, if you try to install it alongside Windows on the same HD, it corrupts your partition table so bad you have to use fdisk alone to fix it. I would like to install a newer distro but I cannot risk that happening again. Has a solution been arrived at? Is there a new kernel (I think the bad one was 2.6) that addresses this issue?
AFAIK, you install Windows first then Linux after creating at least two partitions. Install Windows on the first one, then use the remaining one to create the Linux partitions from. The kernel itself corrupt Windows partitions, installing it wrongly by the end user will though.
No, there was something--for me it was actually Suse 9.1. I had tried countless distros, they all worked fine, but this one did a number on my partition table. There was actually a discussion about it in the Suse section, and many attributed it to a specific kernel. It happened to a few people, it was a big deal if I remember.
The partitioning tool parted, which YaST uses during the installation, may write an incorrect partition table. The problem occurs if
* the BIOS and Linux "see" different disk geometries AND
* the Windows partition is larger than about 8 GB (more precisely: if the first hard disk partition ends on cylinder 1024 or beyond this point).
When the system is booted, Windows may use the values in the partition table, which causes a failure.
Currently, this problem also occurs on other Linux distributions using kernel 2.6.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.