mount WD 1TB usb hard drive

uname -a gives:
Code: 
FreeBSD freebsd 5.4-RELEASE FreeBSD 5.4-RELEASE #0: Sun May  8 10:21:06 UTC 2005                                   
[email]root@harlow.cse.buffalo.edu[/email]:/usr/obj/usr/src/sys/GENERIC  i386
 
fdisk gives

Code: 
******* Working on device /dev/da0 *******
parameters extracted from in-core disklabel are:
cylinders=4427 heads=255 sectors/track=63 (16065 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=4427 heads=255 sectors/track=63 (16065 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 165 (0xa5),(FreeBSD/NetBSD/386BSD)
    start 63, size 69625647 (33996 Meg), flag 80 (active)
        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 69625710, size 1494045 (729 Meg), flag 0
        beg: cyl 1023/ head 255/ sector 63;
        end: cyl 1023/ head 254/ sector 63
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>
 
Judging for fdisk's output your system isn't recognizing the USB disk. Can you past the full contents of dmesg after inserting the USB disk?
 
demsg gives

Code: 
da1: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled
da1: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C)
Mounting root from ufs:/dev/da0s1a
WARNING: / was not properly dismounted
WARNING: /home was not properly dismounted
WARNING: /tmp was not properly dismounted
WARNING: /usr was not properly dismounted
/usr: mount pending error: blocks 4 files 1
WARNING: /var was not properly dismounted
umass0: Western Digital External HDD, rev 2.00/1.75, addr 3
umass0: at uhub0 port 1 (addr 3) disconnected
umass0: detached
umass0: Western Digital External HDD, rev 2.00/1.75, addr 3
 
USB drives are controlled by the SCSI driver.

Type 'camcontrol /devlist'

This will show the drive most likely as da0. Then you will need to append the slice, most likely as da0s1.

I have a Western Digital Mybook 1TB USB drive preformatted for Windows and mounted it this way:

Code: 
mount -o large -t msdosfs /dev/da0s1 /mountpoint

That showed the MS files preloaded on the new drive.

I then went to format it in sysinstall and disklabel but got an error when trying to write the partition to the drive, something like: "can't write to device da0s1".

So now I'm stuck. Not sure why I can't write to it, since it was recognized by the disklabel editor. Some kind of write protect in Mybook or something? Thought I saw a post somewhere about that.
 
You can't format mounted filesystem....

Also sysinstall only supports UFS :)


NOTE: also MBR by definition is limited and doesn't support 1TB drives... you need gpt, which isn't supported by sysinstall. but you can do everything in fixit mode :D

I've told you probably more than you asked [i think] :D
 
phewww...

you guys are talking way over my head...

found another drive I plugged in.
Code: 
umass0: Maxtor OneTouch, rev 2.00/2.00, addr 2
umass0: Get Max Lun not supported (STALLED)
da2 at umass-sim0 bus 0 target 0 lun 0
da2:<Maxtor OneTouch 0201> Fixed Direct Access SCSI-0 device
da2: 1.000MB/s transfers
da2: 117246MB

So this one is recognized and has about 115 GB free
how to mount this one ?
(pls consider I am a noob.)
 
when I try to mount:
Code: 
mount: /dev/da2s1 on /backup: incorrect super block

How do I know what comes after da2 ?
 
Don't know what that error means.

Why don't you plug the WD back in and just format it for FBSD?

Follow these instructions as I did on my WD 1TB drive. You'll likely use the whole disk for FBSD and a single slice, as I did.

After formatting it reboot and type 'camcontrol devlist' to see what the device is, eg, da1. Remember, external USB drives are considered SCSI drives. If you formatted it as a single slice, then mount that slice:

mount /dev/da1s1 /backup
 
&quot said:
Oh, you're right.... [just checked wikipedia]
Click to expand...
You can easily remember it, logically, without having to check: the MBR uses a 32-bit int/dword to store the BIOS partition size, so the maximum supported is 4GB (2^32) * 512 bytes (the typical size of a sector) = 2048GB = 2TB. Easy. :)
 
djemmers said:
when I try to mount:
Code: 
mount: /dev/da2s1 on /backup: incorrect super block

How do I know what comes after da2 ?
Click to expand...
You can check the MBR using % fdisk /dev/da2.
The slice may be FAT formatted. If it is, try mounting it using the -t msdosfs option.
 
You must log in or register to reply here.
Back
Top