Occasional long delays on brand new SSD

Timmi · 16 Jul 2018

OK, do tell me how reconfiguring my computer the way you want it, helps resolve the issue at hand?

And I am not moving \users. I've been using a separate Data partition for data for decades now. I don't want to be slave to some \users structure for my data. I want the data as easily accessible from Windoze and Linux. Not in some Windows' users-sub-sub directory called documents videos etc.
Data gets dumped onto HDD as a backup, and occasionally HDD gets backed up onto an external hard drive.
I also want the freedom to remove the HDD, to either use it in one of my other computers, or put another Data HDD in it's place.
The system has to be able to run independently, should a component fail or be removed.
Your way, if I change my Data drive I have to map everything all over again - I'm not signing up for an eternal system-configuring-as-a-hobby here!

With space on the SSD at a premium, I've decided to put Linux onto my data drives, and use [F12] to select which drive to boot from. This makes it even simpler, and gets me further towards my goal of KISS.
Besides, when the SSD finally fails, I'll be able to get one 4 times the capacity at half the price. Why should I organise everything as if the SSD is the more permanent component? DATA is what's important - not the OS and what's holding it.

FAT32: I don't care about file size. It's never been a problem until now, so why should I care?
And what are these other "limitations" you speak of? Do you even know of any? Why do you think NTFS is "safer"? Will NTFS resolve my issue? AFAIK the NTFS specification isn't even shared by MS - I learned that it's proprietary and that everyone else's implementation of it is best-guess. To me, that doesn't sound much better than FAT.
Also, I've had instances where Linux cannot read NTFS, because the NTFS partition required a password to boot when booting Windows. So I do not feel secure that it will work. I suppose I can test it - put Mint 19 onto the HDD, boot with that, and see if it can access the SSD's data. But even then, WILL NTFS RESOLVE THE SSD LAG ISSUE? I haven't seen that question answered.

And I'm not buying a new laptop just to have UEFI which I do NOT need. Besides, you shouldn't even like UEFI yourself, as some of it's code resides on a FAT partition!

Megahertz07 · 16 Jul 2018

I don't know if NTFS will resolve your issue.
What I know is that your data will be much more secure on NTFS than on a Fat32.
NTFS - Wikipedia
File Allocation Table - Wikipedia
If you've had instances where Linux cannot read NTFS, because the NTFS partition required a password to boot when booting Windows, it could be that it had the disk encrypted.
Never said to you to buy a new laptop. Yes, UEFI - GPT uses Fat32 to hold the boot loaders because it's universal to all OS.
GUID Partition Table - Wikipedia

I gave you some suggestions that in my opinion will make your system work better and safer.
You seem to know what you want and you're aggressive on your answers. Good luck.

Timmi · 17 Jul 2018

Megahertz07 said:

- You shouldn't have FAT32 for Data. It has limitations on file size and isn't robust as NTFS. And Linux can read / write to NTFS.

WHY not FAT? it gets backed up anyways, to the other drive. that's what the other one is there for.

There are 2 reasons why I will not move \users to the HDD:
1.first, I need to be able to swap either drive! (so that's a hard limit)
2.second, I want the performance of the swap file(s) being on the SSD. When I run CAD software and it swaps something to disk, I prefer it to be closer to RAM speeds than to HDD speeds - the benefits are immense.

And I really don't care about file size. 4GB is big enough. The largest files I have are a few videos, the largest of which are under 2GB in size.

Will changing FAT to NTFS resolve the issue? Or are you just giving advice on how you prefer to have your computers configured? (because that is what it sounds like, so it begs the question).

If it will resolve it for sure, I'll do it. If it's just that you don't like my config, that's not a solution.

Timmi · 18 Jul 2018

Megahertz07 said:

I don't know if NTFS will resolve your issue.
What I know is that your data will be much more secure on NTFS than on a Fat32.

If you've had instances where Linux cannot read NTFS, because the NTFS partition required a password to boot when booting Windows, it could be that it had the disk encrypted.

Never said to you to buy a new laptop. Yes, UEFI - GPT uses Fat32 to hold the boot loaders because it's universal to all OS.

I gave you some suggestions that in my opinion will make your system work better and safer.
You seem to know what you want and you're aggressive on your answers. Good luck.

Last I heard, FAT manages 2 copies and therefore can be rebuilt. So it's not that dismally-bad.
And I never encrypt my partitions... I'm too paranoid of something happening and then not being able to run data-recovery on it should everything go to hell.

If I seem "aggressive" to you, it's simply because I'm exasperated with you!
You kept on making it a point to mention over and over about how "old" my computer is and how it's not UEFI... you keep on campaigning for "your" preferred configurstion, even if you are admitting you're not even offering a solution in the end. ...and now you complain? This behavior is nothing other than veiled arrogance.
You went on over and over about uefi and guid - it's not even pertinent to this thread! The problem presented here is in a BIOS system. If you're not trying to bash my hardware or convince me to buy new hardware, why do you keep on repeatedly outlining the differences with yours?

This isn't supposed to be a my-harware-is-better-than-yours-snobfest!
It's supposed to be about people being impartial, and helping other people, with useful advice, and not derailing threads into other peripheral and non-pertinent topics.

You have hi-jacked this thread, offering pages of lectures on how you want everyone to do as you do, without even considering for a moment that everyone's needs aren't the same as yours.
You haven't got a clue (!) about the solution, you're just being a militant for your configuration.
Except that now, newcomers to the thread have an extra page of information to sift through that isn't even relevant, all because of you telling me how old my hardware is and pointing out it's not uefi and how I should move \users to hdd.

Please do me a favor, don't ever answer any of my threads in the future.
That should free up some time to get to the solution faster.