Hi, I'm using Debian Bookworm and all things have been going well until recently.
One of my drives recently takes a long time to mount. It's a hdd 2.5" 4TB drive partitioned as GPT and formatted as NTFS since it shares the files in it with Windows.
Using <sytemd-analzye blame> shows the process takes about 23 seconds to mount that particular drive. This brings out a noticeable delay whereas Debian was booting while mounting the same drive very fast just few days ago.
In the beginning, I used Gparted to unmount and check it, and it showed errors about cluster errors and asked me to boot into windows and run chkdsk and boot twice thing.
I then copied the directories into another drive, used gparted to delete the whole drive and repartition and reformatted again, and copied back my backup into the drive.
Now Gparted shows no errors, but it still takes about 23 - 25 seconds trying to mount it. It mounts successfully, but I wonder why it's not mounting immediately. I have another 2TB hdd drive which is mounted very fast.
The thing is I wonder why the sudden delay now, whereas Debian booted very fast until this incident?
(The only thing I remember doing when this happened, was, I was installing bluetooth, bluez and blueman packages and while following the Debian wiki, I followed up to the logoff and login to see the bluetooth pop-up dialogue, and at the same time, I torrent was downloading to that drive.)
Or is my drive dying down? It's a Seagate drive removed from the Backup Plus external drive enclosure. (My other 2TB mentioned above was also removed from its Backup Plus Slim enclosure. The Seagate's Backup Plus external series use the same SATA interface as the standard 2.5" internal drives.)
EDIT: The UUID is correct in the fstab.
Thank you for any information.
One of my drives recently takes a long time to mount. It's a hdd 2.5" 4TB drive partitioned as GPT and formatted as NTFS since it shares the files in it with Windows.
Using <sytemd-analzye blame> shows the process takes about 23 seconds to mount that particular drive. This brings out a noticeable delay whereas Debian was booting while mounting the same drive very fast just few days ago.
In the beginning, I used Gparted to unmount and check it, and it showed errors about cluster errors and asked me to boot into windows and run chkdsk and boot twice thing.
I then copied the directories into another drive, used gparted to delete the whole drive and repartition and reformatted again, and copied back my backup into the drive.
Now Gparted shows no errors, but it still takes about 23 - 25 seconds trying to mount it. It mounts successfully, but I wonder why it's not mounting immediately. I have another 2TB hdd drive which is mounted very fast.
The thing is I wonder why the sudden delay now, whereas Debian booted very fast until this incident?
(The only thing I remember doing when this happened, was, I was installing bluetooth, bluez and blueman packages and while following the Debian wiki, I followed up to the logoff and login to see the bluetooth pop-up dialogue, and at the same time, I torrent was downloading to that drive.)
Or is my drive dying down? It's a Seagate drive removed from the Backup Plus external drive enclosure. (My other 2TB mentioned above was also removed from its Backup Plus Slim enclosure. The Seagate's Backup Plus external series use the same SATA interface as the standard 2.5" internal drives.)
EDIT: The UUID is correct in the fstab.
Thank you for any information.
Statistics: Posted by M22 — 2024-02-10 02:41 — Replies 1 — Views 38