Re: [S.u.S.E. Linux] error file system
Hi! Trying to kill the keyboard, satan@nfinity.com produced:
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:.
Ok, up to here I understand it :)
I repartitioned /dev/hda thusly: ^^^^^^^^^^^^^ Using which tool? Or, in other words: fdisk and reinstall of Windows or something else and no reinstall?
/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
Too bad we don't have the physical layout of the HD, but I think you packed them with no space in between: 5,6,7,8,9.
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
Does that means that Windows did not report an E: anymore?
fdisk it reported the correct partition information, 1 gig fat16 and 3 gigs of type unknown.
Which proves (to me, at least) that the information had been properly stored. However, there is the (remote, stupid, unneccessary i.e. M$ might have done it) possibility that Windows stores the partition information about it's install partition at install time ... and if you did not reinstall it ... but I don't think that was it.
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.
Hmmm ... Well, reinstall, dos fdisk may not be necessary ... but I don't know.
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.
Hmm ...
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 ^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^ Well, the error messages there was certainly no kernel panik.
(You may know the story of the mother who playd a famous violin(?) teacher a tape recording. The teacher listens, *listens* and starts go get tears in his eyes ... and finally says "Madame, is that really your son playing?" to which she answers "Why no, that's a recording of Yehudi Menhuin. But with my boy it sounds just the same." ... In other words, I appreciate your trying to be helpful with the error messages, but ... I'd need them as exact as possible. )
earlier.
Well, it would have been interesting to know if your / (/dev/hda6, inside that 2 GB part) still worked (i.e. fsck error messages) or not ...
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?
Hmmm. Difficult question. You did shut down your Linux carefully before that boot-attempt? There are/were no errors on your HD? Which partition(s) were actually broken? -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
participants (1)
-
weissel@jupiter.ph-cip.uni-koeln.de