iH,
  Pulled an old disk lying around...
 and started mounting partitions in it.
The weird thing is that the first slice [~15GB] is said to be fat, but I
do have freebsd partitions on it:

denver:#mount|grep ad10
/dev/ad10s1a on /maxtor500GB (ufs, NFS exported, local, soft-updates)
/dev/ad10s1d on /maxtor500GB/var (ufs, local, soft-updates)
/dev/ad10s1f on /maxtor500GB/usr (ufs, local, soft-updates)
/dev/ad10s1e on /maxtor500GB/tmp (ufs, local, soft-updates)
/dev/ad10s3d on /maxtor500GB/data (ufs, NFS exported, local, soft-updates)
/dev/ad10s2d on /maxtor500GB/data2 (ufs, local, soft-updates)

denver:#fdisk /dev/ad10
******* Working on device /dev/ad10 *******
parameters extracted from in-core disklabel are:
cylinders=969021 heads=16 sectors/track=63 (1008 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=969021 heads=16 sectors/track=63 (1008 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 6 (0x06),(Primary DOS, 16 bit FAT (>= 32MB))
    start 63, size 31455207 (15358 Meg), flag 0
        beg: cyl 0/ head 1/ sector 1;
        end: cyl 1023/ head 254/ sector 63
The data for partition 2 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
    start 31455270, size 31455270 (15359 Meg), flag 80 (active)
        beg: cyl 1023/ head 255/ sector 63;
        end: cyl 1023/ head 254/ sector 63
The data for partition 3 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
    start 62910540, size 913857525 (446219 Meg), flag 0
        beg: cyl 1023/ head 255/ sector 63;
        end: cyl 1023/ head 254/ sector 63
The data for partition 4 is:
<UNUSED>
denver:#

There are what appears to be a freebsd base install from Jul 19/20th 2007
on /dev/ad10s1{a,d,e,f}

denver:#ls -l /maxtor500GB/tmp/
total 2
drwxrwxr-x  2 root  operator  512 Jul 20  2007 .snap

denver:#ls -l /maxtor500GB/
total 38
drwxrwxr-x   2 root  operator   512 Jul 20  2007 .snap
drwxr-xr-x   2 root  wheel     1024 Jul 19  2007 bin
drwxr-xr-x   7 root  wheel      512 Jul 19  2007 boot
..
....
denver:#df -hl|grep ad10
/dev/ad10s1a              496M     11M    445M     2%    /maxtor500GB
/dev/ad10s1d              989M    106K    910M     0%    /maxtor500GB/var
/dev/ad10s1f               16G     97M     15G     1%    /maxtor500GB/usr
/dev/ad10s1e              727M    580K    668M     0%    /maxtor500GB/tmp
/dev/ad10s3d              422G    384G    4.0G    99%    /maxtor500GB/data
/dev/ad10s2d               15G     11G    2.5G    81%    /maxtor500GB/data2


running sysinstall also show s1 as 'fat'

I've been writing/reading a lot of data from it just fine - Curios why s1
is being detect as a 'fat' partition and not a fbsd slice.
Have not tried to put this disk into a windows/another box...

]Peter[

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

Reply via email to