News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon

Blog Archives

  • There goes another excuse for not backing up

    Posted on May 13th, 2018 at 14:51 woody Comment on the AskWoody Lounge

    Just got a message from Noel Carboni.

    I just ordered another new backup drive from Amazon (via your home page link), a MyBook 8 TB drive.

    The price was decent I think – $169.99. For EIGHT TB. I’ve seen Seagate 8 TB drives for less, but I prefer the Western Digital brand myself.

    I would post this on your site in a post encouraging people to do backups – but I don’t know how to format the link to make sure you get your commission.

    Problem solved. 🙂

    Seriously, this is an amazing price for a very capable piece of hardware. If you aren’t doing backups, you just lost another excuse.

  • Newly reported chkdsk bug in Windows 7 on Western Digital drives

    Posted on May 28th, 2017 at 09:41 woody Comment on the AskWoody Lounge

    This in from reader NR:

    Hello, Woody !

    I want to share to you my recent experience running chkdsk /f /r on licensed Windows 7 Professional SP1 on two different types of WD Black and Enterprise hdd, WD5003AZEX and WD5003ABYX.

    The scenario looks like that: 2 partitions, C:\ and D:\, no recovery partition. On C:\ is windows installation, on D:\, data archive. Both NTFS. D:\ could be primary or logical, doesn’t matter.

    The drives are SATA3 and SATA2, but THE CONTROLLER WORKS ONLY ON IDE (ATA) MODE, due to a motherboard limitation (2008 – 2009).

    So, we are running chkdsk /f /r on drive D:\. The logfile says at the end “no problems found”, but at the beginning of the logfile appears a message like this:

    “CHKDSK is verifying files (stage 1 of 5)…
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x0 for possibly 0x2 clusters.”

    Additionally, i’ve run chkdsk on C:\ too. The error is not there.

    I’ve suspected the drives, but all the serious hdd programs i know says: The status of the drive is PERFECT. No further action required.

    From 6 WD hdd i’ve tested, only ONE doesn’t have this error (on partition D:\), and IS WORKING IN AHCI MODE. The rest of hdd’s configurations are identical (ATA). All pc’s are up to date with Windows Updates, Group B.

    I push the things forward and make a fresh install of Windows 7 SP1, on one of hdd’s, WITH NONE OF UPDATES, AND ON IDE (ATA) MODE. THE ERROR DOESN’T EXIST.

    The two conclusions are:

    The error appears only on IDE (ATA) mode, but with all the windows updates applied. The error is not present in AHCI mode, regardless if all the windows updates are applied.

    The difficult question is: what Microsoft KB could make this mess ?

    I’m concerned about the data safety on these hdd’s. You could see the error in the logfile attached.

    Any help will be appreciated. Thank you.

  • OS X Mavericks upgrade destroys data, reports Western Digital

    Posted on November 4th, 2013 at 20:51 woody Comment on the AskWoody Lounge

    Until Apple issues a workaround or patch, it would be very wise to avoid using any external hard drive, or any eSATA- or Thunderbolt-based peripherals, on Mavericks systems.

    InfoWorld Tech Watch