Dear all,
I have been trying to install FreeBSD 5.3, and having problems with partitions.
My HD configuration was as follows:
- one IBM 30 GB HD (seen as ad0 by FreeBSD booted from CD, and as /dev/hde by
Linux) with a FAT32 partition (WinME), a Ext3 partition (Mandrake Linux 8.1) and
a Linux Swap partition
- one Maxtor 200 GB HD (seen as ad1 by FreeBSD and as /dev/hdg by Linux) with a
FAT32 partition (no OS on it), a Ext3 partition (Slackware Linux 10.1) and 100
GB free space.
The OSes are booted by Lilo installed on the MBR of the first disk.
I made a 30GB partition for FreeBSD and installed the system on it, leaving the
MBRs untouched. It did give me a warning about wrong disk geometry, but
otherwise the installation seemed OK.
Now what happens is:
- WinME can't see the FAT32 partition on the Maxtor disk (let alone the other 
ones);
- Mandrake Linux and Lilo can't see any partition on the Maxtor disk (so I can't
boot the OSes on this disks);
- Knoppix 3.7 (a live Linux CD) can see the partitions on the Maxtor disk (even
the sub-partitions in the FreeBSD partitions - let me apologize here for not
using the proper FreeBSD terminology) but it can't mount them properly;
- FreeBSD (booted from CD) can see and mount everything properly.
A couple more notes:
- I made the partitions on the Maxtor CD with Slackware's fdisk;
- When I boot from the FreeBSD cd (or Freesbie) I need to choose safe mode, or
it will hang after detecting the Maxtor disk (maybe I should have taken this in
more account...).
Any idea on what went wrong and how to fix it? The data already on the Maxtor
disk are not critical, but I would prefer to recover them.
Thanks,
Marco



____________________________________________________________
Navighi a 4 MEGA e i primi 3 mesi sono GRATIS. 
Scegli Libero Adsl Flat senza limiti su http://www.libero.it


_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to