"Disks" tells me the kind of information that tells me it needs a chkdsk, but testdisk, something I used often to save my data when it looked grim, tells me the partition, which takes the whole internal drive, but is under an extended partition for some reason (I wouldn't have done this, I left it as ntfs even if it is a drive I only got for data about 5 years ago).
The computer's BIOS/UEFI sees the drive, so it doesn't look to me like it's broken. I've been using live sessions for extended periods of time and I think my usb 3.0 extension (only have 2 in the back of the desktop, so I bought an additional seperate power source 4 port extension, so I have 5 in total that are 3.0/3.1). But when testdisk tells me something...I believe it. I really can't lose what's on there, at least 3/4 of it, I burned some of that drive's content to a BD-R 100gb but back then that thing didn't contain my "notes" files, where all my logins and everything are. I thankfully had made a copy of that file on a usb drive on dec 30th, so thankfully all of my pw's are up to date...now I only have to worry about whether the live session, which doesn't boot correctly (I checked the usb drive on my s/o's win10 laptop so I could verify its integrity and it is fine), but a live session eventually always has trouble, and this one I had running since late november until yesterday...I might be pushing it...I know, I should just install the damn thing.
Sometimes the usb 256gb stick boots so badly it doesn't see the network adapters and incorrectly detects my sound adapters and doesn't give me permissions to change my time zone or access some other drive/partition's contents. Weird, 18.04.5 didn't do that, but then again 20.04 was a lot more stable on a live session since I started using it in august.
I have Hiren's Boot 15.2 so I will be looking to do a chkdsk and everything else to clean up the ntfs drive....if it sees it, the testdisk telling me "D" for the partitions..well, there's really only one but like I said it sees 2 because there's an extended partition of 1tb under the main 1tb partition for some reason.
Now is it possible it is only an issue with the usb ports extension (I tried 3 different ports out of 4 and it doesn't change anything, live sessions start up fine once out of 4).
This isn't a particularly old desktop, since I built it to last, amd3+ FX-9350 4.4ghz octocore, 16gb 2133mhz Corsair ram....the motherboard might be a bit overwhelmed though, with the large cooling tower and everything that's added up to it, every diagnostics I ran tells me all is running smooth though. Just can't mount a disk that suddenly refuses to when I start up a live session that always did, and I decided to look at the boot sequence by pressing escape and I see how it has a lot of issues with sdb5 (it really should be sdb1 like I said, don't know why it sees it that way but that never mattered before). Stuff I've seen before with drives that needed a windows chkdsk, nothing ntfs utils for linux will fix.
Is this something that could be fixed easily if I just installed ubuntu mate 20.04 to an internal drive finally or I should expect the same result? I'll keep you updated/edit my post after I boot with Hiren's Boot and look if I can fix it...if it doesn't see it, then testdisk is right, but i can still save the data since obviously nothing was written there since I can't access it, testdisk sees the files just fine and I could copy them to some other drive if I wanted, I don't know if I could just resuscitate it by changing its status in testdisk, I did this before, but I never had a drive act this way, usually when something is dead on it like the power, the computer itself doesn't see it.
I know I can fetch out the boot sequence for you guys to check it out, but I'm pretty busy with other things right now, but if it would help to show you what's suddenly happening when I boot from the usb stick to a live session with this sdb5 1tb partition/drive, what I've seen in the boot sequence, please go ahead. I'll check this thread later tonight. I'm frustrated enough right now that I'll just be watching TV on vlc through the desktop, spent the whole morning trying to figure what was wrong all of a sudden.
Hopefully the whole world hasn't been put on a curfew around you where you are...