Let me be specific: On my box, I have a 4 gig drive which is /dev/hda and a 2 gig drive which is /dev/hdb. Before installing linux, /dev/hda consisted of a 2 gig primary partition which windows recognized as C: and a 2 gig extended partition containing a 2 gig logical partition which windows saw as E:. /dev/hdb was seen by windows as D:. I had been using E: as my linux drive when I decided to give linux an extra gig from A:. I repartitioned /dev/hda thusly: /dev/hda1 primary 1 gig windows /dev/hda2 extended 3 gigs -- /dev/hda5 logical 64 megs swap /dev/hda6 logical 100 megs / /dev/hda7 logical 300 megs /opt /dev/hda8 logical 2.3 gigs /usr /dev/hda9 logical 200 megs /home Having installed linux, the two operating systems began a peaceful coexistence. However, windows still reported C: as being the previous 2 gigs (E:, of course was no longer visible to windows, being a 3 gig ext2 set of partitions). If I went into dos fdisk it reported the correct partition information, 1 gig fat16 and 3 gigs of type unknown. I decided that perhaps to have windows properly report the correct partition size it would be necessary to repartition using dos fdisk then reinstall windows. There was no need to go to those lengths just to have windows tell me that C: was the correct size so I dismissed the notion and reconciled myself to living with the mild annoyance. Several weeks later I defragged C: in windows. Later that day when I booted linux I went into kernel panic, got the same error messages that were displayed on this list earlier. I manually ran fsck, and an hour later after repairing error after error and no end in sight I decided reinstalling would be faster than fixing and reformatted the disk and reinstalled. If you don't think that windows defrag is to blame what would you suggest? Wolfgang Weisselberg wrote:
Hi!
Trying to kill the keyboard, satan@nfinity.com produced:
I got the same error once when I was new to linux. If /dev/hda on your box is home to both linux and windows and you defragment in windows it screws up the partition table for linux, or something. Say you have a 2 gig drive, and you repartition, giving windows 1 gig and linux 1 gig. Windows still sees A: as being two gigs. No big deal, you know it's only a gig. But if you defrag in windows it creates problems. I don't think you can recover from that. I reinstalled when it happened to me. Sorry to be vague, I don't fully understand what gets screwed up, but it did happen to me, and I ended up having to reinstall. Perhaps Bodo or someone more qualified can provide a better explanation of what happened.
Well, I know that M$ Soft is evil at times, knows not that it should not touch the MBR and more of these stuff, but I certainly doubt your explanation. You see, even Windows knows there might be other partitions on the same HD (like d: e: and f:), especially on such a large one. And so defrag is not ging to touch other partitions. And if Windows saw c: (you mean c:, not a:) as 2 Gigs in size, would it know that there was no more space left?
(Operating Computers by popular myth is ... well, like living by superstition. You'll never get any good in it, you just learn not to get too close to imagined or read danger. And different to life, computers do always do things logically, even if they are very complex ...)
But whatever happened to his partition must have been very bad, cause fsck is usually able to repair a lot of damage. Better hope that you have a working backup somewhere.
-Wolfgang
-- PGP 2 welcome: Mail me, subject "send PGP-key". If you've nothing at all to hide, you must be boring. Unsolicited Bulk E-Mails: *You* pay for ads you never wanted. Is our economy _so_ weak we have to tolerate SPAMMERS? I guess not. -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e