• Error Dmg Aborting Because No Mount Point Found Inside
• Error Dmg Aborting Because No Mount Point Found Without

I've also tried using hdiutil to convert the dmg to an iso to mount in XP, and no luck there either. I've tried verifying and repairing the image file in Disk Utility, and neither worked. I know the data's there in some form or another - because the image file is 90 GB.

• Aug 5 18:10:10 MacBook-Pro bless707: Disk at mount point (/Volumes) doesn't appear to be backed by a TDM system, using running device identity Aug 5 18:10:10 MacBook-Pro bless708: Disk at mount point (/Volumes) doesn't appear to be backed by a TDM system, using running device identity.
• 2020-06-03 08:57:45-07 Calvins-iMac systeminstalld922: copydmg: 2020-06-03 08:57:45.067 diskimages-helper2303:35843 mountDevEntries: disk3s1 aborting mountpoint postflight because disk image has no band size specified.

Thank you all for your replies :-)

What happens when you do try the suggestion given by it?

I don't exactly know how I should 'repair manually'... I thought a filesystem check in GParted would have been enough...

You can boot the system using a archlinux live cd, and run fsck manually on every linux partition in the old system with options.
DON'T mount any of the filesystems before running fsck, or your data will probably be lost. If you want to check the partition information first, run fdisk -l with root privileges.

Thanks. I tried booting from an ArchBang live CD last night and ran 'e2fsck -pcv' on each partition. The check completed, but the problem persists... I just tried again using 'fsck' as you suggested and got the following output (but the machine still fails to boot with the same error as before):

Error Dmg Aborting Because No Mount Point Found Inside

Error Dmg Aborting Because No Mount Point Found Without

As mentioned already, the reason it's failing is because the /dev/sdb2 partition is mounted before it can be fsck'd. What is this partition exactly (which filesystem, what's on it, mountpoint,...)?

I'm not overly familiar with the Linux boot process, but why would it suddenly be mounting this partition before fsck-ing it? Even if it was mounted when the netbook shutdown, surely the boot process starts with all partitions unmounted...? Anyway, the partition details from /etc/fstab are below.

I'm (now) aware that mounting /usr as a separate partition is a bad idea and (having read the 'Error when booting with the new initscripts' thread), I have told pacman to ignore updates to the initscripts package (until I figure out how best to work round or fix that issue).

Write umount /dev/sdb2 in konsole or unmount partition in gparted by right click on problematic partition and click unmount. Than proced.

If I type 'umount /dev/sdb2' at the prompt, I get the following error:

I tried 'umount -l /dev/sdb2' to unmount when the device becomes free... but it never does.

I also booted into GParted, but there is no option to 'unmount' /dev/sdb2. There is a 'mount' option in the menu, but it is greyed out. If I open a terminal window from the GParted Live environment and type 'sudo umount /dev/sdb2' I get the following message:

Are you mounting the root drive with 'ro' (read only) in fstab?

No (as shown above). I don't *think* I've messed anything up with fstab or any other config files -- everything was working perfectly till the netbook shutdown whilst pacman was running.