First time I saw this was after I installed a bunch of updates, which included the apm update. The drive doesn't have a suspend to disk file or partition - could it be related to this? Drive checks fine with both windows and linux, and ez-smart running on the windows side things that other than running low on disk space (which is true) that the drive is OK.
Wish I knew where this message originates. V. On Monday 13 January 2003 08:33 pm, J. Greenlees wrote: > Vincent Meyer, MD wrote: > > Hi, > > > > Getting this message whenever I boot up the machine, multiple times at > > different stages of the boot: > > > > ldm_validate_partition_table(): disk read failed. > > > > no idea why or what it means. What other info will help? > > only time I've seen disk read errors was when the drive was failing to > register with the bios. > or crashing ( ancient drive ) > if your partition table got damaged at all that could concievably cause > same error.
