Kris Moore | 1 Dec 2009 23:47

Re: Removing Stale OOo v2.4.2 PBI from Update Manager

Ian Robinson wrote:
> Update Manager in  PCBSD 7.1.1 constantly states there is an upgrade to
> OpenOffice-EN 2.4.2_3 even though I installed OpenOffice 3.x some time ago.
> I believe OOo v2.4 is left over from the time when PCBSD 7.x came with OOo
> v2.4.  I want to get rid of the "update" notice for a PBI I no longer use.
> 
> Ordinarily one can just delete the program directory in
> /Programs/≤Application_Name>.  On my system, OpenOffice-EN3.0.1 is listed
> and there  is a corresponding directory for it at
> /Programs/OpenOffice-EN3.0.1.  However, I cannot find an entry in /Programs
> for OOo v2.4.
> 
> Another way is the use the "Software & Updates" tool at the PBI Manager tab,
> but it likewise does not list OOo v2.4 in the inventory of PBIs.
> 
> I do have a hidden OOo directories in my directory -- .openoffice.org (where
> v3 is located) and .openoffice.org2 (where v2 is located).  In order to
> disable the Update Manager's reference to v2.4, can I simply remove the
> hidden directory at /usr/home/.openoffice.org2?  Alternatively is there a
> better way to rid myself of the pesky reminder?
> 
> Ian Robinson
> Salem, Ohio
> 

Ian,

The odds are that for some reason the OO 2.4 entry didn't get removed 
from the installed PBIs conf file. Take a look at this file on your system:

(Continue reading)

Jeff | 2 Dec 2009 08:09
Picon
Favicon

Re: Support for J-Micron?

I tried that at first but ad0 and ad1 are the two main drives and I'd assume they'd be the same since it's a RAID-1, mirrored.

Mounting either of those drives shows the contents of the system.



--- On Mon, 11/30/09, doverosx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org <doverosx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

From: doverosx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org <doverosx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PC-BSD Testing] Support for J-Micron?
To: "PC-BSD Testing list" <testing-Fhbtn2kkCAMgLfnEB/6iFw@public.gmane.org.org>
Date: Monday, November 30, 2009, 6:51 PM

Josh Paetzel wrote:
>
> On Nov 30, 2009, at 4:59 PM, doverosx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
> <mailto:doverosx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>>>
>> Okay I see ar0, that is for a raid array and I see ad1 and ad0.
>>
>> If I assume ad1 is connected to the J-micron controller
>>
>> you'd mount it like /dev/ad1s1 /media/Backup
>>
>> ata is the controller and so you must mount block devices..in other
>> words a device that has a block type file structure. Hard drives tend to
>> be part of ad0, ad1, ad2, ad3, etc. RAID arrays are parte of ar0, ar1,
>> ar2, ar3, etc.
>>
>> ad0s1 denotes a "slice" or low-level partition and ad0s1a denotes a
>> high-level partition like /, /etc, /var, etc.
>>
>> Good luck and let us know ;)!
>> _______________________________________________
>> Testing mailing list
>> Testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org <mailto:Testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org>
>> http://lists.pcbsd.org/mailman/listinfo/testing
>
> Judging by the fact that the same slices and partitions exist on ad0
> and ad1 it's very likely those are the components of the RAID array.
>  I'd recommend against mounting them directly while the RAID array is
> mounted unless you know for a fact that they aren't the raw components.
>
> Thanks,
>
> Josh Paetzel
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Testing mailing list
> Testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org
> http://lists.pcbsd.org/mailman/listinfo/testing
>   
Good point...I was trying to convey that but clearly I failed and my
caffeine levels are wearing off :p
_______________________________________________
Testing mailing list
Testing <at> lists.pcbsd.org
http://lists.pcbsd.org/mailman/listinfo/testing

_______________________________________________
Testing mailing list
Testing@...
http://lists.pcbsd.org/mailman/listinfo/testing
Josh Paetzel | 2 Dec 2009 13:21
Favicon

Re: Support for J-Micron?


On Dec 2, 2009, at 1:09 AM, Jeff <dejamuse-/E1597aS9LQAvxtiuMwx3w@public.gmane.org> wrote:

I tried that at first but ad0 and ad1 are the two main drives and I'd assume they'd be the same since it's a RAID-1, mirrored.

Mounting either of those drives shows the contents of the system.

Couple of things:

The last eSATA controller I had didn't support hot plugging in FreeBSD. A drive attached when the system booted would be seen, but the system would not recognize drives attached after the system was booted. 

PATA supports two devices per controller, generally refered to as a master and a slave. The controller cannot access both devices simultaniously. In a perfect world the devices in your mirror would be on seperate controllers. I don't know how smart the ar driver is about reads, but theoretically having the drives on seperate controllers would allow for two concurrent reads simultaniously.  It could also allow for better resiliancy in the case of an unclean shutdown. In your current setup, writes are always serialized. If the system were to crash during a write the mirror would almost certainly need to be resynced.  Anyways, you might contemplate moving the drive that is the primary slave (ad1) to being on the other IDE controller. It may or may not have some tangible benefits, in theory it should. 

Thanks,

Josh Paetzel
_______________________________________________
Testing mailing list
Testing@...
http://lists.pcbsd.org/mailman/listinfo/testing
Jeff | 2 Dec 2009 14:05
Picon
Favicon

Re: Support for J-Micron?

The RAID array is managed by an onboard ROM based controller, Intel matrix.

I previously had my system setup as RAID - 0 but it failed after a few months. Assuming a drive had failed I replaced both and the array broke again.  Gave up on RAID - 0.

Guess I'll have to give up on eSATA for now and just use the USB connection.

...Jeff

--- On Wed, 12/2/09, Josh Paetzel <josh <at> tcbug.org> wrote:

From: Josh Paetzel <josh-uIPEzr5JHgjYtjvyW6yDsg@public.gmane.org>
Subject: Re: [PC-BSD Testing] Support for J-Micron?
To: "PC-BSD Testing list" <testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org>
Cc: "PC-BSD Testing list" <testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org>
Date: Wednesday, December 2, 2009, 7:21 AM


On Dec 2, 2009, at 1:09 AM, Jeff <dejamuse-/E1597aS9LQAvxtiuMwx3w@public.gmane.org> wrote:

I tried that at first but ad0 and ad1 are the two main drives and I'd assume they'd be the same since it's a RAID-1, mirrored.

Mounting either of those drives shows the contents of the system.

Couple of things:

The last eSATA controller I had didn't support hot plugging in FreeBSD. A drive attached when the system booted would be seen, but the system would not recognize drives attached after the system was booted. 

PATA supports two devices per controller, generally refered to as a master and a slave. The controller cannot access both devices simultaniously. In a perfect world the devices in your mirror would be on seperate controllers. I don't know how smart the ar driver is about reads, but theoretically having the drives on seperate controllers would allow for two concurrent reads simultaniously.  It could also allow for better resiliancy in the case of an unclean shutdown. In your current setup, writes are always serialized. If the system were to crash during a write the mirror would almost certainly need to be resynced.  Anyways, you might contemplate moving the drive that is the primary slave (ad1) to being on the other IDE controller. It may or may not have some tangible benefits, in theory it should. 

Thanks,

Josh Paetzel

-----Inline Attachment Follows-----

_______________________________________________
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
Picon

Re: Support for J-Micron?

Jeff wrote:
> The RAID array is managed by an onboard ROM based controller, Intel 
> matrix.
>
> I previously had my system setup as RAID - 0 but it failed after a few 
> months. Assuming a drive had failed I replaced both and the array 
> broke again.  Gave up on RAID - 0.
>
> Guess I'll have to give up on eSATA for now and just use the USB 
> connection.
>
> ...Jeff
>
> --- On *Wed, 12/2/09, Josh Paetzel /<josh@...>/* wrote:
>
>
>     From: Josh Paetzel <josh@...>
>     Subject: Re: [PC-BSD Testing] Support for J-Micron?
>     To: "PC-BSD Testing list" <testing@...>
>     Cc: "PC-BSD Testing list" <testing@...>
>     Date: Wednesday, December 2, 2009, 7:21 AM
>
>
>     On Dec 2, 2009, at 1:09 AM, Jeff <dejamuse@...
>     </mc/compose?to=dejamuse@...>> wrote:
>
>>     I tried that at first but ad0 and ad1 are the two main drives and
>>     I'd assume they'd be the same since it's a RAID-1, mirrored.
>>
>>     Mounting either of those drives shows the contents of the system.
>>
>
>     Couple of things:
>
>     The last eSATA controller I had didn't support hot plugging in
>     FreeBSD. A drive attached when the system booted would be seen,
>     but the system would not recognize drives attached after the
>     system was booted. 
>
>     PATA supports two devices per controller, generally refered to as
>     a master and a slave. The controller cannot access both devices
>     simultaniously. In a perfect world the devices in your mirror
>     would be on seperate controllers. I don't know how smart the ar
>     driver is about reads, but theoretically having the drives on
>     seperate controllers would allow for two concurrent reads
>     simultaniously.  It could also allow for better resiliancy in the
>     case of an unclean shutdown. In your current setup, writes are
>     always serialized. If the system were to crash during a write the
>     mirror would almost certainly need to be resynced.  Anyways, you
>     might contemplate moving the drive that is the primary slave (ad1)
>     to being on the other IDE controller. It may or may not have some
>     tangible benefits, in theory it should. 
>
>     Thanks,
>
>     Josh Paetzel
>
>     -----Inline Attachment Follows-----
>
>     _______________________________________________
>     Testing mailing list
>     Testing@... </mc/compose?to=Testing@...>
>     http://lists.pcbsd.org/mailman/listinfo/testing
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Testing mailing list
> Testing@...
> http://lists.pcbsd.org/mailman/listinfo/testing
>   
Unfortunately, that seems to be the case...only thing I can find is 
atacontrol..

# atacontrol detach ataX && atacontrol attach ataX

Brodey
Arthur | 3 Dec 2009 03:47

Re: Support for J-Micron?


>The RAID array is managed by an onboard ROM based controller, Intel matrix.
>
>I previously had my system setup as RAID - 0 but it failed after a 
>few months. Assuming a drive had failed I replaced both and the 
>array broke again.  Gave up on RAID - 0.
>
>Guess I'll have to give up on eSATA for now and just use the USB connection.
>
>...Jeff

Jeff,

Is the BIOS on this motherboard up to date? I know sometimes with 
BIOS updates they also update the firmware / ROM of the RAID 
controller to fix bugs. Have you checked that out?

Arthur 
Ian Robinson | 3 Dec 2009 06:35
Picon

Re: Testing Digest, Vol 35, Issue 2

On Wed, Dec 2, 2009 at 3:00 PM, <testing-request <at> lists.pcbsd.org> wrote:
 
Today's Topics:
  1. Re: Removing Stale OOo v2.4.2 PBI from Update     Manager (Kris Moore)

Message: 1
Date: Tue, 01 Dec 2009 17:47:36 -0500
From: Kris Moore <kris-hU3oy4EhJ9EAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PC-BSD Testing] Removing Stale OOo v2.4.2 PBI from
       Update  Manager
To: PC-BSD Testing list <testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org>
Message-ID: <4B159D08.20207 <at> pcbsd.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Ian Robinson wrote:
> Update Manager in  PCBSD 7.1.1 constantly states there is an upgrade to
> OpenOffice-EN 2.4.2_3 even though I installed OpenOffice 3.x some time ago.
> I believe OOo v2.4 is left over from the time when PCBSD 7.x came with OOo
> v2.4.  I want to get rid of the "update" notice for a PBI I no longer use.
>
> Ordinarily one can just delete the program directory in
> /Programs/<Application_Name>.  On my system, OpenOffice-EN3.0.1 is listed
> and there  is a corresponding directory for it at
> /Programs/OpenOffice-EN3.0.1.  However, I cannot find an entry in /Programs
> for OOo v2.4.
>
> Another way is the use the "Software & Updates" tool at the PBI Manager tab,
> but it likewise does not list OOo v2.4 in the inventory of PBIs.
>
> I do have a hidden OOo directories in my directory -- .openoffice.org (where
> v3 is located) and .openoffice.org2 (where v2 is located).  In order to
> disable the Update Manager's reference to v2.4, can I simply remove the
> hidden directory at /usr/home/.openoffice.org2?  Alternatively is there a
> better way to rid myself of the pesky reminder?
>
> Ian Robinson
> Salem, Ohio
>

Ian,

The odds are that for some reason the OO 2.4 entry didn't get removed
from the installed PBIs conf file. Take a look at this file on your system:

/Programs/.config/ProgList

Look for a duplicate OpenOffice entry in there, and remove its entire
section. Be careful though, you don't want to mess up the formatting of
this file if possible. Best make a backup copy first :)

--

Kris Moore
PC-BSD Software
http://www.pcbsd.com



Dear Kris,

I found the file, and it was no surprise to find its contents matched the list of installed PBI's.  However there was no OO 2.4 entry.  Only the entry for OO 3.x

[ Program Entry ]
ProgName: OpenOffice-EN
ProgVer: 3.0.1

etc.

Thus the problem is coming from somewhere else and remains at large.  Perhaps it is only an anomaly, and it is certainly more trivial than critical, and even less important now that you are working hard to bring out PCBSD  8.0. So, please don't waste time on the problem and do the more important work towards 8.0.

Ian Robinson
Salem, Ohio
_______________________________________________
Testing mailing list
Testing@...
http://lists.pcbsd.org/mailman/listinfo/testing
Jeff | 3 Dec 2009 11:13
Picon
Favicon

Re: Support for J-Micron?

I didn't see anything in the last few  BIOS updates relating to the RAID ROM.

Now I have just seen my new RAID - 1 reporting degraded after a system crash.

A little more Googling and I found numerous references to exactly these problems with FreeBSD, so guess I'll have to get rid of the array.  I wonder if it's possible to just return the drives to non-RAID config without a problem.  I assume so since the system still boots up fine.  Just one drive reporting errors.

--- On Wed, 12/2/09, Arthur <A-Koziol-QtYOAdWFdlQ@public.gmane.org> wrote:

From: Arthur <A-Koziol <at> neiu.edu>
Subject: Re: [PC-BSD Testing] Support for J-Micron?
To: "PC-BSD Testing list" <testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org>
Date: Wednesday, December 2, 2009, 9:47 PM


>The RAID array is managed by an onboard ROM based controller, Intel matrix.
>
>I previously had my system setup as RAID - 0 but it failed after a
>few months. Assuming a drive had failed I replaced both and the
>array broke again.  Gave up on RAID - 0.
>
>Guess I'll have to give up on eSATA for now and just use the USB connection.
>
>...Jeff

Jeff,

Is the BIOS on this motherboard up to date? I know sometimes with
BIOS updates they also update the firmware / ROM of the RAID
controller to fix bugs. Have you checked that out?

Arthur

_______________________________________________
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
Josh Paetzel | 3 Dec 2009 14:32
Favicon

Re: Support for J-Micron?

I've had very poor experiences in the past with BIOS RAID solutions. You should be able to boot off of the native device just fine. You also might find geom_mirror an acceptable RAID solution. Regardless of what you use for RAID you might consider moving ad1 to the other IDE controller (assuming there is one)

Thanks,

Josh Paetzel

On Dec 3, 2009, at 4:13 AM, Jeff <dejamuse-/E1597aS9LQAvxtiuMwx3w@public.gmane.org> wrote:

I didn't see anything in the last few  BIOS updates relating to the RAID ROM.

Now I have just seen my new RAID - 1 reporting degraded after a system crash.

A little more Googling and I found numerous references to exactly these problems with FreeBSD, so guess I'll have to get rid of the array.  I wonder if it's possible to just return the drives to non-RAID config without a problem.  I assume so since the system still boots up fine.  Just one drive reporting errors.

--- On Wed, 12/2/09, Arthur <A-Koziol-QtYOAdWFdlQ@public.gmane.org> wrote:

From: Arthur <A-Koziol-QtYOAdWFdlQ@public.gmane.org>
Subject: Re: [PC-BSD Testing] Support for J-Micron?
To: "PC-BSD Testing list" <testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org>
Date: Wednesday, December 2, 2009, 9:47 PM


>The RAID array is managed by an onboard ROM based controller, Intel matrix.
>
>I previously had my system setup as RAID - 0 but it failed after a
>few months. Assuming a drive had failed I replaced both and the
>array broke again.  Gave up on RAID - 0.
>
>Guess I'll have to give up on eSATA for now and just use the USB connection.
>
>...Jeff

Jeff,

Is the BIOS on this motherboard up to date? I know sometimes with
BIOS updates they also update the firmware / ROM of the RAID
controller to fix bugs. Have you checked that out?

Arthur

_______________________________________________
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
Arthur Koziol | 3 Dec 2009 14:48

Re: Support for J-Micron?

On 12/03/2009 4:13 AM, Jeff wrote:
I didn't see anything in the last few  BIOS updates relating to the RAID ROM.

Now I have just seen my new RAID - 1 reporting degraded after a system crash.

A little more Googling and I found numerous references to exactly these problems with FreeBSD, so guess I'll have to get rid of the array.  I wonder if it's possible to just return the drives to non-RAID config without a problem.  I assume so since the system still boots up fine.  Just one drive reporting errors.

That's too bad. Hopefully better support will come down the line.

Arthur
_______________________________________________
Testing mailing list
Testing@...
http://lists.pcbsd.org/mailman/listinfo/testing

Gmane