EXT4FS Disk cannot be mounted again because of the broken filesystem #8083
Comments
|
More dmesg log when try again: |
|
What's wrong with the kernel about: |
ghost
mentioned this issue
|
I have this issue as well. Any resolution? |
|
I also have this issue. Please advise |
|
|
|
+1 (I realize there is a workaround, but hoping for a fix to save future keystrokes): strangely, it appears a mountpoint was still created for the "failed to mount": |
|
Met same issue, and managed to mount the drive by following @mjanson |
|
Just to add an error that happened to me, you have to do what @mjanson says, in my case even doing that it still didn't work, it mounted the disk but when I wanted to access the contents it threw "permission denied". To solve this just pass the ownership of the contents to your user. Important: using the command can take a long period of time depending on the capacity of the hard disk, in my case a 300GB disk connected as removable storage took about 6 minutes. So make sure you have the time at hand first. sudo chown -R YOURUSER DRIVEe.g. sudo chown -R enzod PHYSICALDRIVE2p1 |
|
What worked for me was to add I also used |
Version
Microsoft Windows [Version 10.0.22557.1]
WSL Version
Kernel Version
5.10.93.2
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps
wsl --mount \.\PHYSICALDRIVE2
Expected Behavior
mount successfully
Actual Behavior
The disk was attached but failed to mount: Invalid argument.
For more details, run 'dmesg' inside WSL2.
To detach the disk, run 'wsl.exe --unmount \.\PHYSICALDRIVE2'.
dmesg log:
[ 31.411807] scsi 0:0:0:3: Direct-Access WDC WD40PURX-78AKYY0 80.0 PQ: 0 ANSI: 0
[ 31.412350] sd 0:0:0:3: Attached scsi generic sg3 type 0
[ 31.412469] sd 0:0:0:3: [sdd] Very big device. Trying to use READ CAPACITY(16).
[ 31.413306] sd 0:0:0:3: [sdd] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[ 31.413598] sd 0:0:0:3: [sdd] 4096-byte physical blocks
[ 31.414485] sd 0:0:0:3: [sdd] Write Protect is off
[ 31.414741] sd 0:0:0:3: [sdd] Mode Sense: 0f 00 00 00
[ 31.416201] sd 0:0:0:3: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 31.416839] sd 0:0:0:3: [sdd] Very big device. Trying to use READ CAPACITY(16).
[ 31.448636] sdd: sdd1
[ 31.449078] sd 0:0:0:3: [sdd] Very big device. Trying to use READ CAPACITY(16).
[ 31.451711] sd 0:0:0:3: [sdd] Attached SCSI disk
[ 31.469402] WSL2: Detected (null) filesystem for device: /dev/sdd
[ 31.469733] ERROR: Mount:2716: mount(/dev/sdd, /share/PHYSICALDRIVE2, (null), 0x0, ) failed
[ 31.469734] 22
fdisk -llog:The primary GPT table is corrupt, but the backup appears OK, so that will be used.
Disk /dev/sdd: 3.65 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: WD40PURX-78AKYY0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 2DA8DB1A-0A96-4ACC-A73F-DD27DBB70D4D
Device Start End Sectors Size Type
/dev/sdd1 34 32767 32734 16M Microsoft reserved
Partition 1 does not start on physical sector boundary.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: