Hi all, I've got a new PC and I've just installed that:
On a 160 Gbytes HD, three partitions: hda1 with Windows 2000 (119 Gbytes), NTFS hda2 with a Linux swap partition (1 Gbyte) hda3 with an ext2 file system (40 Gbytes) My linux installation is a Debian Woody (just downloaded the image files using jigdo a month ago). My problem: after rebooting from Linux (ctrl+alt+del) the FS crashed. I was told to run fsck on /dev/hda3 manually, so I did. I had to use the -y option because the huge amount of question I was asked (several thousands). Windows 2000 worked fine. After running fsck Debian started fine again, but Windows 2000 FS didn't. It seemed as fsck had done something wrong on hda1... very strange. I had to install Windows 2000 from scratch again. Then, two days later I got the same error. Debian startup didn't work, I was told again to run fsck manually. Just to check, I rebooted and started Windows 2000: it worked fine. I run then fsck on /dev/hda3, rebooted, and hda1 was broken again (hda3 was clean). It seems clear to me that the fsck utility does something on hda1, even when run on hda3. Is it a known bug? I checked the first partition, and his FS type has been changed from NTFS to 0x14 :-?. The partition seems completely corrupted and unrecoverable. Now I'll re-install Windows 2000 from scratch, but I'd need some advice. That's what I'm doing: 1. Moving from ext2 to ext3 or ReiserFS. Which one? 2. Even after moving to ext3/ReiserFS, there's a danger (smaller) that hda3 brokes and I've to run fsck again. What can I do to prevent fsck to corrupt the first partition? Maybe moving the Linux partition to the HD beginning (so Linux would be at hda1 and windows at hda3) could help? Does anyone know why this happen? Has this happen to anyone else? Thanks, David desperated -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
