Off-Topic > Off-Topic - Tiny Core Lounge
wi-fi
cast-fish:
Hello,
THis same problem manifest again here. very recently...
Again, this is after very prolonged usage....maybe over 15 hours and it does exactly the same
thing and locks into a hard drive read loop. Basically, the fault shows up about every 1 percent of usage time and persists for about an hour.
The Laptop, otherwise has performed perfect for a fortnight of heavy usage....and also the 13 prevoius years.
THis error, it hangs around.....maybe say a while, a couple of boots.....and it seems that after
the machine is left and temperatures cool....it works fine again.
I am certain it's an intermittent hardware fault now and somekind of chip creep error...after 13 years of heavy usage...electronic equipment can develop traits in it's performance.
The Hitachi hard drive (incompatability issues is a remote possibility). ALso this machine will perform slightly intermittently on Tinycore......graphics will lock and black screens....then maybe a day or so later.....the exact same approach with loading extensions will work fine....
it could be chip creep....over 13 years of excessive usage of this laptop. Leaves intermittent faults.
i am not happy at a machine that wont be rock solid on some OS....will further test Tinycore and
maybe try Slitaz.
It would not be so bad it it was fixable software fault.....but it's looking to me like a hardware issue which persists...
O___0
Vince.
cast-fish:
interesting.
Gparted tool won't do anything with this hard drive. It instantly reports an error.....say if you try to re-size the partition that is on there. NTFS win32 partition (only thing on the drive and fresh)
so why won't gparted do anything with this hard drive...?
the stripping military grade tool i used earlier DID report that this drive had an error and block zero
and interestingly gparted "hicups" almost the instant it starts trying to perform an operation like say re-sizing the partition
This is strange.
I think there could literally be some-kind of compatabliity error with certain hard drives and this
motherboard....and it could have been a compaq laptop re-call way back in the 2000's
Hitachi hard drive
why do i think this?
well the hard drive works perfectly on win32 and linux....for prolonged periods of time...months
really....and only has a slight error as mentioned above in a microscopic amounts of that running time..... and the error goes away after an hour or so...or when temps have dropped and reboots issued.
strange indeed.
faulty hard drive?....or somekind of re-call laptop thing on HDD compatability?
Still, this does me no favors....i can't put a 1 gig SWAP file onto this hard drive for TCL.....gparted does not like the drive
next may even try unetbootin...to put TCL onto the actual machine
You see, TCL performance is very poor on a USB 2.0 swap....
Vince.
Juanito:
Did you try to use ntfsprogs directly, rather than via gparted?
Rich:
Hi cast-fish
Prior to resizing you should have Windows de-frag the drive a couple of times. Also, the drive can not be mounted when resizing.
--- Quote ---the stripping military grade tool i used earlier DID report that this drive had an error and block zero ...
--- End quote ---
Are you are referring to a track 0 error, or maybe no free blocks available for remapping?
cast-fish:
Hello,
THanks for the replies.
Juanto.....nope. I have used Gparted years and it's very rare to refuse to do something to a HDD.
THe HDD Is fresh....fresh OS too.
Rich, the drive was not mounted. The drive was not defragged...did not need it .....win32 reported.
The military grade tool which reported "Block Zero error "sector" zero etc....nothjng about tracks.
(but completely re-running that military grade tool a second time from a cold boot reported NO problems ....and succeeded.....mentioned earlier)
You see, electronic equipment gets a thing called "chip creep" after long periods of time. Many industrial situations never ever switch off hardware, during it's entire lifecycle for this reason.
Gparted don't like the HDD....points to a faulty HDD. The other tool also reported a fault on this hard drive. It's actually the Hard drive that manifests the fault mentioned above....not other parts of the machine like screen, or keyboard signals or bios's unhappy
therefor
Vince
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version