Post by: StWtal on February 01, 2020, 05:51:59 pm
Recently I bought a SL-C3100 from Japan on eBay.
According to the description the internal 4GB drive is faulty and the device is not booting up.
After inserting a new battery and a reset it's back to life now.
It also came witch an additional 4GB Microdrive.
To be sure the internal drive is faulty, I entered "D+M" setup and started "HDD Check".
Does anybody know, what the "BANK_X" values mean?
Maybe it is the reliability of the sectors?
BTW: Test of the HDD resulted "OK!"
Rgds,
Stefan
Post by: DiTBho on January 30, 2021, 11:13:59 am
I used the utility badblocks
Code: [Select]
# badblocks -swv /dev/sda
Unfortunately it's seriously damaged, so I ordered a new micro-drive.
Tested it again, it resulted perfectly working.
Post by: DiTBho on January 31, 2021, 12:42:07 pm
Code: [Select]
# badblocks -swv /dev/sda
Checking for bad blocks in read-write mode
From block 0 to 3999743
Testing with pattern 0xaa: done, Reading and comparing: done
Testing with pattern 0x55: done, Reading and comparing: done
Testing with pattern 0xff: done, Reading and comparing: done
Testing with pattern 0x00: done, Reading and comparing: done
Pass completed, 0 bad blocks found.
3999744 blocks ~ 4GB. It took 4 hours to check.
Post by: DiTBho on January 31, 2021, 12:45:22 pm
This is the equipment I am using. I bought it on Amazon for 15 euro.
The showed microdrive is the damaged one
Post by: DiTBho on February 14, 2021, 05:05:59 pm
Code: [Select]
# make
- generating interface public for disktest ... done
- generating interface public for host_io ... done
- generating interface private for disktest ... done
- generating interface private for host_io ... done
- compiling disktest ... done
- compiling host_io ... done
- linking to disktest
# obj/disktest /dev/hdc
opening /dev/hdc ... done
Checking for bad blocks in read-write mode
From 0 to 1.610.735.615, by 8.192 bytes at time
[ 0 ] BBBBBBBBB..BBBBB.BBBBBBBBBBBB........BBBBBBBBBBBBBBBBBBBBBBBBBBB
[ 16.6 ] BBBBBBBBBBBBBBBBBBBBBBB.BBBBBBBBBBBBBBBBBB.BBBBBBBBBBBB....BBBBB
[ 33.3 ] BBBBBBBBBBB...............BBBBBBBBBBB.BBBBBBBBBBBBB.BBBBBBBBBBBB
[ 49.9 ] BB...BBBBBBBBBBBBBBB.BBBBBBBBBBBBBBB......BBBBBBBBBBBBBBBBBBBBBB
[ 66.6 ] BBBBBBBBBBBBBBBBB....BBBBBBBBBB.BBBBBBBBBBBBBBB....BBBBBBBBB.BBB
[ 83.3 ] BBBBBBBBBBBBBBBBBB.BBB.BBBBBB.BBBBB..BB..BB.BBBBB.BBB...........
[ 99.9 ] .
"." means no problem
"B" means error during I/O
The above disk is a voluntary damaged one used to test the disk-testing program. This application works good with electro-mechanical HDDs but doesn't work with SSDs and flash-devices.
Since it only does 1 pass, it's ~3x times faster than the program"badblocks".
Post by: Varti on February 15, 2021, 08:22:10 am
I wrote my own disk testing program ;DNice, a faster alternative to badblocks, well done :) I have myself 3 Zauruses with a Microdrive, I'd like to give it a go someday. I guess it's portable, but it will need to be compiled for each OS separately (Sharp/Cacko, pdaXrom, void...), is this correct?Code: [Select]
# make
- generating interface public for disktest ... done
- generating interface public for host_io ... done
- generating interface private for disktest ... done
- generating interface private for host_io ... done
- compiling disktest ... done
- compiling host_io ... done
- linking to disktest
# obj/disktest /dev/hdc
opening /dev/hdc ... done
Checking for bad blocks in read-write mode
From 0 to 1.610.735.615, by 8.192 bytes at time
[ 0 ] BBBBBBBBB..BBBBB.BBBBBBBBBBBB........BBBBBBBBBBBBBBBBBBBBBBBBBBB
[ 16.6 ] BBBBBBBBBBBBBBBBBBBBBBB.BBBBBBBBBBBBBBBBBB.BBBBBBBBBBBB....BBBBB
[ 33.3 ] BBBBBBBBBBB...............BBBBBBBBBBB.BBBBBBBBBBBBB.BBBBBBBBBBBB
[ 49.9 ] BB...BBBBBBBBBBBBBBB.BBBBBBBBBBBBBBB......BBBBBBBBBBBBBBBBBBBBBB
[ 66.6 ] BBBBBBBBBBBBBBBBB....BBBBBBBBBB.BBBBBBBBBBBBBBB....BBBBBBBBB.BBB
[ 83.3 ] BBBBBBBBBBBBBBBBBB.BBB.BBBBBB.BBBBB..BB..BB.BBBBB.BBB...........
[ 99.9 ] .
"." means no problem
"B" means error during I/O
The above disk is a voluntary damaged one used to test the disk-testing program. This application works good with electro-mechanical HDDs but doesn't work with SSDs and flash-devices.
Since it only does 1 pass, it's ~3x times faster than the program"badblocks".
Varti
Post by: DiTBho on February 15, 2021, 11:59:26 am
it will need to be compiled for each OS separately (Sharp/Cacko, pdaXrom, void...), is this correct?
dunno. if you can compile badblocks, then you can compile it; it uses direct IO functions provided by glibc, I haven't tested uclibc and musl.
Post by: ArchiMark on February 16, 2021, 09:45:49 am
Much better and larger storage capacity.
Mark