You are not logged in.
- Topics: Active | Unanswered
#1 2023-03-21 18:10:29
- Monero
- Member
- Registered: 2022-04-18
- Posts: 30
Internal EXT4 Disk Drive fails after having booted into windows
Sooo..
I have a process that downloads large files every night. Last night it completely filled the available disk space - unbeknownst to me.
I then had to (dual-)boot into Windows to do some things, and realized that the partition was gone. I started the partition manager in Windows and saw that the relevant drive was all shown as "unallocated". I didn't format it or anything. I immediately booted back into Linux, just to find that it didn't boot anymore because the partition wasn't recognized anymore. Mind you the partition only holds text data, nothing relevant to booting. Anyways, I removed the drive from /etc/fstab and was able to boot back into Arch. Tried mounting the drive myself and am getting:
xxx@local ~> sudo mount /dev/sda /mnt/tapes/
mount: /mnt/tapes: wrong fs type, bad option, bad superblock on /dev/sda, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.
I then launched gparted and am seeing that the drive contains the following:
/dev/sda1 - MICROSOFT RESERVED PARTITION: 16MB
UNALLOCATED: 9.1 TB
ok so now I am very worried that I won't be able to access my data anymore.
Can someone help me recover my data?
Thank you guys!
Offline
#2 2023-03-21 20:22:52
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 25,198
Re: Internal EXT4 Disk Drive fails after having booted into windows
Try to fsck the device/partition. Also check whether the drive itself is healthy and post the output of
sudo smartctl -a /dev/sdapotentially after having run a long smart test on it: https://wiki.archlinux.org/title/S.M.A.R.T.#Run_a_test
Offline
#3 2023-03-22 15:43:32
- Monero
- Member
- Registered: 2022-04-18
- Posts: 30
Re: Internal EXT4 Disk Drive fails after having booted into windows
Ok so the result of fsck is this:
xxx@local ~> sudo fsck /dev/sda1
fsck from util-linux 2.38.1
e2fsck 1.47.0 (5-Feb-2023)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda1
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>The long test for smartctl takes several days (I think it says 17000 hours apparently?), so in the meantime I am posting the short result:
xxx@local ~> sudo smartctl -H /dev/sda
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.2.7-arch1-1] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSEDI also ran testdisk with the following results:
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
OS: Linux, kernel 6.2.7-arch1-1 (#1 SMP PREEMPT_DYNAMIC Sat, 18 Mar 2023 01:06:36 +0000) x86_64
Compiler: GCC 12.2
ext2fs lib: 1.47.0, ntfs lib: libntfs-3g, reiserfs lib: none, ewf lib: none, curses lib: ncurses 6.3
Hard disk list
Disk /dev/sda - 10000 GB / 9314 GiB - CHS 1215865 255 63, sector size=512 - WDC WD101FZBX-00ATAA0, S/N:VCGZ8L7P, FW:01.01A01
Partition table type (auto): None
Disk /dev/sda - 10000 GB / 9314 GiB - WDC WD101FZBX-00ATAA0
Partition table type: EFI GPT
Analyse Disk /dev/sda - 10000 GB / 9314 GiB - CHS 1215865 255 63
check_part_gpt failed for partition
1 P MS Reserved 34 32767 32734 [Microsoft reserved partition]
Current partition structure:
No FAT, NTFS, ext2, JFS, Reiser, cramfs or XFS marker
1 P MS Reserved 34 32767 32734 [Microsoft reserved partition]
1 P MS Reserved 34 32767 32734 [Microsoft reserved partition]
search_part()
Disk /dev/sda - 10000 GB / 9314 GiB - CHS 1215865 255 63
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 32768 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 98304 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 163840 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 229376 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 294912 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 819200 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 884736 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 1605632 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 2654208 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 4096000 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 7962624 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 11239424 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 20480000 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 23887872 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 276714722 419954681057 419677966336
WBFS, 214 TB / 195 TiB
0 0000 0000 00 00 00 00 00 00 00 00
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 519959699 652911838 132952139
WBFS, 68 GB / 63 GiB
0 0000 0000 00 00 00 00 00 00 00 00
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 71663616 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 78675968 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 102400000 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 214990848 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
check_FAT: Bad number of sectors per cluster
check_FAT: Bad jump in FAT partition
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 512000000 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 550731776 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 644972544 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
check_FAT: Bad jump in FAT partition
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 6620483134 12774540029234749 12774533408751616 [CD{eWMWeC\&pe_oe_]
BeFS blocksize=2, 6540561 TB / 5948605 TiB
0 0000 0000 00 00 00 00 00 00 00 00
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 7228304118 8540139194 1311835077
FATX, 671 GB / 625 GiB
0 0000 0000 00 00 00 00 00 00 00 00
%?S Linux filesys. data 9731320723 9735841572 4520849 [
d]
cramfs, 2314 MB / 2207 MiB
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Mon Mar 13 08:21:25 2023
Linux filesys. data 9764602016 29297475743 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Mon Mar 13 08:21:25 2023
Linux filesys. data 9764658248 29297531975 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Mon Mar 13 08:21:25 2023
Linux filesys. data 9764658288 29297532015 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Mon Jan 16 14:07:10 2023
Linux filesys. data 9764759032 29297632759 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Mon Jan 16 14:07:10 2023
Linux filesys. data 9764759128 29297632855 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Sat Jul 23 16:59:48 2022
Linux filesys. data 9764911136 29297784863 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Sat Jul 23 16:59:48 2022
Linux filesys. data 9764911232 29297784959 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Sat Jul 23 16:59:48 2022
Linux filesys. data 9764911328 29297785055 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Sat Jul 23 16:59:48 2022
Linux filesys. data 9764911424 29297785151 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Sat Jul 23 16:59:48 2022
Linux filesys. data 9764911520 29297785247 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 10694755062 11808789317 1114034256
FATX, 570 GB / 531 GiB
0 0000 0000 00 00 00 00 00 00 00 00
check_FAT: Bad number of sectors per cluster
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 12515043946 16060501428 3545457483
FATX, 1815 GB / 1690 GiB
0 0000 0000 00 00 00 00 00 00 00 00
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 1934917632 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 15732554884 19692167584 3959612701 [Ň]
SysV4, 2027 GB / 1888 GiB
0 0000 0000 00 00 00 00 00 00 00 00
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 16749527777 16749527776 0 [eBQ>]
SysV4, 0 B
0 0000 0000 00 00 00 00 00 00 00 00
Linux filesys. data 16954935524 16955731053 795529 [__{p`]
cramfs, 407 MB / 388 MiB
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 17002468214 225613581173 208611112960
WBFS, 106 TB / 97 TiB
0 0000 0000 00 00 00 00 00 00 00 00
Disk /dev/sda - 10000 GB / 9314 GiB - CHS 1215865 255 63
Check the harddisk size: HD jumper settings, BIOS detection...
The harddisk (10000 GB / 9314 GiB) seems too small! (< 15 TB / 13 TiB)
The following partitions can't be recovered:
Linux filesys. data 9764602016 29297475743 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764658248 29297531975 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764658288 29297532015 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764759032 29297632759 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764759128 29297632855 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764911136 29297784863 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764911232 29297784959 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764911328 29297785055 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764911424 29297785151 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764911520 29297785247 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
SIGINT detected! TestDisk has been killed.The SIGINT was me in the end. I was not sure what to do and didn't want to screw anything up.
What can I do? I really need the data ASAP O_O
Offline
#4 2023-03-22 16:11:13
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 25,198
Re: Internal EXT4 Disk Drive fails after having booted into windows
If you don't have backups then you don't have data (or so the saying goes) disks can fail at any time.
That said smartctl -H is useless, if you want to post something post smartctl -a.
Offline
#5 2023-03-22 16:35:02
- Monero
- Member
- Registered: 2022-04-18
- Posts: 30
Re: Internal EXT4 Disk Drive fails after having booted into windows
I do have backups, but not daily. Either way, this is the result:
Self-test execution status: ( 249) Self-test routine in progress...
90% of test remaining.
Total time to complete Offline
data collection: ( 87) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 994) minutes.
SCT capabilities: (0x0035) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0
2 Throughput_Performance 0x0004 133 133 054 Old_age Offline - 92
3 Spin_Up_Time 0x0007 145 145 024 Pre-fail Always - 597 (Average 521)
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 551
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0
7 Seek_Error_Rate 0x000a 100 100 067 Old_age Always - 0
8 Seek_Time_Performance 0x0004 128 128 020 Old_age Offline - 18
9 Power_On_Hours 0x0012 098 098 000 Old_age Always - 17697
10 Spin_Retry_Count 0x0012 100 100 060 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 107
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 1177
193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 1177
194 Temperature_Celsius 0x0002 117 117 000 Old_age Always - 47 (Min/Max 17/65)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 17696 -
# 2 Extended offline Aborted by host 90% 17696 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.Any way to restore data? Is testdisk perhaps useful at all?
Offline
#6 2023-03-22 18:51:41
- tsweet64
- Member
- Registered: 2021-04-29
- Posts: 14
Re: Internal EXT4 Disk Drive fails after having booted into windows
Yeah, testdisk is probably worth a try, that's what I would personally try in this situation, but make sure you have a backup of the disk before writing any permanent changes to it in case something gets messed up further.
One more thing that might help, what's the output of `file /dev/sda1`? Nevermind, that doesn't provide useful information
Last edited by tsweet64 (2023-03-22 18:53:27)
Offline
#7 2023-03-22 19:12:56
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 25,198
Re: Internal EXT4 Disk Drive fails after having booted into windows
The drive as a drive looks fine, so yes I'd also opt for testdisk. Since "simply" running out of diskspace should not cause these kind of corruptions in the first place afaik, did you set up some custom ext flags? e.g. decrease the root safety provision?
Offline
#8 2023-03-23 21:57:34
- Monero
- Member
- Registered: 2022-04-18
- Posts: 30
Re: Internal EXT4 Disk Drive fails after having booted into windows
Ok so I don't wanna screw this up. On various pages I read that I should use EFI GPT, but in the testdisk docs it says to use the default, which I believe was Intel? https://www.cgsecurity.org/wiki/TestDis … le%20types
I just ran a long-scan using EFI GPT and testdisk gives me the option to fix some data now. However, the data is not a boot partition, so I am not sure if this is the right mode to begin with? I originally formatted it as EXT4 partition, so am I doing the right thing?
EDIT: Ok, so testdisk is really confusing to me: https://i.imgur.com/cFbs05v.png
Log file for testdisk is:
/dev/sda: LBA, HPA, LBA48, DCO support
/dev/sda: size 19532873728 sectors
/dev/sda: user_max 19532873728 sectors
/dev/sda: native_max 19532873728 sectors
Using locale 'en_US.UTF-8'.
Tue Mar 21 14:17:33 2023
Command line: TestDisk /log /dev/sda
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
OS: Linux, kernel 6.2.7-arch1-1 (#1 SMP PREEMPT_DYNAMIC Sat, 18 Mar 2023 01:06:36 +0000) x86_64
Compiler: GCC 12.2
ext2fs lib: 1.47.0, ntfs lib: libntfs-3g, reiserfs lib: none, ewf lib: none, curses lib: ncurses 6.3
Hard disk list
Disk /dev/sda - 10000 GB / 9314 GiB - CHS 1215865 255 63, sector size=512 - WDC WD101FZBX-00ATAA0, S/N:VCGZ8L7P, FW:01.01A01
Partition table type (auto): None
Disk /dev/sda - 10000 GB / 9314 GiB - WDC WD101FZBX-00ATAA0
Partition table type: EFI GPT
Analyse Disk /dev/sda - 10000 GB / 9314 GiB - CHS 1215865 255 63
check_part_gpt failed for partition
1 P MS Reserved 34 32767 32734 [Microsoft reserved partition]
Current partition structure:
No FAT, NTFS, ext2, JFS, Reiser, cramfs or XFS marker
1 P MS Reserved 34 32767 32734 [Microsoft reserved partition]
1 P MS Reserved 34 32767 32734 [Microsoft reserved partition]
search_part()
Disk /dev/sda - 10000 GB / 9314 GiB - CHS 1215865 255 63
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 32768 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 98304 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 163840 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 229376 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 294912 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 819200 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 884736 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 1605632 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 2654208 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 4096000 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 7962624 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 11239424 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 20480000 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 23887872 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 276714722 419954681057 419677966336
WBFS, 214 TB / 195 TiB
0 0000 0000 00 00 00 00 00 00 00 00
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 519959699 652911838 132952139
WBFS, 68 GB / 63 GiB
0 0000 0000 00 00 00 00 00 00 00 00
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 71663616 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 78675968 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 102400000 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 214990848 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
check_FAT: Bad number of sectors per cluster
check_FAT: Bad jump in FAT partition
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 512000000 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 550731776 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 644972544 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
check_FAT: Bad jump in FAT partition
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 6620483134 12774540029234749 12774533408751616 [CD{eWMWeC\&pe_oe_]
BeFS blocksize=2, 6540561 TB / 5948605 TiB
0 0000 0000 00 00 00 00 00 00 00 00
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 7228304118 8540139194 1311835077
FATX, 671 GB / 625 GiB
0 0000 0000 00 00 00 00 00 00 00 00
Linux filesys. data 9731320723 9735841572 4520849 [
%?S
d]
cramfs, 2314 MB / 2207 MiB
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Mon Mar 13 08:21:25 2023
Linux filesys. data 9764602016 29297475743 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Mon Mar 13 08:21:25 2023
Linux filesys. data 9764658248 29297531975 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Mon Mar 13 08:21:25 2023
Linux filesys. data 9764658288 29297532015 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Mon Jan 16 14:07:10 2023
Linux filesys. data 9764759032 29297632759 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Mon Jan 16 14:07:10 2023
Linux filesys. data 9764759128 29297632855 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Sat Jul 23 16:59:48 2022
Linux filesys. data 9764911136 29297784863 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Sat Jul 23 16:59:48 2022
Linux filesys. data 9764911232 29297784959 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Sat Jul 23 16:59:48 2022
Linux filesys. data 9764911328 29297785055 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Sat Jul 23 16:59:48 2022
Linux filesys. data 9764911424 29297785151 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Sat Jul 23 16:59:48 2022
Linux filesys. data 9764911520 29297785247 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 10694755062 11808789317 1114034256
FATX, 570 GB / 531 GiB
0 0000 0000 00 00 00 00 00 00 00 00
check_FAT: Bad number of sectors per cluster
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 12515043946 16060501428 3545457483
FATX, 1815 GB / 1690 GiB
0 0000 0000 00 00 00 00 00 00 00 00
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 1934917632 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 15732554884 19692167584 3959612701 [Ň]
SysV4, 2027 GB / 1888 GiB
0 0000 0000 00 00 00 00 00 00 00 00
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 16749527777 16749527776 0 [eBQ>]
SysV4, 0 B
0 0000 0000 00 00 00 00 00 00 00 00
Linux filesys. data 16954935524 16955731053 795529 [__{p`]
cramfs, 407 MB / 388 MiB
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 17002468214 225613581173 208611112960
WBFS, 106 TB / 97 TiB
0 0000 0000 00 00 00 00 00 00 00 00
Disk /dev/sda - 10000 GB / 9314 GiB - CHS 1215865 255 63
Check the harddisk size: HD jumper settings, BIOS detection...
The harddisk (10000 GB / 9314 GiB) seems too small! (< 15 TB / 13 TiB)
The following partitions can't be recovered:
Linux filesys. data 9764602016 29297475743 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764658248 29297531975 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764658288 29297532015 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764759032 29297632759 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764759128 29297632855 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764911136 29297784863 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764911232 29297784959 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764911328 29297785055 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764911424 29297785151 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764911520 29297785247 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
SIGINT detected! TestDisk has been killed.
/dev/sda: LBA, HPA, LBA48, DCO support
/dev/sda: size 19532873728 sectors
/dev/sda: user_max 19532873728 sectors
/dev/sda: native_max 19532873728 sectors
Using locale 'en_US.UTF-8'.
Wed Mar 22 16:51:07 2023
Command line: TestDisk /log /dev/sda
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
OS: Linux, kernel 6.2.7-arch1-1 (#1 SMP PREEMPT_DYNAMIC Sat, 18 Mar 2023 01:06:36 +0000) x86_64
Compiler: GCC 12.2
ext2fs lib: 1.47.0, ntfs lib: libntfs-3g, reiserfs lib: none, ewf lib: none, curses lib: ncurses 6.3
Hard disk list
Disk /dev/sda - 10000 GB / 9314 GiB - CHS 1215865 255 63, sector size=512 - WDC WD101FZBX-00ATAA0, S/N:VCGZ8L7P, FW:01.01A01
Partition table type (auto): None
Disk /dev/sda - 10000 GB / 9314 GiB - WDC WD101FZBX-00ATAA0
Partition table type: EFI GPT
Analyse Disk /dev/sda - 10000 GB / 9314 GiB - CHS 1215865 255 63
check_part_gpt failed for partition
1 P MS Reserved 34 32767 32734 [Microsoft reserved partition]
Current partition structure:
No FAT, NTFS, ext2, JFS, Reiser, cramfs or XFS marker
1 P MS Reserved 34 32767 32734 [Microsoft reserved partition]
1 P MS Reserved 34 32767 32734 [Microsoft reserved partition]
search_part()
Disk /dev/sda - 10000 GB / 9314 GiB - CHS 1215865 255 63
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 32768 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 98304 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 163840 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 229376 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 294912 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 819200 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 884736 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 1605632 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 2654208 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 4096000 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 7962624 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 11239424 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 20480000 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 23887872 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 276714722 419954681057 419677966336
WBFS, 214 TB / 195 TiB
0 0000 0000 00 00 00 00 00 00 00 00
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 519959699 652911838 132952139
WBFS, 68 GB / 63 GiB
0 0000 0000 00 00 00 00 00 00 00 00
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 71663616 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 78675968 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 102400000 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 214990848 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
check_FAT: Bad number of sectors per cluster
check_FAT: Bad jump in FAT partition
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 512000000 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 550731776 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 644972544 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
check_FAT: Bad jump in FAT partition
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 6620483134 12774540029234749 12774533408751616 [CD{eWMWeC\&pe_oe_]
BeFS blocksize=2, 6540561 TB / 5948605 TiB
0 0000 0000 00 00 00 00 00 00 00 00
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 7228304118 8540139194 1311835077
FATX, 671 GB / 625 GiB
0 0000 0000 00 00 00 00 00 00 00 00
Linux filesys. data 9731320723 9735841572 4520849 [
%?S
d]
cramfs, 2314 MB / 2207 MiB
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Mon Mar 13 08:21:25 2023
Linux filesys. data 9764602016 29297475743 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Mon Mar 13 08:21:25 2023
Linux filesys. data 9764658248 29297531975 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Mon Mar 13 08:21:25 2023
Linux filesys. data 9764658288 29297532015 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Mon Jan 16 14:07:10 2023
Linux filesys. data 9764759032 29297632759 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Mon Jan 16 14:07:10 2023
Linux filesys. data 9764759128 29297632855 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Sat Jul 23 16:59:48 2022
Linux filesys. data 9764911136 29297784863 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Sat Jul 23 16:59:48 2022
Linux filesys. data 9764911232 29297784959 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Sat Jul 23 16:59:48 2022
Linux filesys. data 9764911328 29297785055 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Sat Jul 23 16:59:48 2022
Linux filesys. data 9764911424 29297785151 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
Filesystem created: Sat Feb 20 16:10:20 2021
Last mount time: Sat Jul 23 16:59:48 2022
Linux filesys. data 9764911520 29297785247 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
This partition ends after the disk limits.
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 10694755062 11808789317 1114034256
FATX, 570 GB / 531 GiB
0 0000 0000 00 00 00 00 00 00 00 00
check_FAT: Bad number of sectors per cluster
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 12515043946 16060501428 3545457483
FATX, 1815 GB / 1690 GiB
0 0000 0000 00 00 00 00 00 00 00 00
recover_EXT2: part_offset problem
recover_EXT2: "e2fsck -b 1934917632 -B 4096 device" may be needed
Filesystem created: Sat Feb 20 16:10:20 2021
Linux filesys. data 0 19532873727 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 10000 GB / 9314 GiB
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 15732554884 19692167584 3959612701 [Ň]
SysV4, 2027 GB / 1888 GiB
0 0000 0000 00 00 00 00 00 00 00 00
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 16749527777 16749527776 0 [eBQ>]
SysV4, 0 B
0 0000 0000 00 00 00 00 00 00 00 00
Linux filesys. data 16954935524 16955731053 795529 [__{p`]
cramfs, 407 MB / 388 MiB
0 0000 0000 00 00 00 00 00 00 00 00
Unknown 17002468214 225613581173 208611112960
WBFS, 106 TB / 97 TiB
0 0000 0000 00 00 00 00 00 00 00 00
Disk /dev/sda - 10000 GB / 9314 GiB - CHS 1215865 255 63
Check the harddisk size: HD jumper settings, BIOS detection...
The harddisk (10000 GB / 9314 GiB) seems too small! (< 15 TB / 13 TiB)
The following partitions can't be recovered:
Linux filesys. data 9764602016 29297475743 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764658248 29297531975 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764658288 29297532015 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764759032 29297632759 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764759128 29297632855 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764911136 29297784863 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764911232 29297784959 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764911328 29297785055 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764911424 29297785151 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
Linux filesys. data 9764911520 29297785247 19532873728
ext4 blocksize=4096 Large_file Sparse_SB Recover, 10000 GB / 9314 GiB
interface_write()
1 P Linux filesys. data 9731320723 9735841572 4520850 [
%?S
d]
2 P Linux filesys. data 16954935524 16955731053 795530 [__{p`]
interface_write()
1 P Linux filesys. data 9731320723 9735841572 4520850 [
%?S
d]
2 P Linux filesys. data 16954935524 16955731053 795530 [__{p`]
interface_write()
1 P Linux filesys. data 9731320723 9735841572 4520850 [
%?S
d]
2 P Linux filesys. data 16954935524 16955731053 795530 [__{p`]Last edited by Monero (2023-03-23 22:16:04)
Offline