After the install of odyssey-rc (iso images from ftp.free.fr mirror
dated october 12, 2000) my hdb fat32 was unusuable under windows and
linux
1-config:
dell xpsm200 pentium mmx 200
ide drives :
primary ide master hda MAXTOR 90871U2 cyl 16383 heads 16 s 63 8,4 go
hda1 win98 fat32 3 go
hda2 to hda7 linux partitions
slave hdb Western digital caviar 33100 WDAC33100-18H cyl
6136 heads 16 s 63 3,4 go
hdb1 win98 fat32 3,4 go
no linux partition at all on this drive (but this
drive has been used in the past as a primary master with lilo on the MBR
)
2- circumstances:
I simply run an install (expert mode) when diskdrake prompted I made a
lot of changes to linux partitions on hda
but no change at all to hdb
when I used diskdrake no particular messages were dislpayed everything
looked fine the same when I closed diskdrake no messages, everything
went fine.
it is only when trying to reboot under windows I realised that
although I didn't make any change to hdb partitions diskdrake screwed up
the partition table of this drive making it unusuable under windows and
unreadeable by linux fdisk .
windows scandisk froze when trying to check/repair this drive
only windows fdisk allowed me to remove/recreate partition on this drive
3- thoughts
the next reboot under linux showed hdb1 and hdb5 .. he he.. why hdb5 ??
I'm supposed to have only one partition on this drive . I then realised
that for some reason there was a small empty parttion (about 4 meg) at
the beginnig of the disk . this partition was not seen by windows, (may
be seen by diskdrake but if so, the graphical representation was so thin
(only 4 meg) I coukdn't see it !!!). may be this caused the problem
whith disdrake .
4- suggestions:
I feel something is still not working in diskdrake and the final 7.2
should not be released whithout fixing diskdrake first.
by the way why can't we anymore choose to use diskdruid or fdisk during
the partitionning stage ???
