Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Firefox 10.05esr and seamonkey-2.7.2.en-US.os2.10.5 esr
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Trevor Hemsley  
View profile  
 More options Jun 28 2012, 12:50 pm
Newsgroups: mozilla.dev.ports.os2
From: "Trevor Hemsley" <Trevor.Hems...@mytrousers.ntlworld.com>
Date: Thu, 28 Jun 2012 11:50:49 -0500
Local: Thurs, Jun 28 2012 12:50 pm
Subject: Re: Firefox 10.05esr and seamonkey-2.7.2.en-US.os2.10.5esr
On Thu, 28 Jun 2012 10:02:24 UTC in mozilla.dev.ports.os2, David Arturo Macias

Corona <dmac...@mail.udg.mx> wrote:
> Trevor Hemsley wrote:
> >> SMART Self-test log structure revision number 1
> >> Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
> >> # 1  Extended offline    Completed: read failure       90%     10263        32618056
> >> # 2  Extended offline    Completed: read failure       90%     10261        32618056

> > And this bit doesn't look good either, 90% of the way through a long smart test,
> > it crapped out trying to read the same sector on two different runs.
> Many facts point to problems in HDD, so I am looking for a new one.
> I want a Sata III, 1.5 Tb size

I think you will be OK with this as long as you are up to date - os2dasd.dmd had
a 512GB limit until a few years ago for example but on eCS 2.x you should be OK
with all this. Having said that I've never booted an OS/2 system from a disk of
that size although I did have a Netcell RAID card in my OS/2 system for a long
time with a 640GB array and that was fine - but I didn't boot from it.

> But usual questions arise:

> - Should I replace only HDD or should I replace most hardware ?

That depends on the age of the rest of the hardware and its condition. I'm
running with a Core2Duo E6850 3GHz processor and a 5 year old motherboard here
and it's still plenty fast enough.

>   Is good time to up-grade, considering work to do  :-)
> - When ? Upgrading take a lot of time to prepare all OS involved
> - What ? It is not easy to find new hardware (MoBo, multi-core, cards,
> ... ) supported by ecs21
> - Size of HDD ? All seem go around 500 Gb line supported by ecs21
> without tricks

I just put a spare Crucial m4 128GB SSD into my main OS/2 machine and it has
made a *huge* difference. I went from an LSI MegaRAID Express 500 hardware RAID
controller with 128MB cache RAM and a pair of Fujitsu 15k rpm 73GB disks in RAID
1 to the SSD and my boot time has decreased from ~2 minutes to 22 seconds. It's
similarly speedy in general use though it's really too soon to tell how reliable
it will be and how it will slow down over time due to the lack of TRIM support
in OS/2. SSD prices have pretty much halved here in the UK in the last 6 weeks!
I paid only a little more for a new 256GB SSD two weeks ago than I did for this
128GB one in January 2012.

> For example, DFSee report 35 "bad spots"

That fits fairly well with the 31 pending sectors reported by SMART - it found
another 4 while it was scanning. It's definitely on its way out and you should
be backing up your critical files on a regular basis in case it dies completely.

> In other event, I have problems to update an SVN directory in J:
> partition, recently prepared for ecs21 tests with JFS
> ( my daily work is with ecs20, with these computer+HDD installed around
> 3.5 years )

> Playing with DFSee:DFSCHECK J:, it report problems with files in those
> directories

> An ecs20 CHKDSK J: show info included below, with main fact:
>    "CHKDSK  File system is dirty but is marked clean"

You will always get this if you run against a JFS partition with files that are
open. If using it with the /F switch refuses to run because it's in use then any
report without /F will be unreliable and report problems that don't really
exist. OTOH, if you are running it with /F and it is really checking it then you
do have  a problem.

--
Trevor Hemsley, Brighton, UK
Trevor dot Hemsley at ntlworld dot com


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.