Resolved Possible hardware issue

One of the reasons I recommended the plain'ol UBCD version.

Here are a couple of direct download links for V5.2.0:

1. ftp://ftp.cc.uoc.gr/mirrors/linux/ubcd/ubcd520.iso
   
   
2. http://ftp.cc.uoc.gr/mirrors/linux/ubcd/ubcd520.iso
   
   Size: 417MB
   
   MD5/SHA1 checksums:
   
   
   [MD5] f359cb6d0f383c4d00903f63cfe42830
   [SHA1] a1c8224451b297530d9f11959524225fa5910024
   [SHA-256] b58901ec524efea67c6638dc02863aff1300fdb8a6f7e223a564640411bd8b74​

 

CHKDSK checks the file system. The hard drive manufacturer's diagnostic utility checks the hardware.

 

Thanks Spyware Dr, - I was also having issues booting from my cdrom so I`ve had to go into the bios to alter the boot order, I`m still not seeing the disks I`ve made though, but will persevere so thanks for the new links.

I don't know the make of the HDD and my case is sealed so I`m worried that breaking the seal will invalidate my warranty. I`m going to do a bit of googling and see if I can narrow it down to the manufacturer.
Will also read up on chkdsk - haven`t run it yet (& won`t if I don`t need to)

One last question, asked out of curiousity. -I believe there is a utility called ChkBack which can recover data lost when Chkdsk relocates file fragments.
Why is there a need for such a utility? - does Chkdsk actually damage data when recovering fragments? - I thought it just relocated them for use again.

 

Did you check in the Device Manager\Disk Drives then post the drive info. If you already tried this my apologies to you.

 

Thanks - it says its a "ST2000DM01-9YN164" which I assume means a 2TB Seagate drive (SATA)?

Edit :- Have now run "Seatools" from seagate website and it passes all tests.
So I guess I`ll test the RAM next.

 

Yes, the "ST2000DM001" is a Seagate Barracuda 2TB 7200 RPM 64MB Cache SATA 6.0Gb/s 3.5" Internal Hard Drive

Excellent!

And if that also passes, you're finally ready to run "CHKDSK /F ".

 

I recommend running chkdsk /r instead of /f. The /r switch performs the same tasks as /f, but includes more thorough checks as well. See chkdsk /? for details.

 

Two problems :-
One . - I can`t boot from cdrom - despite changing boot order in bios I`m just getting "Non system disk" error when I try to.

Two. - Can`t run CHDSK at all - getting message saying it can`t run because a process is preventing it , but does not identify the process. - it asks if I want to run CHKDSK at next reboot but when I answer yes and reboot it seems to run it but completes in seconds saying it has passed - it seems too quick, as if its not running at all.

I think I`m just going to wait and see if it fails altogether, I`ll just have to put up with its failings for now and wait.

TBH I am just suspicious of windows 8 itself - I think maybe I`m expecting too much from it. It does not seem to be a "stable" O/S IMHO.

Edit :- one reason for this viewpoint is that I had been running Linux from a wubi installation before I upgraded to win 8 Pro and did not have a problem with it so I suspect the hardware is O.K.

Edit2:- the CD is O.K. - it boots O.K. on my laptop.

 

WELL....

It Died.

First I could not open windows explorer windows - double clicking on a folder just opened the properties window for the folder, SO.... I re-booted.
OOPS.
Bios password requested,--o.k.
wait for bitlocker password request....it asks me what language keyboard I am using...
(Strange?) entered UK, -- now requesting bitlocker unlock key.(No password?)

After much digging around , I found & entered key - now I`m in the "repair/goto windows 8 /boot from USB or DVD/open Dos prompt/system restore "--- screen.

goto windows 8 just reboots into the key request screen again

repair says "cannot repair "

I tried the system restore option

the restore seemed to complete o.k. but then rebooted into the key request screen

tried the repair DVD -same again - just reboots into key request screen.

opened a dos prompt - I am in an X:\windows\system32 directory.

I opened a diskpart /list and everything LOOKED normal ,- I can mount c: and see my directorys

The continuous looping back to the bitlocker key request screen is slowing everything down and is a PITA so I am currently decrypting the drive in dos with the manage-bde -off command.
at its current rate it wont complete until later tonight.

Any ideas as to what I do next?

any help would be gratefully received.......