Can Linux have difficulty with a 2TB drive?
 

The title should include a problem with Grub

The problem is that it takes 75 seconds to boot on a fast (3.9GHz) desktop with 16Gb RAM.

When booting, fsck checks the disk and blocks the keyboard from interrupting with Ctrl-C. When it finishes the login screen appears normally.

This desktop Linux Mint 19.3 is installed on a new 2TB 7200 rpm Seagate which I know is slow compared to an SSD, but not this slow.

This attached report lists the following problem:

"File descriptor 63 (pipe:[59749]) leaked on lvs invocation. Parent PID 2099: /bin/bash"

But I have no clue what it means.

Using boot-repair's report feature, I attached the report as a better source of info.

* In Windows, CrystalInfo reports that all three disks are functioning within their parameters and the temps are between 29C - 38C. normal.

* Windows disk health check reports that all is well.

* fsck booted from live USB reports that all drive systems are well.

* gparted also reports that all drives are well.

Frankly, a minute and 15 seconds with a standard HDD sounds like a fairly reasonable boot time to me.

Agreed. I’d be happy if my desktop booted that quickly. Mine takes about two minutes, but the processor is slower, and it only has 8GB of RAM.

" fsck checks the disk and blocks the keyboard from interrupting with Ctrl-C"

Not sure this should be checking each boot. I'd suspect that some issue or setting can be changed.

Smart tools may be a place to look for drive health.

Wonder why bash is running a start up?

Thanks, and I know that a SDD would solve the speed problem, but, my concern is the leakage. Another reason being that when using the live USB, it loads fast 15 - 20 seconds, and all the drives are connected and accessible. When used the live USB boot-repair, here was no "leakage" reported. In addition, I've been trying to resolve this issue for the past week, and installed LM19.3 several times. After installation, the first boot is fast, and after that it slows down

The drive health was checked by several different apps in both Windows and Linux.

Normally, LM offers fsck of the system drive after every 20 boots. Based on experience, I am sure that checking every boot is not normal. I know that something is wrong, and that is he focus of this post. I want to find out what "File descriptor 63 (pipe:[59749]) leaked on lvs invocation. Parent PID 2099: /bin/bash" means. and does this tie into the drive size. There are three drives involved.

this is lvs: https://man7.org/linux/man-pages/man8/lvs.8.html
It is not a problem with the drive itself, not a problem with the size or capacity, but [probably] the created logical volumes and/or filesystems. Also it can be a simple issue with the implementation of that piece of software (which reports this problem). But it is a general error message and I have no any idea where is it coming from. Probably you can find some additional details in /var/log or dmesg. Probably the installation of Mint went wrong.

That's not a horrible boot time but a bit slower than I would expect. My desktop runs at 3.2GHz with 8GB of RAM and a garden-variety SATA HDD. Boot times for Leap (according to /var/log/boot.msgs) run about 26s plus the time it takes to mount the additional drives, start Xorg, etc. Total time: never more than ~40s. On an old Slackware system I have running (1GHz, 256MB RAM, SCSI HDD) the system is up and ready for use in ~30s (no X). I can't recall seeing boot times >1m since the '486 or early Pentium days.

Is the fsck that you mentioned the standard check that takes place on the root filesystem during boot? That normally only takes a few seconds. What other services are starting? Do you have a largish filesystem set to do fscks at frequent intervals (i.e., after every "N" mounts; you can set that mount-count with tune2fs).

This has nothing to do Linux but here is a great example that aggravates me to no end every morning I fire up my work laptop:

Dell 7700 (?) 17" laptop
i7 quad core at 2.7ghz
16GB ram
Spinning HDD

From power on to a USABLE desktop takes 10-15 minutes. the HDD activity light stays on solid for closer to 20 minutes.

Windows 10 Enterprise on a government network with all of the related security tweaks and desktop management software. Once running, it's fine but I have to start the logon process early or I'll be late to work...

Consider yourself lucky at 75 seconds...

The missus's Win7 laptop has comparable boot time. (It's one major thing I really don't miss about Windows.) I try to remind her to turn it on before making the morning coffee so, maybe, it'll be ready by the time the coffee's ready.

It's crazy because although I don't know the generation of CPU in my laptop, my desktop also has an i7 7700) albeit it is all SSD, and my desktop boots in about 10 seconds. Corporate/business Windows 10 set up vice "Home" set up though so that probably makes a huge difference.

I had two 120GB SSD's, one for Windows 10 and one for Linux Mint and it also booted very fast. But buying the 2TB drive, forced me to remove the Linux SSD and install it in my laptop where the space was needed. The 2TB drive was a replacement of an 8 year old 500GB Seagate which was developing issues of reliability. Since I only had the budget for one drive, I had no choice.

Drive size seen in Linux has to do with the file system used and 2TB drives should be no issue at all. I can't speak to the nuances of each file system because I have only used (historically) Ext2,3 and 4.

No kidding. Does it automatically check for updates and install them on boot up? I've been told that windows does that now whether you like it or not. No wonder the default on windows is to hibernate and not turn off.

I have a 12TB mechanical disk array on my file server - I guess boot time is not an issue as it is on 24/7, but size is not an issue (insert joke here).

When I moved some of my Linux desktops from mechanical to SSD, we are talking 2 mins changing to under 30 seconds. My main desktop went from a minute to 10 seconds power to desktop. I built a living room PC for my sister with an M.2 drive which is power to desktop in under 10 (jealous, wish I did that on mine).

Just giving my anecdotal experience with Linux boot times. And to add that for every single machine that I converted from Windows to Linux, the time was improved massively. We had a Windows 10 machine that took about 10 minutes before it was operational (an expensive laptop) - put Debian on it and it was under a minute on a mechanical drive. Boot times are so variable but at the same time, generally easy to improve.