Firefox 10.05esr and seamonkey-2.7.2.en-US.os2.10.5esr

[Dave Yeo]

Firefox 10.05esr has been released. I've also rebuilt SeaMonkey 2.7.2
with 10.05. Available at netlabs, users of 10.04 are encouraged to
upgrade for the latest security fixes.
No OS/2 specific changes in this release.
https://www.mozilla.org/en-US/firefox/10.0.5/releasenotes/
https://www.mozilla.org/security/known-vulnerabilities/firefoxESR.html
Dave
ps I'll upload Thunderbird 10.05 over the weekend

[Harald Kamm]

On Fri, 8 Jun 2012 06:20:39 UTC, Dave Yeo <dave....@gmail.com> wrote:

Hi Dave,

thanks so much! Do you have any hint to make Forecastfox work again? I always get the
error message "Connection error".

Thanks again, Harald

--

[Mark Dodel]

On Fri, 8 Jun 2012 10:12:33 UTC, "Harald Kamm"
<harald.k...@bnv-bamberg.de> wrote:

-> On Fri, 8 Jun 2012 06:20:39 UTC, Dave Yeo <dave....@gmail.com> wrote:
->
-> Hi Dave,
->
-> thanks so much! Do you have any hint to make Forecastfox work again? I always get the
-> error message "Connection error".
->
-> Thanks again, Harald

I see the same thing and have for several releases of FF10. I'll have
to try previous releases to see where it started. I searched
Forecastfox support for that error and didn't find anything useful. I
also reset the settings for the addon but same thing. I get something
similar for Facebook Chat " Unable to connect to chat. Check your
internet connection." No idea if it is related.

Mark

->
-> > Firefox 10.05esr has been released. I've also rebuilt SeaMonkey 2.7.2
-> > with 10.05. Available at netlabs, users of 10.04 are encouraged to
-> > upgrade for the latest security fixes.
-> > No OS/2 specific changes in this release.
-> > https://www.mozilla.org/en-US/firefox/10.0.5/releasenotes/
-> > https://www.mozilla.org/security/known-vulnerabilities/firefoxESR.html
-> > Dave
-> > ps I'll upload Thunderbird 10.05 over the weekend
->
->


--
From the eComStation 2.1 GA desktop of Mark Dodel

Warpstock 2011 - http://www.warpstock.org
Warpstock Europe 2011 - http://www.warpstock.eu

[Dave Yeo]

Mark Dodel wrote:
> On Fri, 8 Jun 2012 10:12:33 UTC, "Harald Kamm"
> <harald.k...@bnv-bamberg.de> wrote:
>
> -> On Fri, 8 Jun 2012 06:20:39 UTC, Dave Yeo<dave....@gmail.com> wrote:
> ->
> -> Hi Dave,
> ->
> -> thanks so much! Do you have any hint to make Forecastfox work again? I always get the
> -> error message "Connection error".
> ->
> -> Thanks again, Harald
>
> I see the same thing and have for several releases of FF10. I'll have
> to try previous releases to see where it started. I searched
> Forecastfox support for that error and didn't find anything useful. I
> also reset the settings for the addon but same thing. I get something
> similar for Facebook Chat " Unable to connect to chat. Check your
> internet connection." No idea if it is related.

I think there is a subtle bug somewhere where Firefox is reporting to
add-ons that it is off-line even though it is online. Where I have no
idea. It might be possible to hack the addition to ignore the off-line
status, somebody did that with a different add-on.
Dave

[Ray Davison]

Dave Yeo wrote:
> I've also rebuilt SeaMonkey 2.7.2 with 10.05. Available at netlabs,

Where?

Ray

[Steve Wendt]

On 06/08/12 04:30 pm, Ray Davison wrote:

>> I've also rebuilt SeaMonkey 2.7.2 with 10.05. Available at netlabs,
>
> Where?

ftp://ftp.netlabs.org/incoming/mozilla/seamonkey-2.7.2.en-US.os2.10.5esr.zip

As usual, direct links are available from here:
http://www.os2bbs.com/os2news/Warpzilla.html

[Steve Wendt]

On 06/07/12 11:20 pm, Dave Yeo wrote:

> I've also rebuilt SeaMonkey 2.7.2 with 10.05.

> No OS/2 specific changes in this release.

For what it's worth, I tried enabling Flashgot again. RMB crash
produced an entry in popuplog.os2 (no exceptq log):

06-08-2012 16:53:10 SYS3171 PID 0305 TID 0001 Slot 0092
D:\OS2APPS\SEAMONKEY\SEAMONKEY.EXE
c0000005
1d1e16c6
P1=00000002 P2=0002fff0 P3=XXXXXXXX P4=XXXXXXXX
EAX=2004c9a0 EBX=00000000 ECX=0ff2bf70 EDX=101ced80
ESI=000300a0 EDI=206ae4a0
DS=0053 DSACC=f0f3 DSLIM=ffffffff
ES=0053 ESACC=f0f3 ESLIM=ffffffff
FS=150b FSACC=00f3 FSLIM=00000030
GS=0000 GSACC=**** GSLIM=********
CS:EIP=005b:1d1e16c6 CSACC=f0df CSLIM=ffffffff
SS:ESP=0053:0002fff4 SSACC=f0f3 SSLIM=ffffffff
EBP=0003001c FLG=00212202

NSPR4.DLL 0001:000216c6

I know the exceptq logging is working, because I can still trigger a
DOSCALL1 crash by doing a restart for addons.

[Dave Yeo]

On 06/08/12 04:58 pm, Steve Wendt wrote:
> For what it's worth, I tried enabling Flashgot again. RMB crash
> produced an entry in popuplog.os2 (no exceptq log):

I'd be surprised if it didn't crash though it is still strange how my
install stopped crashing, making it very hard to debug

>
> 06-08-2012 16:53:10 SYS3171 PID 0305 TID 0001 Slot 0092
> D:\OS2APPS\SEAMONKEY\SEAMONKEY.EXE

[...]

>
> I know the exceptq logging is working, because I can still trigger a
> DOSCALL1 crash by doing a restart for addons.

The problem is it recurses until it runs out of stack, which causes
exceptq to fail to log anything, see help 3171.
Dave

[Mark Dodel]

On Fri, 8 Jun 2012 14:35:09 UTC, Dave Yeo <dave....@gmail.com>
wrote:

-> Mark Dodel wrote:
-> > On Fri, 8 Jun 2012 10:12:33 UTC, "Harald Kamm"
-> > <harald.k...@bnv-bamberg.de> wrote:
-> >

-> > -> On Fri, 8 Jun 2012 06:20:39 UTC, Dave Yeo<dave....@gmail.com> wrote:
-> > ->
-> > -> Hi Dave,
-> > ->
-> > -> thanks so much! Do you have any hint to make Forecastfox work again? I always get the

-> > -> error message "Connection error".

-> > ->
-> > -> Thanks again, Harald

-> >
-> > I see the same thing and have for several releases of FF10. I'll have
-> > to try previous releases to see where it started. I searched
-> > Forecastfox support for that error and didn't find anything useful. I
-> > also reset the settings for the addon but same thing. I get something
-> > similar for Facebook Chat " Unable to connect to chat. Check your
-> > internet connection." No idea if it is related.
->
-> I think there is a subtle bug somewhere where Firefox is reporting to
-> add-ons that it is off-line even though it is online. Where I have no
-> idea. It might be possible to hack the addition to ignore the off-line
-> status, somebody did that with a different add-on.

I tried 9.0.1 and 10.0 thru 10.0.4 and Forecast fox worked in all, but
doesn't in 10.0.5. also Facebook chat works in 9.0.1 but not in any
of the 10 releases so it may not be related.

Mark

[Dave Yeo]

It never worked here in 10.04 and there were very minimal changes
between 10.0.4 and 10.0.5. It also doesn't work in early 11a (later ones
crash with any add-on enabled, I've been building over and over trying
to find where it broke :( )
I'll try to find time to test earlier 10's but right now I'm in fixing
11 mode with hopes of going forward.
Dave

[Dave Saville]

On Sun, 10 Jun 2012 00:56:04 UTC, "Mark Dodel" <madode...@ptd.net>
wrote:

Yes - me - Flagfox always thinks it is offline. It's the
"window.navigator.onLine" function that has a flakey idea of when it
is online or not. My wife is still using FF8 and it is/was OK in that.

--
Regards
Dave Saville

[madodel]

I'm pretty sure it didn't work in at least 10.0.4 and probably the ones
before that here as well. But now trying them it works. Really weird.
Excellent to hear that work is continuing on 11. Your work is greatly
appreciated.

Mark

--
Posted from my iPad

[David Arturo Macias Corona]

Dave Yeo wrote:
> Firefox 10.05esr has been released. I've also rebuilt SeaMonkey 2.7.2
> with 10.05. Available at netlabs, users of 10.04 are encouraged to
> upgrade for the latest security fixes.

Some people here know about my problems with SM 2.x series and FAT32 profile
I applied some suggestions, for example remove /EA and CACHEF32, which
fix some problems but not main problems with SM/FAT32

Now I found "another line for tiger"

Days ago I started to use "seamonkey-2.7.2.en-US.os2.10.5esr" in
completely new directory:

28/02/12 12:19a <DIR> 354 ---- seamonkey272
16/05/12 3:15a <DIR> 354 ---- seamonkey272esr
11/06/12 3:41p <DIR> 0 ---- seamonkey272esr105

but now, in every SM272esr105 startup, appear the well-know screen
containing:

---------------------------------
Would you like to restore your session?

Your previous SeaMonkey session closed unexpectedly. We sincerely
apologize for the inconvenience. You can restore the tabs and windows
from your previous session, or start a new session if they are no longer
needed.
---------------------------------

I was checking many times and it happen even if CHKDSK ( in ecs or real
Windows ) does not show any problem

For example, below is a result of CHKDSK with no problem, and after that
starting SM, it show same problem

Any hints or checks ?

My current dll files are:

[E:\ecs\dll]dir libc* /od

The volume label in drive E is ECS20.
The Volume Serial Number is 6A12:2015.
Directory of E:\ecs\dll

14/04/04 4:37p 356,330 0 a--- libc05.dll
5/09/06 8:51a 929,002 0 a--- libc062x.dll
11/08/08 11:53a 1,353,252 0 a--- libc064x.dll
23/03/12 4:32a 1,353,208 0 a--- libc065.dll
23/03/12 4:32a 48,142 0 a--- libc06.dll
23/03/12 4:32a 48,142 0 a--- libc061.dll
23/03/12 4:32a 157,124 0 a--- libc062.dll
23/03/12 4:32a 157,124 0 a--- libc063.dll
23/03/12 4:32a 157,176 0 a--- libc064.dll
9 file(s) 4,559,500 bytes used
435,236,864 bytes free

David Macias


The type of file system for the disk is FAT32.
The FAT32 file system program has been started.
(UFAT32.DLL version 0.9.12 compiled on Apr 15 2008)
The volume label is WINXPP.
The Volume Serial Number is 496F-DD6D.
CHKDSK is checking fats :Ok.
CHKDSK is checking files and directories...
CHKDSK is searching for lost data.
CHKDSK has searched 100% of the disk.

83840417792 bytes total disk space.
5062656 bytes in bad sectors.
2254700544 bytes in 4012 hidden files.
526565376 bytes in 31846 directories.
0 bytes in extended attributes.
70793330688 bytes in 357663 user files.
10260758528 bytes available on disk.

16384 bytes in each allocation unit.
5117213 total allocation units.
626267 available allocation units on disk.

0% of the files and directories are fragmented.

[Alfredo Fernández Díaz]

David Arturo Macias Corona wrote:
...

> Some people here know about my problems with SM 2.x series and FAT32 profile
> I applied some suggestions, for example remove /EA and CACHEF32, which fix
> some problems but not main problems with SM/FAT32
>
> Now I found "another line for tiger"

...

> but now, in every SM272esr105 startup, appear the well-know screen containing:
>
> ---------------------------------
> Would you like to restore your session?

...

> I was checking many times and it happen even if CHKDSK ( in ecs or real
> Windows ) does not show any problem

So, SM fails to write its stuff to disk properly (because it says so) but the
filesystem is verifiably NOT corrupted? Sounds like a timeout issue to me,
which would point again to the file ssytem cache, but this is just a wild guess.

[Dave Yeo]

David Arturo Macias Corona wrote:

[...]

> Some people here know about my problems with SM 2.x series and FAT32
> profile
> I applied some suggestions, for example remove /EA and CACHEF32, which
> fix some problems but not main problems with SM/FAT32
>
> Now I found "another line for tiger"
>
> Days ago I started to use "seamonkey-2.7.2.en-US.os2.10.5esr" in
> completely new directory:
>
> 28/02/12 12:19a <DIR> 354 ---- seamonkey272
> 16/05/12 3:15a <DIR> 354 ---- seamonkey272esr
> 11/06/12 3:41p <DIR> 0 ---- seamonkey272esr105
>
> but now, in every SM272esr105 startup, appear the well-know screen
> containing:
>
> ---------------------------------
> Would you like to restore your session?
>
> Your previous SeaMonkey session closed unexpectedly. We sincerely
> apologize for the inconvenience. You can restore the tabs and windows
> from your previous session, or start a new session if they are no longer
> needed.
> ---------------------------------
>
> I was checking many times and it happen even if CHKDSK ( in ecs or real
> Windows ) does not show any problem
>
> For example, below is a result of CHKDSK with no problem, and after that
> starting SM, it show same problem
>
> Any hints or checks ?
>

[...]

>
> The type of file system for the disk is FAT32.
> The FAT32 file system program has been started.
> (UFAT32.DLL version 0.9.12 compiled on Apr 15 2008)
> The volume label is WINXPP.
> The Volume Serial Number is 496F-DD6D.
> CHKDSK is checking fats :Ok.
> CHKDSK is checking files and directories...
> CHKDSK is searching for lost data.
> CHKDSK has searched 100% of the disk.
>
> 83840417792 bytes total disk space.
> 5062656 bytes in bad sectors.

Your hard drive seems to have problems. You shouldn't have any bad
sectors as the hard drive controller should take care of remapping bad
blocks. Have you done a SMART query? Danis506 comes with a fairly
extensive SMART utility and there is smartmon on Hobbes. You might have
to enable SMART in your BIOS, I know I had to.
[...]
Dave

[David Arturo Macias Corona]

Dave, thanks

Dave Yeo wrote:
> Your hard drive seems to have problems. You shouldn't have any bad
> sectors as the hard drive controller should take care of remapping bad
> blocks. Have you done a SMART query? Danis506 comes with a fairly
> extensive SMART utility and there is smartmon on Hobbes. You might have
> to enable SMART in your BIOS, I know I had to.
> [...]

I always have SMART enabled in BIOS

In danis506r187\smart I found Smartctl.exe

I used
smartctl -a hd0
smartctl -t long hd0

Below is output of "smartctl -a hd0" used some days ago, but I do not
know what values mean

Can you check it and tell me if there are something to care ?
Is a SATA II HDD with IDE mode enabled in BIOS, as ecs20 required

If I need another HDD, I am ready :-)

My CONFIG.sys value since eCS 2.0 installation is:
BASEDEV=DANIS506.ADD /!BIOS


And about problem:
=====================================
...but now, in every SM272esr105 startup, appear the well-know screen
containing:

Would you like to restore your session?

=====================================

after last SM272esr105 problem with FAT32 profile which "cut" prefs.js I
found a "fat" sessionstore.json of about 40 Mb, while common are 10 Mb
filesize

Restoring sessionstore.json problem with "restore your session" has gone
As I see, there was not problem with sessionstore.json in filesystem
detected by CHKDSK, but problem in internal sessionstore.json structures

David Macias


smartctl version 5.37 [i386-pc-ibmvac365] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.10 family
Device Model: ST3250310AS
Serial Number: 6RYEC31K
Firmware Version: 3.AHC
User Capacity: 250,059,350,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Fri Jun 15 07:03:35 2012
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 121) The previous self-test completed
having
the read element of the test failed.
Total time to complete Offline
data collection: ( 433) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 56) minutes.
SCT capabilities: (0x0035) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 100 253 006 Pre-fail
Always - 0
3 Spin_Up_Time 0x0002 098 097 000 Old_age
Always - 0
4 Start_Stop_Count 0x0032 097 097 020 Old_age
Always - 3134
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail
Always - 0
7 Seek_Error_Rate 0x000f 084 060 030 Pre-fail
Always - 256434034
9 Power_On_Hours 0x0032 089 089 000 Old_age
Always - 10264
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail
Always - 0
12 Power_Cycle_Count 0x0033 096 096 020 Pre-fail
Always - 4424
184 Unknown_Attribute 0x0033 100 253 097 Pre-fail Always
- 0
187 Reported_Uncorrect 0x003a 001 001 000 Old_age Always
- 217
189 High_Fly_Writes 0x0022 100 100 045 Old_age Always
- 0
190 Airflow_Temperature_Cel 0x0022 052 046 000 Old_age Always
- 48 (Lifetime Min/Max 18/54)
194 Temperature_Celsius 0x001a 048 054 000 Old_age Always
- 48 (0 18 0 0)
195 Hardware_ECC_Recovered 0x0012 073 066 000 Old_age Always
- 81791812
197 Current_Pending_Sector 0x0010 099 099 000 Old_age
Offline - 31
198 Offline_Uncorrectable 0x003e 100 100 000 Old_age Always
- 0
199 UDMA_CRC_Error_Count 0x0000 200 200 000 Old_age
Offline - 0

SMART Error Log Version: 1
ATA Error Count: 218 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 218 occurred at disk power-on lifetime: 86 hours (3 days + 14 hours)
When the command that caused the error occurred, the device was
active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 b9 94 4e e0 Error: UNC at LBA = 0x004e94b9 = 5149881

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 80 55 94 4e e0 00 00:18:18.744 READ DMA EXT
25 00 01 df 51 b9 e0 00 00:18:22.922 READ DMA EXT
25 00 80 d5 48 49 e0 00 00:18:22.906 READ DMA EXT
25 00 01 65 05 81 e0 00 00:18:22.893 READ DMA EXT
35 00 01 6a 62 53 e0 00 00:18:22.889 WRITE DMA EXT

Error 217 occurred at disk power-on lifetime: 86 hours (3 days + 14 hours)
When the command that caused the error occurred, the device was
active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 9f 48 49 e0 Error: UNC at LBA = 0x0049489f = 4802719

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 80 55 48 49 e0 00 00:18:18.744 READ DMA EXT
25 00 01 71 6c 10 e0 00 00:18:18.734 READ DMA EXT
25 00 80 d5 10 41 e0 00 00:18:18.734 READ DMA EXT
25 00 01 36 a2 16 e0 00 00:18:18.710 READ DMA EXT
35 00 01 6a 62 53 e0 00 00:18:14.296 WRITE DMA EXT

Error 216 occurred at disk power-on lifetime: 86 hours (3 days + 14 hours)
When the command that caused the error occurred, the device was
active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 6b 10 41 e0 Error: UNC at LBA = 0x0041106b = 4264043

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 80 55 10 41 e0 00 00:18:10.165 READ DMA EXT
25 00 01 00 00 00 e0 00 00:18:10.165 READ DMA EXT
35 00 01 6a 62 53 e0 00 00:18:10.165 WRITE DMA EXT
35 00 01 3f c6 52 e0 00 00:18:10.153 WRITE DMA EXT
25 00 01 00 00 00 e0 00 00:18:14.296 READ DMA EXT

Error 215 occurred at disk power-on lifetime: 86 hours (3 days + 14 hours)
When the command that caused the error occurred, the device was
active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 e2 14 3d e0 Error: UNC at LBA = 0x003d14e2 = 4003042

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 80 d5 14 3d e0 00 00:18:10.165 READ DMA EXT
25 00 80 55 14 3d e0 00 00:18:10.165 READ DMA EXT
25 00 80 d5 48 51 e0 00 00:18:10.165 READ DMA EXT
25 00 01 d3 ea 29 e0 00 00:18:10.153 READ DMA EXT
25 00 80 55 48 51 e0 00 00:18:10.153 READ DMA EXT

Error 214 occurred at disk power-on lifetime: 86 hours (3 days + 14 hours)
When the command that caused the error occurred, the device was
active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 47 48 51 e0 Error: UNC at LBA = 0x00514847 = 5326919

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 80 d5 47 51 e0 00 00:18:06.063 READ DMA EXT
25 00 01 a6 e3 61 e0 00 00:18:06.052 READ DMA EXT
25 00 80 55 47 51 e0 00 00:18:06.052 READ DMA EXT
25 00 01 ac 36 0a e0 00 00:18:06.028 READ DMA EXT
25 00 80 d5 a6 4e e0 00 00:18:01.906 READ DMA EXT

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

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

[Dave Yeo]

On 06/19/12 03:57 am, David Arturo Macias Corona wrote:
> Dave, thanks
>
> Dave Yeo wrote:
>> Your hard drive seems to have problems. You shouldn't have any bad
>> sectors as the hard drive controller should take care of remapping bad
>> blocks. Have you done a SMART query? Danis506 comes with a fairly
>> extensive SMART utility and there is smartmon on Hobbes. You might have
>> to enable SMART in your BIOS, I know I had to.
>> [...]
>
> I always have SMART enabled in BIOS
>
> In danis506r187\smart I found Smartctl.exe
>
> I used
> smartctl -a hd0
> smartctl -t long hd0
>
> Below is output of "smartctl -a hd0" used some days ago, but I do not
> know what values mean
>
> Can you check it and tell me if there are something to care ?
> Is a SATA II HDD with IDE mode enabled in BIOS, as ecs20 required

I'm far from expert at reading this so you should get a second opinion.

>
> If I need another HDD, I am ready :-)
>

[...]

> Vendor Specific SMART Attributes with Thresholds:
> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
> WHEN_FAILED RAW_VALUE
> 1 Raw_Read_Error_Rate 0x000f 100 253 006 Pre-fail

This looks bad.

> Always - 0
> 3 Spin_Up_Time 0x0002 098 097 000 Old_age
> Always - 0
> 4 Start_Stop_Count 0x0032 097 097 020 Old_age
> Always - 3134
> 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail

This also looks bad, too bad I can't see listed how many sectors have
been remapped.

> Always - 0
> 7 Seek_Error_Rate 0x000f 084 060 030 Pre-fail

This also looks bad.

> Always - 256434034
> 9 Power_On_Hours 0x0032 089 089 000 Old_age
> Always - 10264
> 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail
> Always - 0
> 12 Power_Cycle_Count 0x0033 096 096 020 Pre-fail
> Always - 4424
> 184 Unknown_Attribute 0x0033 100 253 097 Pre-fail Always
> - 0
> 187 Reported_Uncorrect 0x003a 001 001 000 Old_age Always
> - 217
> 189 High_Fly_Writes 0x0022 100 100 045 Old_age Always
> - 0
> 190 Airflow_Temperature_Cel 0x0022 052 046 000 Old_age Always
> - 48 (Lifetime Min/Max 18/54)
> 194 Temperature_Celsius 0x001a 048 054 000 Old_age Always
> - 48 (0 18 0 0)
> 195 Hardware_ECC_Recovered 0x0012 073 066 000 Old_age Always
> - 81791812

This and the next also look bad.

> 197 Current_Pending_Sector 0x0010 099 099 000 Old_age
> Offline - 31
> 198 Offline_Uncorrectable 0x003e 100 100 000 Old_age Always
> - 0

I think this means that all your spare sectors are used.

> 199 UDMA_CRC_Error_Count 0x0000 200 200 000 Old_age
> Offline - 0
>
> SMART Error Log Version: 1

The rest I don't even pretend to be able to judge :)
One other idea you might want to try is underclocking your drive to see
if that helps, I had to underclock my DVD drive to install eCS. I did it
in the BIOS but I think you can also do it with arguments to
danis506.add. IIRC I changed the DMA to a lower number perhaps 5 to 3
but I'm not sure and don't want to reboot to get into the BIOS right now.
Dave

[Trevor Hemsley]

On Tue, 19 Jun 2012 10:57:41 UTC in mozilla.dev.ports.os2, David Arturo Macias
Corona <dma...@mail.udg.mx> wrote:

> === START OF INFORMATION SECTION ===
> Model Family: Seagate Barracuda 7200.10 family
> Device Model: ST3250310AS
> Serial Number: 6RYEC31K
> Firmware Version: 3.AHC
> User Capacity: 250,059,350,016 bytes
> Device is: In smartctl database [for details use: -P show]
> ATA Version is: 7
> ATA Standard is: Exact ATA specification draft version not indicated
> Local Time is: Fri Jun 15 07:03:35 2012
> SMART support is: Available - device has SMART capability.
> SMART support is: Enabled
>
> === START OF READ SMART DATA SECTION ===
> SMART overall-health self-assessment test result: PASSED

So far so good. However, this is a Seagate drive and the smart attributes often
reports some very funny numbers like yours below. The only ones I'm a bit
concerned about are the temperate ones - 48C seems a touch too high for normal
operation to me, not dangerous but higher than is comfortable. Oh, and the
Current_Pending_Sector at 31 is not good at all - that's where it's found 31
sectors that it cannot read and they will be reassigned new ones from the spare
list when they are next written. I'm not sure I'd take too much notice of the
huge numbers on Seek_error_rate and Hardware_ECC_Recovered as they look like the
sort of invalid numbers that are common on Seagate drives. I've reflowed your
output below so that each line is complete - the the numbers on the right hand
end that you need to look at not the ones in the middle of each line.

> SMART Attributes Data Structure revision number: 10
> Vendor Specific SMART Attributes with Thresholds:
> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
> 1 Raw_Read_Error_Rate 0x000f 100 253 006 Pre-fail Always - 0
> 3 Spin_Up_Time 0x0002 098 097 000 Old_age Always - 0
> 4 Start_Stop_Count 0x0032 097 097 020 Old_age Always - 3134
> 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
> 7 Seek_Error_Rate 0x000f 084 060 030 Pre-fail Always - 256434034
> 9 Power_On_Hours 0x0032 089 089 000 Old_age Always - 10264
> 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
> 12 Power_Cycle_Count 0x0033 096 096 020 Pre-fail Always - 4424
> 184 Unknown_Attribute 0x0033 100 253 097 Pre-fail Always - 0
> 187 Reported_Uncorrect 0x003a 001 001 000 Old_age Always - 217
> 189 High_Fly_Writes 0x0022 100 100 045 Old_age Always - 0
> 190 Airflow_Temperature_Cel 0x0022 052 046 000 Old_age Always - 48 (Lifetime Min/Max 18/54)
> 194 Temperature_Celsius 0x001a 048 054 000 Old_age Always - 48 (0 18 0 0)
> 195 Hardware_ECC_Recovered 0x0012 073 066 000 Old_age Always - 81791812
> 197 Current_Pending_Sector 0x0010 099 099 000 Old_age Offline - 31
> 198 Offline_Uncorrectable 0x003e 100 100 000 Old_age Always - 0
> 199 UDMA_CRC_Error_Count 0x0000 200 200 000 Old_age Offline - 0

The errors listed below don't look good but they happened a long time ago - the
smart data says it's been powered up now for 10264 hours and the errors are all
from 86 hours so it's gone more than 10,000 hours without an error.

> Error 218 occurred at disk power-on lifetime: 86 hours (3 days + 14 hours)

> Error 217 occurred at disk power-on lifetime: 86 hours (3 days + 14 hours)

> Error 216 occurred at disk power-on lifetime: 86 hours (3 days + 14 hours)

> Error 215 occurred at disk power-on lifetime: 86 hours (3 days + 14 hours)

> Error 214 occurred at disk power-on lifetime: 86 hours (3 days + 14 hours)

> 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.

The only way to get rid of the pending sectors is to force them to be rewritten.
That can be done by writing to the entire drive and destroying its current
contents or the Linux badblocks command can be told to perform a non-destructive
write test on the drive - it reads a sector then writes it back to the same
place. That will force those pending sectors to be reallocated from the spare
list. You could probably boot from a Linux Live CD and run it from there if you
don't have Linux installed already - but I would back up anything critical
before you do so, sometimes already-failing disks can be pushed over the edge by
too much activity so you might lose the lot.

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

[Bob]

Is Thunderbird 10.05 up yet. I had a look in
ftp.netlabs.org/incoming/mozilla and couldn't spot it.

Bob McLellan

[Dave Yeo]

Bob wrote:
> Is Thunderbird 10.05 up yet. I had a look in
> ftp.netlabs.org/incoming/mozilla and couldn't spot it.

Should be there now.
Dave

[David Arturo Macias Corona]

[Dave]

>One other idea you might want to try is underclocking your drive to
>see if that helps, I had to underclock my DVD drive to install eCS.
>I did it in the BIOS but I think you can also do it with arguments
>to danis506.add. IIRC I changed the DMA to a lower number perhaps 5
>to 3 but I'm not sure and don't want to reboot to get into the BIOS
>right now.

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.
>

Dave, Trevor:

Thanks for your detailed explanations, I learn too much

Many facts point to problems in HDD, so I am looking for a new one.
I want a Sata III, 1.5 Tb size

But usual questions arise:

- Should I replace only HDD or should I replace most hardware ?
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
- Wait for ecs22 ?
- ...

I made many other tests, and results are same: it look bad

For example, DFSee report 35 "bad spots"
They may convert and act as "massive black holes eating galaxies" suddenly

--------------------------------
DFSee OS/2 11.1 : executing: scan -E:i
Command timestamp : Thursday 2012-06-28 00:34:20
SectorScan method : Fast Read-only At: 0x00000000, buffer 63 sect =
31.5 KiB
[...]

Elapsed time : 56:26 (h:m:sec) Throughput = 70.43 MiB/sec
35 Bad sectors found! You can use the 'list -w' command to show,
or the 'export' command to save the list to a file.
The list shows EACH individual bad sector found!
Be aware that verbose listing (list -d) will re-read all the
bad sectors, which will be very time consuming!

ReadWrite Store A : PhysDisk : 1 PartId 00 = -- mode=FDISK
280612-013046
RC:35 = 0x23 : 00000000 u=00000000 x=00000000 this=00000000
Base=00000000
--------------------------------

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"

This JFS partition just have a few weeks, with very low use ( just few
tests ) and now are bad

As result, entire HDD seem plenty of "holes" and not just in FAT32 partition

I want a new HDD
but I want an entire new computer instead
Will ecs21 support it ? :-)

I have to think these changes deeply

David Macias


CHKDSK Block size in bytes: 4096
CHKDSK File system size in blocks: 2558343
CHKDSK *Phase 1 - Check Blocks, Files/Directories, and Directory Entries
CHKDSK *Phase 2 - Count Links
CHKDSK *Phase 3 - Rescan for Duplicate Blocks and Verify Directory Tree
CHKDSK *Phase 4 - Report Problems
CHKDSK *Phase 7 - Verify File/Directory Allocation Maps
CHKDSK *Phase 8 - Verify Disk Allocation Maps
CHKDSK Incorrect data detected in disk allocation structures.
CHKDSK Incorrect data detected in disk allocation control structures.
10233372 kilobytes total disk space.
9422 kilobytes are in 5821 directories.
4646414 kilobytes are in 42485 user files.
7824 kilobytes are in extended attributes.
54956 kilobytes are reserved for system use.
5533600 kilobytes are available for use.
JFS0138: CHKDSK Checking a mounted file system does not produce dependable
results.

CHKDSK File system is dirty.
CHKDSK File system is dirty but is marked clean. In its present state, the
results of accessing j: (except by this utility) are undefined.
.....@...

[Trevor Hemsley]

On Thu, 28 Jun 2012 10:02:24 UTC in mozilla.dev.ports.os2, David Arturo Macias
Corona <dma...@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.

[Peter Brown]

Hi

Probably the best way to use chkdsk is during boot. Force the full
chkdsk against all jfs formatted drives by using the line below:-

IFS=L:\OS2\JFS.IFS /LW:5,20,4 /AUTOCHECK:+*


Regards

Pete

[Andreas Buchinger]

Dave Yeo schrieb:

I've updated to SeaMonkey 2.7.2. Seems to work well. A big THANK YOU.

One note - lightning does not work correct anymore. I'm not able to create a new task. Think I've
installed latest lightning for eCS 1.0b8pre. Can you build lightning 1.2.3 too?

Regards, Andi

[Steve Wendt]

On 11/5/2012 11:34 AM, Andreas Buchinger wrote:

> Can you build lightning 1.2.3 too?

http://releases.mozilla.org/pub/mozilla.org/calendar/lightning/releases/1.2.3/contrib/os2/