a request to this de device has been cancelled

TVeblen said:

I would say you have little choice. If the drive is failing then you are lucky to be able to transfer data at all.

Keep it going and hope it does not crap out on you in the middle of it. It may be the only chance you get.

hey How are we doing?

ok, today all my data have been transfered and backed up, except some files which did not transfer with a message like: "This file is no longer located in D:........"

Strange, I could see the files (and all subfolders) but in properties they were 0kb in size.
Hopefully these file were not so significant.

Right now I ran WD Data Lifeguard and chose the option to WRITE ZEROS (quick erase option) and it's doing fine.
Hopefully this will get rid of the problem.

I still want to know why Data Lifeguard would not show SMART for my WD hdd's.

And also, something new that I discovered (and a little out of subject) is that my cpu fan does not respond to SMART fan target.
I mean when the cpu is getting hotter the fan would not speed up even though I have it setup for that in the BIOS...

If you guys could share some knowledge here I'd aprecciate it..
Thanks

Ok , I am about to initialize the HDD, I have a couple of options here: MBR or GPT.
Searching the internet I found this:
Perhaps one of the biggest pitfalls of MBR-based disks is their potential for corruption of the partition table, a region on the disk that maps sectors to logical block numbers. MBR disks only have 1 partition table to keep track of all the blocks in the partition. If the table becomes corrupt, the entire disk must be recovered from backup. Windows GPT-based disks have multiple, redundant partition tables so that if one is detected as being corrupt, it can self-heal itself from a redundant copy of the table.

GPT vs MBR Disk Comparison

This is very interesting, this hdd had the partition corrupted I believe, so I am about to choose GPT to initialize my disk, What do you guys think?

Thanks

TVeblen said:

I have not played with GPT yet. So I have no opinion on that.

But I never like to create a new problem while I'm working out an old problem. So if it were me I would format MBR and then see if my problem was cleared. If it was then I would consider reformatting GPT.

Otherwise, if you do have problems (old or new) you will have to wonder if it is due to GPT or not.

As for fan speed issue: are you sure you have the CPU fan plugged into the correct header on the MB?

of course...

TVeblen said:

If you are sure you have the wiring correct, the settings in the BIOS correct, and the observations are correct, then you are left with:

• A defective motherboard
• A corrupted BIOS.

The BIOS could be corrupted "out of the box", which means it requires a BIOS upgrade, or it could mean you simply need to reset the BIOS defaults or clear the CMOS to reset all.

ok i will try upgrading the BIOS to see if that fixes the problem, thanks

amoretam said:

Ok , I am about to initialize the HDD, I have a couple of options here: MBR or GPT.
Searching the internet I found this:
Perhaps one of the biggest pitfalls of MBR-based disks is their potential for corruption of the partition table, a region on the disk that maps sectors to logical block numbers. MBR disks only have 1 partition table to keep track of all the blocks in the partition. If the table becomes corrupt, the entire disk must be recovered from backup. Windows GPT-based disks have multiple, redundant partition tables so that if one is detected as being corrupt, it can self-heal itself from a redundant copy of the table.

GPT vs MBR Disk Comparison

This is very interesting, this hdd had the partition corrupted I believe, so I am about to choose GPT to initialize my disk, What do you guys think?

Thanks

I don't think the issue was due to corruption of the partition table. There is not that much data there to corrupt (and if it was corrupt a 'chkdsk' would have no effect; you'd have to use other software to recover it). All it contains is the partition status, size, location and such, no file table. Your chkdsk results indicated a problem within the file table contained within the partition itself (and there is a backup copy of that anyway (also within the partition)).

The 'chkdsk' name is somewhat deceptive, it could be named a little more appropriate as 'chkvolume' or maybe 'chkpartition', as it really doesn't do a whole 'check disk'. It's only used to check/repair issues with the file system and space within a volume that's accessible and readable by Windows. It's been around for 25+ years as 'chkdsk' though so I doubt they'll change it anytime soon.

TVeblen said:

I have not played with GPT yet. So I have no opinion on that.

But I never like to create a new problem while I'm working out an old problem. So if it were me I would format MBR and then see if my problem was cleared. If it was then I would consider reformatting GPT.

Otherwise, if you do have problems (old or new) you will have to wonder if it is due to GPT or not.

Agree with TVeblen here as well, on all points. One more reason to consider going with MBR is the fact that it's been in use for years and I think it still is the predominant 'format' in use (so easiest to get help for). As GPT becomes more prominent due to disk size increases and a few other reasons the MBR format may eventually fade out. Not for quite awhile though.

amoretam said:

I still want to know why Data Lifeguard would not show SMART for my WD hdd's.

You're not going to be able to access the drive's SMART feature unless the software can communicate directly with the drive. RAID hard/firmware can block that access and connecting the drive 'unconventionally' (eg, third party USB/SATA adapter) can block it.

amoretam said:

TVeblen said:

If you are sure you have the wiring correct, the settings in the BIOS correct, and the observations are correct, then you are left with:

• A defective motherboard
• A corrupted BIOS.

The BIOS could be corrupted "out of the box", which means it requires a BIOS upgrade, or it could mean you simply need to reset the BIOS defaults or clear the CMOS to reset all.

ok i will try upgrading the BIOS to see if that fixes the problem, thanks

Try the reset/clear first.