[PC-BSD Testing] USB Hard Drive Issues
dejamuse at yahoo.com
Wed Mar 31 21:33:19 PDT 2010
Doh! I just realized that when I went to re-install PCBSD I inadvertently selected the USB drive which explains why my system appeared to be untouched - it was.
I never even looked at the first drive in the drop down box - just assumed it would be the internal hard drive, adx. But instead it defaulted to my USB backup drive and of course overwrote everything that was there.
I guess I would recommend trying to idiot-proof the installation a bit more by making sure the default drive is internal (adx and not dax) and/or changing from a drop down box to radio buttons where none is selected as default to guard against something like this happening.
--- On Mon, 3/29/10, Brodey Dover <doverosx at gmail.com> wrote:
From: Brodey Dover <doverosx at gmail.com>
Subject: Re: [PC-BSD Testing] USB Hard Drive Issues
To: "PC-BSD Testing list" <testing at lists.pcbsd.org>
Date: Monday, March 29, 2010, 12:53 PM
have a bug submitted to the FreeBSD fellows. There was some
recoding going on with FreeBSD 8.0 and how it reads/handles file
systems on USB devices. Perhaps if anyone is willing, they can try
On Mon, Mar 29, 2010 at 6:55 AM, Kris Moore <kris at pcbsd.org> wrote:
> On 03/29/2010 14:51, Mike Bybee wrote:
> On Mon, Mar 29, 2010 at 7:24 AM, Ian Robinson <fitchkendall at gmail.com>
>> On Sun, Mar 28, 2010 at 3:00 PM, <testing-request at lists.pcbsd.org> wrote:
>>> Every time I boot up, the media folder? has an additional directory
>>> called disk, disk1,
and so on - now up to 9.? None of them is the USB drive.
>> It has been standard behavior that when you plug in a USB memory stick,
>> PCBSD creates a directory in /media to use as a mount point. The mount
>> point remains after you disconnect the memory stick. Each time you plug in
>> the same or another USB memory stick, the mount point increments (disk,
>> disk1, . . . disk9). The USB memory stick you plugged in will be mounted at
>> the highest number if you were to look at it in the "regular" Dolphin
>> directory tree. Because the previous mount points (disk, disk1) are passed
>> over, they should be empty. If you delete the mount points, the increment
>> sequence returns to disk, then disk1, etc.
>> It was also standard behavior that after you plugged in a USB memory
>> stick, camera, etc., you
could see it in "Places" and you could
>> "right-click" on the device icon in "Places" and choose to "Unmount
>> <Device_Name>" to safely remove it.
>> Here are some observed variations:
>> PCBSD 7.0.1 Behavior:
>> For an additional -- but unmounted (not listed in /etc/fstab) internal
>> hard drive -- "Places" shows a drive icon. Double clicking on the drive
>> icon mounts the drive to /media/<new_mount_point_name>. Right clicking on
>> the drive icon in "Places" and selecting "Unmount <Device_Name>, the drive
>> is unmounted and the /media/<new_mount_point_name> is removed from the
>> /media directory.
>> A USB hard disk (Seagate Free Agent 500 GB) formatted ntfs is not
>> auto-recognized. You have to mount it manually. An icon shows up
>> "Places" after mounting. You can right click and select "Unmount FreeAgent"
>> but I get an error message at the bottom of the Dolphin window that says:
>> " . . . org.freedesktop.Hal.Device.Volume.NotMountedByHal: Device to
>> unmount is not in /media/.hal-mtab so it is not mounted by HAL."
>> If i '# umount /mnt/<mount_point>, then the device icon disappears from
>> PCBSD 8.0 Behavior.
>> Jeff said: "It used to show a UFS volume in the places section of
>> Dolphin, but now shows 4 USB drives and none of them represent the content
>> of the drive . . ."
>> My PCBSD 8.0 behaves in the opposite fashion -- but is equally bizarre. I
>> get only one icon in "Places" but I get four new mount points in /media.
>> But, before
I got to that point, note that the drive (Segate Free Agent 500
>> GB) did not auto-recognize. I had to mount it in terminal to a mount point
>> I created (#mount_ntfs -o large /dev/da2s1 /media/USB_HD). Once that
>> command was issued, then the drive icon appeared in "Places" and four new
>> mount points appeared under /media (FreeAgent Drive, FreeAgent Drive-1,
>> FreeAgent Drive-2, FreeAgent Drive-3). The four new mount points were
>> In the Dolphin file tree, my designated mount point for the drive
>> (/media/USB_HD) also over-reported the 500 Gb drive properties at 7.3 TiB (I
>> Right clicking on the FreeAgent icon in "Places" did not produce a choice
>> for "Unmount FreeAgent".
>> Clicking on the FreeAgent icon in "Places" caused yet another mount point
appear in /media, and repeatedly clicking continued to increment the
>> mount points with each click with each new mount point empty of contents.
>> I did a umount from terminal without incident, but it did not remove the
>> FreeAgent icon from "Places." However, after the umount and the physical
>> unplugging of the USB connector cable, then the FreeAgent icon disappeared.
>> Next, when re-plugging the USB cable into the computer, the drive (1)
>> appeared automatically in "Places", (2) raised a "Devices Recently Plugged
>> In" window, which said "2 somethings are available". Clicking that last
>> message got me to (3) pop up window letting me know "A new device has been
>> detected. What do you want to do." Clicking on "Open in Dolphin" created
>> three new mount point in /media but otherwise did nothing
>> I mounted the drive in terminal, and yet another three mount points showed
>> How's that for behavior!
>> Ian Robinson
>> Salem, Ohio
>> Testing mailing list
>> Testing at lists.pcbsd.org
> I have a similar FreeAgent USB drive that I can't use at all with PC-BSD due
> to behaviors like above. I get an added prize, however, in the form of the
> machine rebooting itself if I try to copy anything to or from the
> Dmesg produces no errors beyond the USB notification.
> Under Win 7 on the same machine, the drive operates fine.
> Mike Bybee
> Most of the drives not being detected issues sound like HAL bugs, but I'm
> not sure how much effort should go into fixing it, since HAL is now
> depreciated and will be replaced by DeviceKit here soon:
> Your specific issue with a system reboot when copying sounds like a bug in
> the USB stack though. I would report that via FreeBSDs PR system, or
> directly on the USB mailing list, since thats something we need fixed on our
> end :)
> Kris Moore
> PC-BSD Software
> Testing mailing list
> Testing at lists.pcbsd.org
Testing mailing list
Testing at lists.pcbsd.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Testing