Am Montag, 20. Januar 2025, 17:39:19 CET schrieb Adam Weremczuk:
> I'm unable to mount the disk in Windows without formatting to assigne a
> letter, so can't do "chkdsk ... C:"
No, you do NOT have to mount the drive. Just boot windows into rescue mode and 
then got to the DOSshell and do chckdsk on the correct volume (C: , D: , F: 
whatever).

> Windows just reports something that looks like two blank partitions,
> both with 2TB of unallocated space.
> Please see a screenshot attached to my message from about 4.5 hrs ago
> showing that.
> 

> The system/loadout I'm using is not "live" but installed on sda (local
> 1TB SSD).
> I've tried mounting the troublesome 4TB NVMe on 3 different systems already.
> I think it has more to do with a specific sequence of commands or a tool
> allowing me to access that (apparently) inaccessible data.
Just "mount /dev/nvme0n1p3 /my_mountpoint" should work. 

If it can not be mounted, then your filesystem is corrupt. Exfat is not well to 
fix with linux, you should do it in windows. I suggest, not to use an installed 
windows, as windows (boah, crap!) will automatically want to mount any newly 
seen partition, which is bad for fixing using chkdsk.

So my suggestion, use a rescue-windows, must not be based on Win10, even an 
old WinXP lifefile will work for that.

The other way is, to boot an installed windows into rescue-mode and then you 
can fix the drive with chkdsk, too.

Hans
 

> 
> Any ideas, even risky ones, are welcome.
> I have little to lose at this point.
> 
> On 20/01/2025 16:29, Hans wrote:
> > Am Montag, 20. Januar 2025, 17:15:40 CET schrieb Adam Weremczuk:
> > Try "chkdsk /F /R C:" in windows, this should help.
> > 
> > If you do not own a windows computer, then you can use any windows-live-cd
> > for that, like Falcon4, HirensBootCD or UBCD4Win.
> > 
> > Hans
> > 
> >> Also:
> >> 
> >> sudo mount -t exfat /dev/nvme0n1 /mnt/nvme0n1
> >> mount: /mnt/nvme0n1: wrong fs type, bad option, bad superblock on
> >> /dev/nvme0n1, missing codepage or helper program, or other error.
> >> 
> >> makes no difference.




Reply via email to