Jeff | 1 Apr 06:33 2010
Picon

Re: USB Hard Drive Issues

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.

...Jeff


--- On Mon, 3/29/10, Brodey Dover <doverosx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

From: Brodey Dover <doverosx <at> gmail.com>
Subject: Re: [PC-BSD Testing] USB Hard Drive Issues
To: "PC-BSD Testing list" <testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org>
Date: Monday, March 29, 2010, 12:53 PM

I actually 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
-CURRENT.

On Mon, Mar 29, 2010 at 6:55 AM, Kris Moore <kris-E1R8x85rdljYtjvyW6yDsg@public.gmane.org> wrote:
> On 03/29/2010 14:51, Mike Bybee wrote:
>
> On Mon, Mar 29, 2010 at 7:24 AM, Ian Robinson <fitchkendall-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> wrote:
>>
>> On Sun, Mar 28, 2010 at 3:00 PM, <testing-request-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.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 in
>> "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
>> "Places."
>>
>>
>> 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
>> empty.
>>
>> 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
>> wish).
>>
>> 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
>> to 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 else.
>>
>> I mounted the drive in terminal, and yet another three mount points showed
>> up.
>>
>> How's that for behavior!
>>
>>
>> Ian Robinson
>> Salem, Ohio
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Testing mailing list
>> Testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org
>> http://lists.pcbsd.org/mailman/listinfo/testing
>>
>
> 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 drive.
> Dmesg produces no errors beyond the USB notification.
>
> Under Win 7 on the same machine, the drive operates fine.
>
> --
> Thanks,
> 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:
>
> http://en.wikipedia.org/wiki/DeviceKit
>
> Mike,
>
> 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 :)
>
> http://lists.freebsd.org/mailman/listinfo/freebsd-usb
>
>
>
> --
> Kris Moore
> PC-BSD Software
> iXsystems
>
> _______________________________________________
> Testing mailing list
> Testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org
> http://lists.pcbsd.org/mailman/listinfo/testing
>
>
_______________________________________________
Testing mailing list
Testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org
http://lists.pcbsd.org/mailman/listinfo/testing

_______________________________________________
Testing mailing list
Testing@...
http://lists.pcbsd.org/mailman/listinfo/testing
Kris Moore | 1 Apr 12:35 2010

Next Snapshot Available


I've just finished uploading the next snapshot of PC-BSD based upon 
8-Stable:

ftp://ftp.pcbsd.org/pub/snapshots/8/

There have been a fair number of fixes to the installer in this release. 
I've written a patch to "geli" allowing us to use passphrases
for the first time now. When you click to enable encryption, it'll 
prompt you for a password, and when you boot that
same password will be required to mount the disk. Also, I've been able 
to track down some bugs with the installer crashing and
rebooting spontaneously. If anybody still runs into a case where that 
happens, please send me as MUCH detail as possible about
the type of install being done, FS setup, point where it crashes, etc.

I'm finishing up some last enhancements to the installer now, and when 
that's in place it should be pretty much feature-complete
for 8.1 and we can begin working more on the desktop side of things. KDE 
4.4.x should be going into the ports tree here soon,
and I hope to have it in the next snapshot for us to play with.

Thanks again so much for your continual help in testing/improving PC-BSD!

8.1 TODO List:

http://wiki.pcbsd.org/index.php/PC-BSD_8.1_TODO

--

-- 
Kris Moore
PC-BSD Software
iXsystems
Kris Moore | 1 Apr 14:38 2010

Re: USB Hard Drive Issues

On 04/01/2010 04:33, Jeff wrote:
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.

...Jeff

I've just committed a fix so that it'll get sorted alphabetically, and ad0 will be the default (if it exists), hopefully this will be less confusing now.


-- Kris Moore PC-BSD Software iXsystems
_______________________________________________
Testing mailing list
Testing@...
http://lists.pcbsd.org/mailman/listinfo/testing
Kris Moore | 1 Apr 14:42 2010

Re: kioslave for file ???

On 03/30/2010 18:25, Walt Pawley wrote:
> On 3/30/10 9:30 AM +0000, Kris Moore wrote on Re: [PC-BSD
> Testing] kioslave for file ???
>
>    
>> On 03/30/2010 06:47, Walt Pawley wrote:
>>      
>>> Working with PC-BSD 7.1. Something has changed and I've been
>>> trying to find it for a couple of days, on and off as time has
>>> allowed. Mostly, I've managed to gain a thumping headache
>>> pawing through mounds of documentation, etc. Hera are some of
>>> the symptoms:
>>>
>>> Starting File Manager (Dolphin): URL cannot be listed file:///home/wump
>>>
>>> Clicking OK gets:  URL cannot be listed file:///usr/home/wump
>>>
>>> Dolphin does come up, but the file content is empty. Clicking
>>> the Root icon produces the error  URL cannot be listed file:///
>>>
>>> Clicking Network results in  URL cannot be listed remote:/
>>>
>>> Clicking Trash results in  URL cannot be listed trash:/
>>>
>>> Firing up File Manager (Administrator) results in: Could not
>>> start process. Unable to create io-slave: klauncher said:
>>> Unknown protocol 'file'.
>>>
>>> Other applications also fail attempting to use the file:
>>> protocol to access files though I'm not certain it's
>>> ubiquitous. Curiously, as of the last time I tested it, which
>>> was after noting much of the above behavior, typing the
>>> "file:///home/wump" into Firefox's location field resulted in a
>>> listing of the files in my home directory. I suspect that
>>> Firefox is not attempting to use KDE's libkio for this activity.
>>>
>>> I get the feeling this not a big job to fix ... IF one knows
>>> what to tweak. Anyone care to allay my ignorance?
>>>
>>>        
>> So at this point it sounds like dolphin isn't working at all, correct?
>> How about if you open a xterm / konsole, and run "tail -f
>> .xsession-errors" while trying to use dolphin. Any interesting messages
>> going by on the failure?
>>      
> Yup, Dolphin pretty much can't locate anything. I hope this is
> sufficiently interesting:
>
> ~$ tail -f .xsession-errors
> "
> SystemUpdater(1960): couldn't create slave: "Unable to create io-slave:
> klauncher said: Unknown protocol 'http'.
> "
> SystemUpdater(1960): couldn't create slave: "Unable to create io-slave:
> klauncher said: Unknown protocol 'http'.
> "
> SystemUpdater(1960): couldn't create slave: "Unable to create io-slave:
> klauncher said: Unknown protocol 'http'.
> "
> kdeinit4: preparing to launch /usr/local/kde4/bin/dolphin
> dolphin(85597) KLocalePrivate::initEncoding: Cannot resolve
> system encoding, defaulting to ISO 8859-1.
> [/usr/local/kde4/bin/nepomukservicestub] (ServerCore) new socket connection.
> Object::connect: No such signal DolphinView::redirection(KUrl,KUrl)
> Object::connect: No such signal DolphinView::redirection(KUrl,KUrl)
> dolphin(85597)/kdecore (trader)
> KServiceTypeTrader::defaultOffers: KServiceTypeTrader:
> serviceType  "ThumbCreator"  not found
> dolphin(85597)/kdecore (trader)
> KServiceTypeTrader::defaultOffers: KServiceTypeTrader:
> serviceType  "ThumbCreator"  not found
>
>
>    

Well, that really doesn't give a clear error on why it can't work :(

Was it working before and just stopped? Maybe something got corrupted in 
.kde4/?

--

-- 
Kris Moore
PC-BSD Software
iXsystems
Walt Pawley | 1 Apr 23:20 2010

Re: kioslave for file ???

On 4/1/10 12:42 PM +0000, Kris Moore wrote:

>On 03/30/2010 18:25, Walt Pawley wrote:
>> On 3/30/10 9:30 AM +0000, Kris Moore wrote on Re: [PC-BSD
>> Testing] kioslave for file ???
>>
>>
>>> On 03/30/2010 06:47, Walt Pawley wrote:
>>>
>>>> Working with PC-BSD 7.1. Something has changed and I've been
>>>> trying to find it for a couple of days, on and off as time has
>>>> allowed. Mostly, I've managed to gain a thumping headache
>>>> pawing through mounds of documentation, etc. Hera are some of
>>>> the symptoms:
>>>>
>>>> Starting File Manager (Dolphin): URL cannot be listed file:///home/wump
>>>>
>>>> Clicking OK gets:  URL cannot be listed file:///usr/home/wump
>>>>
>>>> Dolphin does come up, but the file content is empty. Clicking
>>>> the Root icon produces the error  URL cannot be listed file:///
>>>>
>>>> Clicking Network results in  URL cannot be listed remote:/
>>>>
>>>> Clicking Trash results in  URL cannot be listed trash:/
>>>>
>>>> Firing up File Manager (Administrator) results in: Could not
>>>> start process. Unable to create io-slave: klauncher said:
>>>> Unknown protocol 'file'.
>>>>
>>>> Other applications also fail attempting to use the file:
>>>> protocol to access files though I'm not certain it's
>>>> ubiquitous. Curiously, as of the last time I tested it, which
>>>> was after noting much of the above behavior, typing the
>>>> "file:///home/wump" into Firefox's location field resulted in a
>>>> listing of the files in my home directory. I suspect that
>>>> Firefox is not attempting to use KDE's libkio for this activity.
>>>>
>>>> I get the feeling this not a big job to fix ... IF one knows
>>>> what to tweak. Anyone care to allay my ignorance?
>>>>
>>>>
>>> So at this point it sounds like dolphin isn't working at all, correct?
>>> How about if you open a xterm / konsole, and run "tail -f
>>> .xsession-errors" while trying to use dolphin. Any interesting messages
>>> going by on the failure?
>>>
>> Yup, Dolphin pretty much can't locate anything. I hope this is
>> sufficiently interesting:
>>
>> ~$ tail -f .xsession-errors
>> "
>> SystemUpdater(1960): couldn't create slave: "Unable to create io-slave:
>> klauncher said: Unknown protocol 'http'.
>> "
>> SystemUpdater(1960): couldn't create slave: "Unable to create io-slave:
>> klauncher said: Unknown protocol 'http'.
>> "
>> SystemUpdater(1960): couldn't create slave: "Unable to create io-slave:
>> klauncher said: Unknown protocol 'http'.
>> "
>> kdeinit4: preparing to launch /usr/local/kde4/bin/dolphin
>> dolphin(85597) KLocalePrivate::initEncoding: Cannot resolve
>> system encoding, defaulting to ISO 8859-1.
>> [/usr/local/kde4/bin/nepomukservicestub] (ServerCore) new socket connection.
>> Object::connect: No such signal DolphinView::redirection(KUrl,KUrl)
>> Object::connect: No such signal DolphinView::redirection(KUrl,KUrl)
>> dolphin(85597)/kdecore (trader)
>> KServiceTypeTrader::defaultOffers: KServiceTypeTrader:
>> serviceType  "ThumbCreator"  not found
>> dolphin(85597)/kdecore (trader)
>> KServiceTypeTrader::defaultOffers: KServiceTypeTrader:
>> serviceType  "ThumbCreator"  not found
>>
>>
>>
>
>Well, that really doesn't give a clear error on why it can't work :(

Yeah. I most certainly believe that!

>Was it working before and just stopped? Maybe something got corrupted in
>.kde4/?

That is pretty much the way I remember it. I supposed that some
code must have gotten dinged up and was shorting out some
connection. I've been hunting for that ding ever since ...
until late last night. For reasons that escape me, the problem
seems to have cleared up after a system restart. Why this
should have happened is inexplicable because I've rebooted the
system numerous times since with the problem persisting
throughout. Alikazzam!
--

-- 

Walter M. Pawley <walt@...>
Wump Research & Company
676 River Bend Road, Roseburg, OR 97471
         541-672-8975
Kris Moore | 2 Apr 11:41 2010

Re: kioslave for file ???

On 04/01/2010 21:20, Walt Pawley wrote:
>
> Yeah. I most certainly believe that!
>
>    
>> Was it working before and just stopped? Maybe something got corrupted in
>> .kde4/?
>>      
> That is pretty much the way I remember it. I supposed that some
> code must have gotten dinged up and was shorting out some
> connection. I've been hunting for that ding ever since ...
> until late last night. For reasons that escape me, the problem
> seems to have cleared up after a system restart. Why this
> should have happened is inexplicable because I've rebooted the
> system numerous times since with the problem persisting
> throughout. Alikazzam!
>    

Well, chock it up to a KDE4 oddity then I guess. If you can duplicate it 
let us know, since we'll want to make sure
it is fixed in 4.4.x here soon :)

--

-- 
Kris Moore
PC-BSD Software
iXsystems
Picon

Re: kioslave for file ???

On 04/02/2010 05:41, Kris Moore wrote:
> On 04/01/2010 21:20, Walt Pawley wrote:
>>
>> Yeah. I most certainly believe that!
>>
>>> Was it working before and just stopped? Maybe something got 
>>> corrupted in
>>> .kde4/?
>> That is pretty much the way I remember it. I supposed that some
>> code must have gotten dinged up and was shorting out some
>> connection. I've been hunting for that ding ever since ...
>> until late last night. For reasons that escape me, the problem
>> seems to have cleared up after a system restart. Why this
>> should have happened is inexplicable because I've rebooted the
>> system numerous times since with the problem persisting
>> throughout. Alikazzam!
>
> Well, chock it up to a KDE4 oddity then I guess. If you can duplicate 
> it let us know, since we'll want to make sure
> it is fixed in 4.4.x here soon :)
>
>
Murphy Law?
Arthur Koziol | 6 Apr 19:30 2010

Freebsd 8.1 TODO wiki is up now

http://wiki.freebsd.org/Releng/8.1TODO

Release date of July 9th. Should we start taking bets on that date? My 
money is in August 30th.
Kris Moore | 6 Apr 20:25 2010

Re: Freebsd 8.1 TODO wiki is up now

My guess would be early August.  I'm keeping an eye on this though so we can try to have pcbsd 8.1 out shortly
thereafter.  

Arthur Koziol <A-Koziol@...> wrote:

>http://wiki.freebsd.org/Releng/8.1TODO
>
>Release date of July 9th. Should we start taking bets on that date? My 
>money is in August 30th.
>_______________________________________________
>Testing mailing list
>Testing@...
>http://lists.pcbsd.org/mailman/listinfo/testing
Arthur Koziol | 6 Apr 20:41 2010

Re: Freebsd 8.1 TODO wiki is up now

Have you heard anything on how well Grand Central Dispatch is working?

> My guess would be early August.  I'm keeping an eye on this though so we can try to have pcbsd 8.1 out shortly thereafter.
>
> Arthur Koziol<A-Koziol@...>  wrote:
>
>    
>> http://wiki.freebsd.org/Releng/8.1TODO
>>
>> Release date of July 9th. Should we start taking bets on that date? My
>> money is in August 30th.
>> _______________________________________________
>> Testing mailing list
>> Testing@...
>> http://lists.pcbsd.org/mailman/listinfo/testing
>>      
> _______________________________________________
> Testing mailing list
> Testing@...
> http://lists.pcbsd.org/mailman/listinfo/testing
>    

Gmane