Please be aware that I am not using Veracrypt but I know its predecessor Truecrypt.
From what I've read I understand that it's possible I corrupted some of the key header data,
You are wrong and you could have simply found this out by reading the Truecrypt/Veracrypt manual. As this is outlined in a picture in there, no special computer knowledge is ...
You are booting from the Windows 7 partition, which is the only primary
partition. Therefore you can't delete it, as Windows cannot be
started from a logical drive.
If you would like to reuse its disk-space, I suggest to boot to
Windows 7 and use Disk Management to reduce the size of the
partition as far as it will let you. Ensure that there is at least
1 GB ...
There are not two partitions. There is 32MB of empty space and a single partition taking up the rest of the space.
Typically space is left unallocated on drives in general cards due to partition alignment and SD cards and SSD in particular to allow the system to align partitions with erase blocks.
In the grand scheme of things having 32MB of unallocated ...
It looks like the .grubparts file is from the wrong disk. Your "old" partition list shows a normal MBR-format partition table, but what you restored looks like the "protective MBR" that is normally found on GPT-partitioned disks – it has the special partition of type 0xEE that usually indicates "you shouldn't be looking here, you ...
Actually, using LUCKS worked best for me. I found this article which walks you through the whole process.
The steps I used were:
First create an empty image. fallocate -l 512M enc.iso
Then encrypt it with cryptsetup. cryptsetup -y luksFormat enc.iso
A simple solution would be to use the free and open-source
It supports full-disk encryption, but also encrypted containers.
A container looks like a file that requires a password for mounting,
so can be used cross-platform (select for that a cross-platform
You will find documentation on the VeraCrypt site, but also many ...
Yes, there is a big benefit for a separate Windows primary partition, and that is the possibility of imaging.
After installing a Windows plus adding antivirus plus some basic configuration, I create an image of the entire partition.
When I want to have a fresh copy of Windows, instead of installing it, I just restore it from that image.
This has the benefit ...
Is it possible to increase the unallocated space of this card?
Not through regular software.
"Unallocated space" is total reported device size minus any partitions. If you don't have any partitions then this is just the actual capacity of the card.
In other words, this isn't a matter of GParted anymore – your card's internal controller reports ...
Your layout is:
System Reserved partition
The C disk.
In order to merge the unallocated space into C, you need to:
Boot using a partition editor boot USB (Not into Windows!)
Move the System Reserved partition to the top of the disk.
The unallocated space will now move to between it and C.
Move C on top of the unallocated space.
I'd recommend just formatting it as a new partition.
I tried recently to overcome the same issue for the same reason using different tools such as gparted without success. After trying hard enough I succeeded in mangling up the drive to the point that I had to reinstall Windows.
I've been told that Paragon Hard Disk Manager can actually move those unmovable ...
This seems to be a problem:
/dev/mmcblk0p1 * 2048 249737215 249735168 119,1G c W95 FAT32 (LBA)
As per U-Boot Wikipedia page u-boot supports only FAT, not FAT32. U-Boot manual doesn't mention it either, just plain old FAT.
My reluctance to purchase a third-party program for a one-use event set me on a missing to find the truth. After hours of research, I stumbled on a post by James Preston who figured out what mbr2gpt was actually doing and potentially why it failed.
For posterity (and in case his site ever goes down) I will copy/paste his suggestion here for all to see:
The unallocated space must follow a partition to be able to merge it
into the partition.
Move nvme0n1p5 upward over the unallocated space, and it will then move
after the partition.
Now you can merge the unallocated space.
Take full backups, as partition work is dangerous in case of error.
If the disk is new and if it is high quality, then it may have had issues in the first format and setup coming from the way it was used.
In this case, formatting properly and seeing there are no errors, the disk should be perfectly fine to use.
If the disk is older and so has had long use, I would not trust a single format. Errors could be hidden by this, ...
The bad blocks are marked in table, that table can be cleared. so a good idea is to perform chkdsk * /r then badblocks might re-appear. If your toshiba drive is silent and has no more than 1000 working hours by smartinfo then it should be usable for long time.
You would need to move those two recovery partitions out of the way; and the second one (greyed out) is unmovable. Not a good idea, IMO, I just managed to kill a Win10 installation trying to do just this; to the point that I needed to reset the device wiping out the drive completely.
I'd rather create a new partition on the currently unallocated space. That'...
Take note that Windows 10 can grow to pretty big size over time, especially if you install games or large software. Mine takes up 90GB without games and without counting the swap file (122 total).
My C partition is 150GB with 27GB free. My advice is to prepare for the worst, better safe than sorry. 150GB C partition should be enough for most people in my ...
So the disks are GPT partitioned, but your system uses legacy BIOS, not UEFI. As per
The BIOS Boot partition GUID should be 21686148-6449-6E6F-744E-656564454649 (check blkid). If it is, install GRUB manually:
# grub-install --target=i386-pc /dev/sda
Then make the grub ...
The "System Reserved" partition (the first partition in your "within disk manager" screenshot) is used for booting, it contains the Windows boot loader and the boot configuration database (BCD), and must not be deleted (otherwise Windows won’t boot anymore).
Usually, this drive is hidden (no drive letter assigned), but from one of your ...
I've already run into 70 000+ consecutive bad blocks. ...... if
these bad blocks just mean I should replace the disk.
I am somewhat surprised the disk is even working. Retrieve what you can and replace disk right away (today if you can).
You probably have the wrong version Ubuntu. Did you download the Raspberry Pi ARM64 version? The Ubuntu for Raspberry Pi I found here
is an .xz archive containing
This is a normal .img file for Balena ...
+1 asks the 'chainloader' command to load the 1st sector of the partition. But your computer uses EFI firmware – it doesn't use boot sectors, so "+1" will do nothing useful at all. Instead, the parameter to the 'chainloader' command has to be a path to an *.efi executable file containing the bootloader.
Windows always installs its bootloader at \...
This worked for me (Ubuntu 20.04) without data loss:
Extend the GPT to the new drive size
# sgdisk -e /dev/sdX
Rescan the partition tables
# partprobe /dev/sdX
Resize the partition
# cgdisk /dev/sdX
cgdisk has a command-line Curses interface where you can navigate with the arrow keys to the partition you want and select 'Resize'. Then 'Write' the partition ...
Here is a community wiki on that topic: https://help.ubuntu.com/community/MovingLinuxPartition
Steps are too many to fit here, and probably will be subject to updates, so no point of maintaining the same steps here, hence only the link.
EDIT: I've managed to shorten this list a lot, for my case (cloning original partition /dev/sda1 to a new/larger partition /...
Switch the partitions. (In Windows, make the first partition NTFS and the 2nd partition ExFat.)
Then on Mac, reformat the ExFat partition to Mac (Journaled) or whatever you want.
I’m on Mac Mojave. It wouldn’t let me partition the unallocated part of a drive that was partitioned in Windows. But when I formatted both partitions as ExFat in Windows, I was able ...
This is technically possible. The filesystem on the USB stick must support sparse files for my method to work.
To tell ddrescue to recover a part of a file, use -m:
Restrict the rescue domain to the blocks marked as finished in the mapfile file. […]
You need to prepare many domain-mapfiles, each describing one rescue ...
Under Cygwin with an NTFS filesystem, the device number comes from the NTFS Volume Serial Number. There is a tool called VolumeID from Microsoft that lets you change it.
$ fsutil fsinfo ntfsinfo g: | grep NTFS
NTFS Volume Serial Number : 0xe3462385ec6d967e
$ ./Volumeid64.exe g: 8f70-...
GPT and MBR are disk partitioning formats. They allow a single physical disk to be split into smaller partitions (volumes)
Basic disk is a plain simple GPT or MBR disk. Each partition on a basic disk spans a linear continuous region on the disk. Dynamic disk OTOH is an abstraction layer above that so it can be constructed on either GPT or MBR formats. It ...
Since Windows 10 build 20185, Windows bootloader could read from refs, and some Chinese did succeed in booting it via multiple times DISM capture to different fs (including exfat).
so it is quite hacky.
My question: Is there any other way around using "ntfsresize" and using different tools to resize disk, or even clone without resizing. Thank you
Clone it at file level – use DISM (from the Win10 installer's CLI) to capture a .wim image from the old disk, then apply it to the new disk. This is almost the same mechanism as how Windows is installed, ...
Just running a Windows program to "fix" bad sectors isn't necessarily going to work, especially if it ran all night long. It's likely that it made many tries to read some sectors - but failed and moved onto the next sector. Does chkdsk validate your GPT/MBR partition information?
If a sector can't be read, it can't be repaired.
Presumably, you just ...