1 Topic by Digital8Doug

  • Digital8Doug
  • New member
  • Offline
  • Registered: 2008-04-01
  • Posts: 6

Topic: MemTest86+ on new 3.6-5 LIVE, Only FAILSAFE version completes booting

Like the latest MemTest86+ version being on new 0.3.6-5 LIVE testing CD, even though 86+ dropped the DRAM & SPD timing change options for AMD 64 recently.
CD would not complete the booting process on Asus G2K-A1 notebook w/ latest 203 BIOS installed, TL-64 x2, ATI Radeon HD 2600, RS 690 chip in most modes. Only FAILSAFE would complete booting process.
(Safe Graphics settings, vga=normal) Hangs @ NET: Registered protocol family 2. 1st 2 options just a gray screen forever!

Was able to extend sda4 both forward & backwards w/o incident. Reclaimed space obtained by `SHRINK Volume' on vista HOME premium OS partition (sda2), and my 1st use of Gparted (http://gparted-forum.surf4.info/viewtopic.php?id=1262) that had reclaimed D:\ (DATA partition) space.

Did not encounter any excessively long time delays as bluemike or theplake experienced (http://gparted-forum.surf4.info/viewtopic.php?id=1273)

I then shifted the 24GB of data {3 GNU/Linux distros} that was sda5 (did not resize) to the very back end of my 160GB HD. Reading took ~ 36 minutes, actual moving data about another 1 hour or so. I neglected to record actual start & stop times as is  my normal practice.

Successfully completed task, noted post 2 of http://gparted-forum.surf4.info/viewtopic.php?id=1258

?*? What happens if I change the DiskLabel now ?*? Will I actually lose all my information, or is that an outdated warning ? { * RSVP via e-mail * }

2 Reply by class413

  • class413
  • Moderator
  • Offline
  • Registered: 2007-05-25
  • Posts: 2,376

Re: MemTest86+ on new 3.6-5 LIVE, Only FAILSAFE version completes booting

Thank you for your detailed report.

About DiskLabel:
Be careful, the recent feature concerns "partition labels" or "volume labels", not the DiskLabel.
About DiskLabel nothing changes. DiskLabel isn't any name for the disk, it is the entire structure of the master boot record, it is specific on the entire system where the disk in inserted, i.e. an intel-type system, or Spark, or powerpc, or other type of processor architecture.  Changing it, overwrites the MBR, so the entire disk content is deleted.

Perhaps it is possible to restore the previous status by restoring the MBR from a backup copy, but I would never try it!
smile

*** It is highly recommended to backup any important files before doing resize/move operations. ***

3 Reply by Digital8Doug

  • Digital8Doug
  • New member
  • Offline
  • Registered: 2008-04-01
  • Posts: 6

Re: MemTest86+ on new 3.6-5 LIVE, Only FAILSAFE version completes booting

Like the documentation @ main site, will be reading in entirety so that I work more intelligently!

class413 wrote:

snpd/EDTD Be careful, the recent feature concerns "partition labels" or "volume labels", not the DiskLabel. CORRECT afaik, NEW/Improved FEATURE WAS ADDED. Is supposedly better to refer to volume (partition) labels than by device (sda#) which may get out of sequence. Might be of concern and value for multi-booters & factory distribution testing {*}

About DiskLabel nothing changes. DiskLabel isn't any name for the disk, it is the entire structure of the master boot record, it is specific on the entire system where the disk in inserted, i.e. an intel-type system, or Spark, or powerpc, or other type of processor architecture.  Changing it, overwrites the MBR, so the entire disk content is deleted.
?*? CAN ANYTHING BE ENTERED as a DiskLabel; or only choose from a supplied list?*?

Perhaps it is possible to restore the previous status by restoring the MBR from a backup copy, but I would never try it!:)

Where is your sense of adventure & testing?? I was hesitant to even look after the caution which you explained more fully. TY
btw, I did the above w/o any B/U, never a good idea, but all data was downloaded ISO {*}

4 Reply by class413

  • class413
  • Moderator
  • Offline
  • Registered: 2007-05-25
  • Posts: 2,376

Re: MemTest86+ on new 3.6-5 LIVE, Only FAILSAFE version completes booting

DiskLabel depends on the hardware and the operating system.
Linux and mswindows on x86 type computers use the msdos label.
If you want to prepare a disk to work on a Sun machine or a Silicon Graphics workstation, you have to use the appropriate disklabel.

*** It is highly recommended to backup any important files before doing resize/move operations. ***