#310389 - 21/05/2008 13:58
Re: more RAM+Harddisk errors
[Re: peter]
|
carpal tunnel
Registered: 18/01/2000
Posts: 5683
Loc: London, UK
|
On the other hand, some people do use v3alpha11 every day without issues. I use v3a11 regularly (but not every day -- my car rarely moves from its spot outside the house, and I'm not using my mlord dock at the moment), and it reboots occasionally. I can live with it. For what it's worth, I don't use the tuner (I have one, but I only use it as a Ford Focus stalk adapter), and I listen to MP3 files only. I also don't bother with the visuals.
_________________________
-- roger
|
Top
|
|
|
|
#310390 - 21/05/2008 15:31
Re: more RAM+Harddisk errors
[Re: peter]
|
carpal tunnel
Registered: 20/12/1999
Posts: 31596
Loc: Seattle, WA
|
should i go for v2.01-final or v3.00-alpha11? That's a good question, which doesn't actually seem to be in the FAQ, at least not in that pithy a form. I've updated the relevant FAQ entry a bit.
|
Top
|
|
|
|
#310392 - 21/05/2008 17:37
Re: more RAM+Harddisk errors
[Re: tfabris]
|
addict
Registered: 22/11/2007
Posts: 475
Loc: Denmark, Odense
|
i have found one error... but the check is not complete
but is there a way to exclude the bad sectors from beeing used?
_________________________
the "monkey" who learned to check a harddrive
|
Top
|
|
|
|
#310394 - 21/05/2008 18:20
Re: more RAM+Harddisk errors
[Re: Boelle]
|
carpal tunnel
Registered: 20/12/1999
Posts: 31596
Loc: Seattle, WA
|
I think that with modern IDE drives, the act of exercising that sector will automatically mark it as bad, you don't need to do anything. Mark, correct me if I'm wrong?
|
Top
|
|
|
|
#310396 - 22/05/2008 00:19
Re: more RAM+Harddisk errors
[Re: Boelle]
|
carpal tunnel
Registered: 29/08/2000
Posts: 14491
Loc: Canada
|
i have found one error... but the check is not complete Huh? If it hits any error, it will bail out completely. So what makes you think it "found one error" ? Log, please.
|
Top
|
|
|
|
#310397 - 22/05/2008 05:09
Re: more RAM+Harddisk errors
[Re: tfabris]
|
carpal tunnel
Registered: 18/01/2000
Posts: 5683
Loc: London, UK
|
I think that with modern IDE drives, the act of exercising that sector will automatically mark it as bad, you don't need to do anything. Mark, correct me if I'm wrong? I believe that you have to write to that sector to cause it to be re-mapped.
_________________________
-- roger
|
Top
|
|
|
|
#310398 - 22/05/2008 06:56
Re: more RAM+Harddisk errors
[Re: Roger]
|
addict
Registered: 22/11/2007
Posts: 475
Loc: Denmark, Odense
|
it has not returned to the command line yet.. but it was telling something about input/output error
_________________________
the "monkey" who learned to check a harddrive
|
Top
|
|
|
|
#310399 - 22/05/2008 07:06
Re: more RAM+Harddisk errors
[Re: Boelle]
|
addict
Registered: 22/11/2007
Posts: 475
Loc: Denmark, Odense
|
empeg:/empeg/bin# cat /dev/hd* > /dev/null hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } hdb: read_intr: error=0x40 { UncorrectableError }, LBAsect=96695, sector=96695 end_request: I/O error, dev 03:40 (hdb), sector 96695 hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } hdb: read_intr: error=0x40 { UncorrectableError }, LBAsect=100349, sector=100349 end_request: I/O error, dev 03:40 (hdb), sector 100349 hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } hdb: read_intr: error=0x40 { UncorrectableError }, LBAsect=115173, sector=115173 end_request: I/O error, dev 03:40 (hdb), sector 115173 cat: /dev/hdc: Input/output error hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } hdb: read_intr: error=0x40 { UncorrectableError }, LBAsect=65264558, sector=65055713 end_request: I/O error, dev 03:44 (hdb), sector 65055713 cat: /dev/hdc4: Input/output error empeg:/empeg/bin#
_________________________
the "monkey" who learned to check a harddrive
|
Top
|
|
|
|
#310402 - 22/05/2008 08:54
Re: more RAM+Harddisk errors
[Re: Boelle]
|
addict
Registered: 22/11/2007
Posts: 475
Loc: Denmark, Odense
|
i thought it could not hurt to format (build) the drives
i had to do it 2 times before it began the stress test, which i remeber means that the build went ok
during one of the builds ig got these errors on the secound drive:
Writing inode tables: done Writing superblocks and filesystem accounting information: done
real 4m0.304s user 0m2.120s sys 0m14.420s hdb: read_intr: status=0x59 hdb: read_intr: error=0x40 end_request: I/O error, dev 03:44 (hdb), sector 119816194 EXT2-fs error (device ide0(3,68)): read_block_bitmap: Cannot read block bitmap - block_group = 7313, block_bitmap = 59908097 EXT2-fs error (device ide0(3,68)): ext2_check_blocks_bitmap: Wrong free blocks count in super block, stored = 77942805, counted = 77934623
_________________________
the "monkey" who learned to check a harddrive
|
Top
|
|
|
|
#310403 - 22/05/2008 09:06
Re: more RAM+Harddisk errors
[Re: Boelle]
|
addict
Registered: 22/11/2007
Posts: 475
Loc: Denmark, Odense
|
btw... will both drives be stress tested?
_________________________
the "monkey" who learned to check a harddrive
|
Top
|
|
|
|
#310404 - 22/05/2008 10:17
Re: more RAM+Harddisk errors
[Re: Boelle]
|
addict
Registered: 22/11/2007
Posts: 475
Loc: Denmark, Odense
|
just did the build 3 times in a row with no problems, just waiting for cat /dev/hd* > /dev/null to tell if the errors are still there.. will take a very looooooong time :-)
_________________________
the "monkey" who learned to check a harddrive
|
Top
|
|
|
|
#310405 - 22/05/2008 10:20
Re: more RAM+Harddisk errors
[Re: Boelle]
|
carpal tunnel
Registered: 29/08/2000
Posts: 14491
Loc: Canada
|
empeg:/empeg/bin# cat /dev/hd* > /dev/null
Ahh.. that explains why you think it "keeps on going". Just for fun, try typing echo cat /dev/hd* and you'll see what command you really issued there. For future advice-givers, the correct syntax is: cat /dev/hd? > /dev/nullWhich will finish in half the time with no errors, or less in the presence of errors. But regardless, in this case there is something wrong. So now use this command to repair the drive: cat /dev/zero > /dev/hdcAnd then re-run the disk-builder stuff. Cheers
|
Top
|
|
|
|
#310406 - 22/05/2008 10:24
Re: more RAM+Harddisk errors
[Re: mlord]
|
addict
Registered: 22/11/2007
Posts: 475
Loc: Denmark, Odense
|
big thanks...
_________________________
the "monkey" who learned to check a harddrive
|
Top
|
|
|
|
#310407 - 22/05/2008 10:28
Re: more RAM+Harddisk errors
[Re: Boelle]
|
addict
Registered: 22/11/2007
Posts: 475
Loc: Denmark, Odense
|
btw.. you said that you could repair a broken handle?
do you ned a pic of it first ?
_________________________
the "monkey" who learned to check a harddrive
|
Top
|
|
|
|
#310408 - 22/05/2008 10:41
Re: more RAM+Harddisk errors
[Re: Boelle]
|
carpal tunnel
Registered: 29/08/2000
Posts: 14491
Loc: Canada
|
btw.. you said that you could repair a broken handle?
do you ned a pic of it first ? I can probably repair the broken handle, but won't know for sure until I try it. A picture (here) might be fun.
|
Top
|
|
|
|
#310412 - 22/05/2008 10:56
Re: more RAM+Harddisk errors
[Re: mlord]
|
addict
Registered: 22/11/2007
Posts: 475
Loc: Denmark, Odense
|
well one pic will be here later
another question, was there ever made a guide for the auto eq thing? i guees that i have to use the mic input on the sled, and some spec. files....
but by guide i mean for dummies.. sometinh like this:
1. do this 2. then do this ...
_________________________
the "monkey" who learned to check a harddrive
|
Top
|
|
|
|
#310420 - 22/05/2008 17:28
Re: more RAM+Harddisk errors
[Re: Shonky]
|
addict
Registered: 22/11/2007
Posts: 475
Loc: Denmark, Odense
|
good guide.... but where do i get the auto-eq files? and what order do i have to set them?
i may be blind but did not sse that
_________________________
the "monkey" who learned to check a harddrive
|
Top
|
|
|
|
#310421 - 22/05/2008 18:36
Auto Eq
[Re: Boelle]
|
carpal tunnel
Registered: 10/06/1999
Posts: 5916
Loc: Wivenhoe, Essex, UK
|
_________________________
Remind me to change my signature to something more interesting someday
|
Top
|
|
|
|
#310422 - 22/05/2008 20:41
Re: Auto Eq
[Re: andy]
|
addict
Registered: 22/11/2007
Posts: 475
Loc: Denmark, Odense
|
thanks for the files
how long should cat /dev/zero > /dev/hdc take for a 80 gb drive?
_________________________
the "monkey" who learned to check a harddrive
|
Top
|
|
|
|
#310424 - 22/05/2008 23:49
Re: Auto Eq
[Re: Boelle]
|
carpal tunnel
Registered: 29/08/2000
Posts: 14491
Loc: Canada
|
thanks for the files
how long should cat /dev/zero > /dev/hdc take for a 80 gb drive? Most likely on the order of 80 * 1000 * seconds, or from 10-22 hours. -ml
|
Top
|
|
|
|
#310487 - 26/05/2008 11:56
Re: more RAM+Harddisk errors
[Re: Boelle]
|
addict
Registered: 22/11/2007
Posts: 475
Loc: Denmark, Odense
|
after some 11-12 hours i got this:
empeg:/empeg/bin# cat /dev/hd? > /dev/null hdb: read_intr: status=0x59 hdb: read_intr: error=0x40 show_message("36e0.-1 hdb: err: read_intr") end_request: I/O error, dev 03:40 (hdb), sector 115464112 cat: /dev/hdc: Input/output error empeg:/empeg/bin#
_________________________
the "monkey" who learned to check a harddrive
|
Top
|
|
|
|
#310488 - 26/05/2008 11:56
Re: more RAM+Harddisk errors
[Re: Boelle]
|
addict
Registered: 22/11/2007
Posts: 475
Loc: Denmark, Odense
|
keep in mind that i did the repair as mark told me to do...
_________________________
the "monkey" who learned to check a harddrive
|
Top
|
|
|
|
#310491 - 26/05/2008 13:26
Re: more RAM+Harddisk errors
[Re: Boelle]
|
carpal tunnel
Registered: 29/08/2000
Posts: 14491
Loc: Canada
|
after some 11-12 hours i got this:
empeg:/empeg/bin# cat /dev/hd? > /dev/null hdb: read_intr: status=0x59 hdb: read_intr: error=0x40 show_message("36e0.-1 hdb: err: read_intr") end_request: I/O error, dev 03:40 (hdb), sector 115464112 cat: /dev/hdc: Input/output error empeg:/empeg/bin# Mmm.. " read_intr: status=0x59 error=0x40" really means " bad sector". That shouldn't happen here if you successfully did the cat /dev/zero > /dev/hdc command beforehand. So repeat both steps again. If it still fails, something else (connectors) may be bad. Or get the smartctl binary for the empeg and run it -- it will read out the error logs from the drive to tell us what *really* happened. Cheers
|
Top
|
|
|
|
#310502 - 26/05/2008 18:58
Re: more RAM+Harddisk errors
[Re: mlord]
|
addict
Registered: 22/11/2007
Posts: 475
Loc: Denmark, Odense
|
while i do another cat /dev/zero > /dev/hdc
i wondered.. the auto.eq thing.. is that only in ver 3?
_________________________
the "monkey" who learned to check a harddrive
|
Top
|
|
|
|
#310503 - 26/05/2008 19:00
Re: more RAM+Harddisk errors
[Re: Boelle]
|
carpal tunnel
Registered: 24/12/2001
Posts: 5528
|
|
Top
|
|
|
|
#310510 - 27/05/2008 08:45
Re: more RAM+Harddisk errors
[Re: tman]
|
addict
Registered: 22/11/2007
Posts: 475
Loc: Denmark, Odense
|
i guees that doing cat /dev/zero > /dev/hdc
it's normal to get no space left on drive error
_________________________
the "monkey" who learned to check a harddrive
|
Top
|
|
|
|
#310512 - 27/05/2008 12:28
Re: more RAM+Harddisk errors
[Re: Boelle]
|
pooh-bah
Registered: 12/01/2002
Posts: 2009
Loc: Brisbane, Australia
|
i guees that doing cat /dev/zero > /dev/hdc
it's normal to get no space left on drive error By doing this you will remove everything. You are zeroing every single sector on the drive. So all data will be gone. It will also erase any partitions set up previously.
_________________________
Christian #40104192 120Gb (no longer in my E36 M3, won't fit the E46 M3)
|
Top
|
|
|
|
#310513 - 27/05/2008 12:34
Re: more RAM+Harddisk errors
[Re: Shonky]
|
addict
Registered: 22/11/2007
Posts: 475
Loc: Denmark, Odense
|
i know...
is there a way to do it for both drives? some of the partions ar mounted read only
_________________________
the "monkey" who learned to check a harddrive
|
Top
|
|
|
|
#310514 - 27/05/2008 12:37
Re: more RAM+Harddisk errors
[Re: Boelle]
|
carpal tunnel
Registered: 18/01/2000
Posts: 5683
Loc: London, UK
|
i know...
is there a way to do it for both drives? some if the partions ar mounted read only To do it for both drives, just use /dev/hda and /dev/hdc for the second parameter. It doesn't care that the partitions are mounted read-only, because it writes over the entire drive, including the partition table. What it does is cause the disk to remap the bad sectors (the drive will only remap when writing). Running out of space is expected: /dev/zero is an infinite-length stream of zeroes, and your disk has finite space. (slightly drunk; being unnecessarily concise)
_________________________
-- roger
|
Top
|
|
|
|
|
|