Fixing PartitionMagic Error 108


Recommended Posts

Can you boot Linux (from drive or LiveCD) and post the output of a

sudo fdisk -l (that is a lowercase letter "L", not the number one)

If you don't use sudo, then just su to root and do the command without "sudo".

This will provide a detailed list out of your partition information.

 Disk /dev/sda: 80.0 GB, 80026361856 bytes
 255 heads, 63 sectors/track, 9729 cylinders
 Units = cylinders of 16065 * 512 = 8225280 bytes
 Disk identifier: 0x005a42a7

	Device Boot	  Start		 End	  Blocks   Id  System
 /dev/sda1   *		   1		7012	56323858+   7  HPFS/NTFS
 /dev/sda2			7181		7377	 1574339   82  Linux swap / Solaris
 /dev/sda3			7377		9729	18900472   83  Linux

You have a strange gap from 7013-7181. That isn't going to be a problem, just difficult to use that space, unless you expand an adjacent partition.

The problem is almost certainly how sda2 uses up to 7377 at the end, and also sda3 uses the same point to start. These partitions cannot share the same data.

Is sda3 readable from within your LiveCD? If so, then the start point for that is probably correct. In that case, delete the sda2 partition, and immediately re-declare it from 7181 to 7376. Keep the 82 type. Reboot, and you should be ok.

P.S. I :heart: the power of *nix commandline

P.P.S. sda2 is swap :pinch: Didn't notice that, oddly enough. It is surely safe to reduce the back end of that by one. (Y)

How do I move the swap partition around? I can't get into PartitionMagic, and my laptop has several problems with Linux CDs (it took me 3 days to get my laptop to recognize the Linux DVD, which is odd because it can read everything else (Windows, DVD Movies, etc.) perfectly).

  markjensen said:
Then how did you boot Linux to get that information? :unsure:

You didn't understand my partition setup...

60 GB NTFS for Windows

18 GB EXT3 for (SuSE 10.3) Linux

2 GB Swap

You see, I have Linux on my computer, it is a dual-boot computer using the Windows NT bootloader.

New Partition Setup...

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x005a42a7

   Device Boot	  Start		 End	  Blocks   Id  System
/dev/sda1   *		   1		7012	56323858+   7  HPFS/NTFS
/dev/sda2			7013		7376	 2923830   82  Linux swap / Solaris
/dev/sda3			7377		9729	18900472   83  Linux

All I was asking is to boot back into the Linux environment you used to get the initial "fdisk -l" info. Then use fdisk to re-create the swap.

It looks like you did that. Does everything work ok? Does PM still report that error now that you corrected your start/end locations? I hope so, because I don't see anything else wrong with that setup.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Gatekeepers? I’m a lifelong Linux user, longer than you! In fact I still use Windows 11, MacOS and Opensuse tumbleweed along with AnduinOS. You’re gatekeeping Windows over Linux!!! There is plenty of Linux distros for beginners!!! You’re no Linux user if you promote against it!!!
    • Windows 10 is the reason why we are so conscious about privacy now by Usama Jawad About a year ago, Microsoft debuted Recall in Windows 11, a feature that would record and remember everything that you do on your PC, allowing you to ask more contextual questions about your various activities and workflows from a dedicated assistant. Although the Redmond firm offered various privacy controls for Recall and even made it opt-in rather than mandatory, the launch was a disaster and the company had to recall Recall. All of this happened because people were not happy that Microsoft would record everything that they do on their PC and then share that information with an AI model, despite the company's assurances that all of this would happen locally and no data would be sent to Redmond's servers. Couple that with some lackluster security features and it was just a disaster waiting to happen. Although things have improved quite a bit since then, thanks to extensive testing in Insider Channels, some third-parties are still giving users controls that will allow them to block Recall for the vendor's software. I personally believe that this is a good thing, and we definitely should have more scrutiny around software that captures our activities (even with our consent). But as we approach Windows 10's 10th birthday and eventual end of support date, I can't help but realize that the main reason behind Windows customers being very privacy conscious nowadays is the beloved Windows 10 operating system itself. Windows 10 and the telemetry fiasco To truly understand what I mean, we have to go back a decade, to the launch of Windows 10 in 2015. Although the operating system has an ardent fanbase now, things weren't always this way. In fact, Windows 10 had a fairly rocky launch, and one of the reasons behind this was dreaded word telemetry. Anyone who has spent some time in the field of software development and productionizing solutions knows that telemetry typically the anonymized collection of data from various signals to monitor the health of software and diagnose a problem in case of any issues. Telemetry is very useful, for example, in cases where your Microsoft Word application may unexpectedly crash. Microsoft would monitor the telemetry logs from this crash, diagnose the problem, and ideally deliver a fix so that it doesn't happen on your or anyone else's device again. Now, telemetry collection is a regular process, all major software vendors have it at some level. However, when Microsoft decided to mention it in their privacy statement for Windows 10's Technical Preview (this is what Windows Insider Previews were called at that time) in 2014, there was massive uproar. Things spiraled to the point that people began to allege that Microsoft is spying on literally everything that you do through Windows 10. The backlash was so significant that by April 2015, a few months prior to the launch of Windows 10, Microsoft was scrambling to add new privacy controls in the operating system in response and the ability to delete content that Cortana (R.I.P) remembered about you. Heck, we even had software pirates and torrent-sharing groups banning Windows 10 over privacy concerns. Even Russian law firms began applying pressure on Moscow to investigate Microsoft over Windows 10's alleged spying. By 2017, Microsoft was under scrutiny from Switzerland, France, and other European authorities because of these claims. During this tumultuous period, the Redmond tech firm was constantly putting out statements to convince people that Windows 10 does not spy on you, all while building a dedicated privacy dashboard for the operating system and fixing actual Windows 10 privacy bugs. It was clear that Windows 10's launch hadn't been as smooth as the company probably would have wanted. Turning the privacy corner Things finally started to go in Microsoft's favor in April 2017, roughly two whole years after the launch of Windows 10. This was primarily because of the firm's increased transparency regarding data collection, enhanced privacy controls, and useful privacy reminders when installing new versions of Windows 10. By August 2017, Microsoft put out a statement saying that it is seeing "positive reception" from customers regarding privacy, indicating that it had finally turned a corner on the specific topic. This did not mean that Microsoft had been completely absolved by the public and regulators. It was still the target of regular regulator scrutiny, despite releasing new privacy controls frequently and constantly assuring customers that their data is not being sent to Microsoft without their consent. But it was clear that the worst was now behind. Where we stand now I would argue that the entire privacy and telemetry fiasco surrounding Windows 10 was blown out of proportion. I will emphasize again: telemetry collection is a regular process in software development and productionization, and it's something that every big firm does. However, a target was put on Microsoft's back just because it was a hot topic to spread fear, uncertainty, and doubt (FUD). As a Windows 10 veteran who has been around since the earliest days of the operating system's Technical Previews, I'm glad that we still managed to extract something positive out of this experience. Microsoft became very conscious about privacy (until Windows 11 Recall, that is), while we as customers began to understand that our data matters to us. Just because Windows 10 was not spying on us didn't mean that no one else is either. Media outlets like Neowin also became conscious of the topic, which is the main reason why we were able to avoid the disastrous initial launch of Windows 11 Recall. Despite how all of this started, all the FUD, I'm at least glad about where we ended. Although Windows 10 is adored by Microsoft customers even now, things weren't always like this. And as we celebrate the 10th birthday of the OS and its imminent device, it's important to be mindful of the fact that this is the operating system that made us so conscious about software privacy, and that's a good thing. This story is a part of our "10 Years of Windows 10" collection, in celebration of the operating system's tenth anniversary, falling on July 29, 2025. Over the next few days and weeks, you'll be able to find more content on this topic in our dedicated section available here.
    • Why suggest Windows 10 LTSC and not Windows 11 LTSC IoT? Hmm?
    • And this is exactly why many people avoid Linux, because of the fanatic gatekeepers like you. If you don't have anything intelligent to say, just keep quiet, the adults are talking here, buddy. By the way, Linux user here.
  • Recent Achievements

    • Dedicated
      CarlosABC earned a badge
      Dedicated
    • One Month Later
      solidox earned a badge
      One Month Later
    • Week One Done
      Stephen Leibowitz earned a badge
      Week One Done
    • Week One Done
      Homayoun Hotak earned a badge
      Week One Done
    • Dedicated
      Profit earned a badge
      Dedicated
  • Popular Contributors

    1. 1
      +primortal
      639
    2. 2
      ATLien_0
      240
    3. 3
      Xenon
      171
    4. 4
      neufuse
      154
    5. 5
      +FloatingFatMan
      122
  • Tell a friend

    Love Neowin? Tell a friend!