***Solution is noted at the end of post*** (I put this in the wrong forum, thank you for your patience and understanding)
I had just accessed this former Windows 7 NTFS 2tb hdd drive, came back later to find.
I looked for the mount point /media/unity/MAINDRIVE to find it was missing, along with HP-Recovery (which I think that one was never mounted anyway) *this is not a dual boot system. here mount shown missing via lsblk -f ..
[CODEsdb
├─sdb1
│ ntfs SYSTEM E0980FA0980F7476 74.8M 25% /media/unity/SYSTEM
├─sdb2
│ ntfs MAIN DRIVE
│ 0E683B55683B3AB3
├─sdb3
│
├─sdb4
│ ntfs HP_RECOVERY
│ 9C50A5F050A5D0F6
└─sdb5
ntfs New Volume
DA129EB3129E93DB 97.6G 0% /media/unity/New Volume
CODE]
I created another mount point at /media/unity/MAINDRIVE and edited fstab (even though in times past, it just mounted the drive) and tried to mount it and got error.
[CODE
Error opening read-only '/dev/sdb2': Permission denied
Failed to mount '/dev/sdb2': Permission denied
Please check '/dev/sdb2' and the ntfs-3g binary permissions,
and the mounting user ID. More explanation is provided at
https://github.com/tuxera/ntfs-3g/wiki/NTFS-3G-FAQ
CODE]
This is all of the sudden unexpected behavior, and my first thought was a wire loosened up on the HDD. However when I look into the hardware devices, it sees the drive. Is anyone familiar with this behavior? The searches I have done online are far off in similarities, leaving me without sound clues, and making me bunny trail. As always your tutor-age is appreciated. (Trying to use code brackets to keep the read outs clean and readable, but do not know if I have done it correctly?)
EDITed to add info....
[CODE sudo fdisk -l /dev/sdb
Disk /dev/sdb: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Hitachi HDS72302
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x52a2d054
Device Boot Start End Sectors SizeIdType
/dev/sdb1 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sdb2 206911 3678771199 3678564289 1.7T 7 HPFS/NTFS/exFAT
/dev/sdb3 3678771200 3883571199 204800000 97.7G f W95 Ext'd (LBA)
/dev/sdb4 * 3883571200 3907027119 23455920 11.2G 7 HPFS/NTFS/exFAT
/dev/sdb5 3678773248 3883571199 204797952 97.7G 7 HPFS/NTFS/exFAT
Partition table entries are not in disk order.
CODE]
I got a clue from gParted when it said use Windows chkdsk, which led me to NTFS-3G, which was already installed on Kubuntu 22.04.
sudo ntfsfix /dev/sdb2 (was the code that fixed it)
sudo apt-get install ntfs-3g (if you need to install it)
my results, the important one it fixed, the other one has bad sectors.
[CODE] sudo ntfsfix /dev/sdb2
Mounting volume... $MFTMirr does not match $MFT (record 3).
FAILED
Attempting to correct errors...
Processing $MFT and $MFTMirr...
Reading $MFT... OK
Reading $MFTMirr... OK
Comparing $MFTMirr to $MFT... FAILED
Correcting differences in $MFTMirr record 3...OK
Processing of $MFT and $MFTMirr completed successfully.
Setting required flags on partition... OK
Going to empty the journal ($LogFile)... OK
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
NTFS partition /dev/sdb2 was processed successfully.
sudo ntfsfix /dev/sdb3
[sudo] password for unity:
Mounting volume... NTFS signature is missing.
FAILED
Attempting to correct errors... NTFS signature is missing.
FAILED
Failed to startup volume: Invalid argument
NTFS signature is missing.
Trying the alternate boot sector
Unrecoverable error
Volume is corrupt. You should run chkdsk.
[CODE]
I had just accessed this former Windows 7 NTFS 2tb hdd drive, came back later to find.
I looked for the mount point /media/unity/MAINDRIVE to find it was missing, along with HP-Recovery (which I think that one was never mounted anyway) *this is not a dual boot system. here mount shown missing via lsblk -f ..
[CODEsdb
├─sdb1
│ ntfs SYSTEM E0980FA0980F7476 74.8M 25% /media/unity/SYSTEM
├─sdb2
│ ntfs MAIN DRIVE
│ 0E683B55683B3AB3
├─sdb3
│
├─sdb4
│ ntfs HP_RECOVERY
│ 9C50A5F050A5D0F6
└─sdb5
ntfs New Volume
DA129EB3129E93DB 97.6G 0% /media/unity/New Volume
CODE]
I created another mount point at /media/unity/MAINDRIVE and edited fstab (even though in times past, it just mounted the drive) and tried to mount it and got error.
[CODE
Error opening read-only '/dev/sdb2': Permission denied
Failed to mount '/dev/sdb2': Permission denied
Please check '/dev/sdb2' and the ntfs-3g binary permissions,
and the mounting user ID. More explanation is provided at
https://github.com/tuxera/ntfs-3g/wiki/NTFS-3G-FAQ
CODE]
This is all of the sudden unexpected behavior, and my first thought was a wire loosened up on the HDD. However when I look into the hardware devices, it sees the drive. Is anyone familiar with this behavior? The searches I have done online are far off in similarities, leaving me without sound clues, and making me bunny trail. As always your tutor-age is appreciated. (Trying to use code brackets to keep the read outs clean and readable, but do not know if I have done it correctly?)
EDITed to add info....
[CODE sudo fdisk -l /dev/sdb
Disk /dev/sdb: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Hitachi HDS72302
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x52a2d054
Device Boot Start End Sectors SizeIdType
/dev/sdb1 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sdb2 206911 3678771199 3678564289 1.7T 7 HPFS/NTFS/exFAT
/dev/sdb3 3678771200 3883571199 204800000 97.7G f W95 Ext'd (LBA)
/dev/sdb4 * 3883571200 3907027119 23455920 11.2G 7 HPFS/NTFS/exFAT
/dev/sdb5 3678773248 3883571199 204797952 97.7G 7 HPFS/NTFS/exFAT
Partition table entries are not in disk order.
CODE]
I got a clue from gParted when it said use Windows chkdsk, which led me to NTFS-3G, which was already installed on Kubuntu 22.04.
sudo ntfsfix /dev/sdb2 (was the code that fixed it)
sudo apt-get install ntfs-3g (if you need to install it)
my results, the important one it fixed, the other one has bad sectors.
[CODE] sudo ntfsfix /dev/sdb2
Mounting volume... $MFTMirr does not match $MFT (record 3).
FAILED
Attempting to correct errors...
Processing $MFT and $MFTMirr...
Reading $MFT... OK
Reading $MFTMirr... OK
Comparing $MFTMirr to $MFT... FAILED
Correcting differences in $MFTMirr record 3...OK
Processing of $MFT and $MFTMirr completed successfully.
Setting required flags on partition... OK
Going to empty the journal ($LogFile)... OK
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
NTFS partition /dev/sdb2 was processed successfully.
sudo ntfsfix /dev/sdb3
[sudo] password for unity:
Mounting volume... NTFS signature is missing.
FAILED
Attempting to correct errors... NTFS signature is missing.
FAILED
Failed to startup volume: Invalid argument
NTFS signature is missing.
Trying the alternate boot sector
Unrecoverable error
Volume is corrupt. You should run chkdsk.
[CODE]