TestDisk fulled my hdd - cannot boot Topic is solved

[xbitz]

I tried to recover some deleted files with TestDisk.
It started generating some .dd file on the /home/user/Desktop directory (i used it wrong).
Then it gave me a message that the disk is full.
I exited the application and deleted the .dd file.

However, i could not re-enter ubuntu, i just got a message at the boot process.

I enetered with a linux live usb disk and i opened the filesystem.
The size available were 0 bytes, that's why it could not boot previously.

However, no matter where i looked, i saw no files i could delete.
So where is all the space that TeskDisk has consumed? Where are all the files it has generated?

[recuperation]

I don't know where Testdisk writes files under Linux.
I would look into the home directory of the user you used.
Otherwise I would use the commands du and tree to find the file.

[xbitz]

Is it only one file? Or did it create many files?

[recuperation]

That depends on what you did using Testdisk. What do you mean by "wrong"? Did you intend to restore files with the extension "dd"?

[xbitz]

I am not exactly sure because i was in panic. But i think it was creating an image of my hdd,, but in the same partition, which is dumb.

It asked me for a folder to write to (ehich i have deleted), but while it was doing its work, i saw a .Dd file in the Desktop.

Then it told me that the disk is full.
I exited the applicationand i deleted the. Dd file.

Turned off, and when i turned on, it could not reboot.
Booted a live linux from usb, and i didnt see any files at the desktop. But still, i have zero bytes available. I dont understand what is going on?

Could it have made copies of each and every file in the system? If yes, where are they?

Are there any commands where i can find what's going on?

[recuperation]

You either restored files from a partition or you generated a backup from a whole partition. The latter only produces one file.
You should remember what you did.

Your new questions suggest that you did not read my answers.

[xbitz]

I dont understand why you are being so aggressive.
I read your answers.

I dont understand what i was doing exactly because i was in panic.

It asked me for a file to write to, i but i have deleted both the. Dd file and the folder.

I saw your post about the du and tree commands, i just asked for more soecofocs on their usage, thats all.

[recuperation]

I said:

Otherwise I would use the commands du and tree to find the file.

You answered:

Are there any commands where i can find what's going on?

Now you pretend

I saw your post about the du and tree commands, i just asked for more soecofocs on their usage, thats all.

and you are saying that I am aggressive.

Thank you.
I am leaving now to an English class to work on my reading disabilities.

[xbitz]

I don't understand why you say i am pretending. I saw the commands, i just asked for more specific usage if that was possible.
Sorry if i gave out a feeling that i wasn't appreciating your help.

Anyway, i found the log file. I will dump its contents here:
Hope it will help make sense

Code: Select all

Fri Oct 23 18:18:28 2020
Command line: TestDisk

TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
OS: Linux, kernel 5.4.0-52-generic (#57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020) x86_64
Compiler: GCC 9.2
ext2fs lib: 1.45.5, ntfs lib: libntfs-3g, reiserfs lib: none, ewf lib: none, curses lib: ncurses 6.1
/dev/sda: LBA, LBA48 support
/dev/sda: size       1953525168 sectors
/dev/sda: user_max   1953525168 sectors
Warning: can't get size for Disk /dev/mapper/control - 0 B - 0 sectors, sector size=512
Warning: can't get size for Disk /dev/loop26 - 0 B - 0 sectors, sector size=512
Hard disk list
Disk /dev/sda - 1000 GB / 931 GiB - CHS 121601 255 63, sector size=512 - WDC WD10SPZX-75Z10T2, S/N:WXP1A39AER71, FW:03.01A03
Disk /dev/sdc - 7759 MB / 7400 MiB - CHS 1022 239 62, sector size=512 - TOSHIBA TransMemory, FW:1.00
Disk /dev/loop0 - 9588 KB / 9364 KiB - 18728 sectors (RO), sector size=512
Disk /dev/loop1 - 102 MB / 97 MiB - 200088 sectors (RO), sector size=512
Disk /dev/loop10 - 63 MB / 60 MiB - 124440 sectors (RO), sector size=512
Disk /dev/loop11 - 70 MB / 67 MiB - 138368 sectors (RO), sector size=512
Disk /dev/loop12 - 58 MB / 55 MiB - 113296 sectors (RO), sector size=512
Disk /dev/loop13 - 32 MB / 30 MiB - 63360 sectors (RO), sector size=512
Disk /dev/loop14 - 280 MB / 267 MiB - 548728 sectors (RO), sector size=512
Disk /dev/loop15 - 114 MB / 108 MiB - 223160 sectors (RO), sector size=512
Disk /dev/loop16 - 143 KB / 140 KiB - 280 sectors (RO), sector size=512
Disk /dev/loop17 - 133 MB / 126 MiB - 259952 sectors (RO), sector size=512
Disk /dev/loop18 - 52 MB / 49 MiB - 101960 sectors (RO), sector size=512
Disk /dev/loop19 - 228 MB / 217 MiB - 446248 sectors (RO), sector size=512
Disk /dev/loop2 - 102 MB / 97 MiB - 200168 sectors (RO), sector size=512
Disk /dev/loop20 - 114 MB / 108 MiB - 223160 sectors (RO), sector size=512
Disk /dev/loop21 - 53 MB / 50 MiB - 103776 sectors (RO), sector size=512
Disk /dev/loop22 - 65 MB / 62 MiB - 127160 sectors (RO), sector size=512
Disk /dev/loop23 - 57 MB / 54 MiB - 112552 sectors (RO), sector size=512
Disk /dev/loop24 - 280 MB / 267 MiB - 548728 sectors (RO), sector size=512
Disk /dev/loop25 - 32 MB / 30 MiB - 63344 sectors (RO), sector size=512
Disk /dev/loop3 - 170 MB / 162 MiB - 333096 sectors (RO), sector size=512
Disk /dev/loop4 - 63 MB / 60 MiB - 124888 sectors (RO), sector size=512
Disk /dev/loop5 - 170 MB / 162 MiB - 333048 sectors (RO), sector size=512
Disk /dev/loop6 - 267 MB / 255 MiB - 523400 sectors (RO), sector size=512
Disk /dev/loop7 - 9924 KB / 9692 KiB - 19384 sectors (RO), sector size=512
Disk /dev/loop8 - 651 KB / 636 KiB - 1272 sectors (RO), sector size=512
Disk /dev/loop9 - 170 MB / 162 MiB - 333552 sectors (RO), sector size=512
Disk /dev/nvme0n1 - 256 GB / 238 GiB - CHS 244198 64 32, sector size=512

Partition table type (auto): EFI GPT
Partition table type (auto): EFI GPT
Disk /dev/nvme0n1 - 256 GB / 238 GiB
Partition table type: EFI GPT

Interface Advanced
hdr_size=92
hdr_lba_self=1
hdr_lba_alt=500118191 (expected 500118191)
hdr_lba_start=34
hdr_lba_end=500118158
hdr_lba_table=2
hdr_entries=128
hdr_entsz=128
check_part_gpt failed for partition
 2 P MS Reserved              1333248    1595391     262144 [Microsoft reserved partition]
check_part_gpt failed for partition
 3 P MS Data                  1595392  262678527  261083136 [Basic data partition]
 1 P EFI System                  2048    1333247    1331200 [EFI system partition]
 2 P MS Reserved              1333248    1595391     262144 [Microsoft reserved partition]
 3 P MS Data                  1595392  262678527  261083136 [Basic data partition]
 7 P Linux filesys. data    262678528  430260223  167581696
 8 P Linux Swap             430260224  463464447   33204224
 4 P Windows Recovery Env   463464448  465491967    2027520
 5 P Windows Recovery Env   465491968  497444863   31952896
 6 P Windows Recovery Env   497446912  500084735    2637824
disk_image write() failed: No space left on device
No space left for the file image.
SIGHUP detected! TestDisk has been killed.

[xbitz]

Hello!
I managed to solve the issue.
The .dd file was still in the trash, so i went ahead and deleted.
Space is freed and everything boots now.

I want to thank you for the help, and sorry for the misunderstandings!
Have a nice weekend!