[O/S] [SOLVED] HDD suddenly takes long time to mount

[M22]

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.

[fabien]

Hello,

The first thing to do when such things happen is to check the system logs.
As root (unless your user is in the systemd-journal group):

Code: Select all

#> journalctl --no-hostname -b

This will show you the latest boot log. You should be able to distinguish the cause and know if it is related to your disk. I would expect a gap in the timestamp where the main error is shown.
Please report the relevant part. If you can't find it, please post the entire log (/tmp/mybootlog.gz) as an attachment:

Code: Select all

#> journalctl --no-hostname -b | gzip >/tmp/mybootlog.gz

[M22]

Hi, here is the output of the above command :

(I am unable to identify what the reason is, though.)

Code: Select all

Feb 10 11:14:36 systemd[1070]: Queued start job for default target default.target.
Feb 10 11:14:36 systemd[1070]: Created slice app.slice - User Application Slice.
Feb 10 11:14:36 systemd[1070]: Created slice session.slice - User Core Session Slice.
Feb 10 11:14:36 systemd[1070]: Reached target paths.target - Paths.
Feb 10 11:14:36 systemd[1070]: Reached target timers.target - Timers.
Feb 10 11:14:36 systemd[1070]: Starting dbus.socket - D-Bus User Message Bus Socket...
Feb 10 11:14:36 systemd[1070]: Listening on dirmngr.socket - GnuPG network certificate management daemon.
Feb 10 11:14:36 systemd[1070]: Listening on gcr-ssh-agent.socket - GCR ssh-agent wrapper.
Feb 10 11:14:36 systemd[1070]: Listening on gnome-keyring-daemon.socket - GNOME Keyring daemon.
Feb 10 11:14:36 systemd[1070]: Listening on gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
Feb 10 11:14:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.freedesktop.systemd1'
Feb 10 11:14:36 systemd[1070]: Listening on gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Feb 10 11:14:36 systemd[1070]: Listening on gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Feb 10 11:14:36 systemd[1070]: Listening on gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Feb 10 11:14:36 systemd[1070]: Listening on pulseaudio.socket - Sound System.
Feb 10 11:14:36 systemd[1070]: Listening on dbus.socket - D-Bus User Message Bus Socket.
Feb 10 11:14:36 systemd[1070]: Reached target sockets.target - Sockets.
Feb 10 11:14:36 systemd[1070]: Reached target basic.target - Basic System.
Feb 10 11:14:36 systemd[1070]: Starting pulseaudio.service - Sound Service...
Feb 10 11:14:36 systemd[1070]: Starting dbus.service - D-Bus User Message Bus...
Feb 10 11:14:36 systemd[1070]: Started dbus.service - D-Bus User Message Bus.
Feb 10 11:14:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.7' (uid=1000 pid=1087 comm="xfce4-session")
Feb 10 11:14:36 systemd[1070]: Starting at-spi-dbus-bus.service - Accessibility services bus...
Feb 10 11:14:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.a11y.Bus'
Feb 10 11:14:36 systemd[1070]: Started at-spi-dbus-bus.service - Accessibility services bus.
Feb 10 11:14:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.9' (uid=1000 pid=1087 comm="xfce4-session")
Feb 10 11:14:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 11:14:36 at-spi-bus-launcher[1154]: dbus-daemon[1154]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=1087 comm="xfce4-session")
Feb 10 11:14:36 at-spi-bus-launcher[1154]: dbus-daemon[1154]: Successfully activated service 'org.a11y.atspi.Registry'
Feb 10 11:14:36 at-spi-bus-launcher[1164]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Feb 10 11:14:36 systemd[1070]: Started gpg-agent.service - GnuPG cryptographic agent and passphrase cache.
Feb 10 11:14:36 gpg-agent[1171]: gpg-agent (GnuPG) 2.2.40 starting in supervised mode.
Feb 10 11:14:36 gpg-agent[1171]: using fd 3 for extra socket (/run/user/1000/gnupg/S.gpg-agent.extra)
Feb 10 11:14:36 gpg-agent[1171]: using fd 4 for ssh socket (/run/user/1000/gnupg/S.gpg-agent.ssh)
Feb 10 11:14:36 gpg-agent[1171]: using fd 5 for std socket (/run/user/1000/gnupg/S.gpg-agent)
Feb 10 11:14:36 gpg-agent[1171]: using fd 6 for browser socket (/run/user/1000/gnupg/S.gpg-agent.browser)
Feb 10 11:14:36 gpg-agent[1171]: listening on: std=5 extra=3 browser=6 ssh=4
Feb 10 11:14:36 systemd[1070]: Started gpg-agent.service - GnuPG cryptographic agent and passphrase cache.
Feb 10 11:14:36 gpg-agent[1174]: gpg-agent (GnuPG) 2.2.40 starting in supervised mode.
Feb 10 11:14:36 gpg-agent[1174]: using fd 3 for extra socket (/run/user/1000/gnupg/S.gpg-agent.extra)
Feb 10 11:14:36 gpg-agent[1174]: using fd 4 for ssh socket (/run/user/1000/gnupg/S.gpg-agent.ssh)
Feb 10 11:14:36 gpg-agent[1174]: using fd 5 for std socket (/run/user/1000/gnupg/S.gpg-agent)
Feb 10 11:14:36 gpg-agent[1174]: using fd 6 for browser socket (/run/user/1000/gnupg/S.gpg-agent.browser)
Feb 10 11:14:36 gpg-agent[1174]: listening on: std=5 extra=3 browser=6 ssh=4
Feb 10 11:14:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.12' (uid=1000 pid=1176 comm="xfwm4")
Feb 10 11:14:36 systemd[1070]: Starting gvfs-daemon.service - Virtual filesystem service...
Feb 10 11:14:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.gtk.vfs.Daemon'
Feb 10 11:14:36 systemd[1070]: Started gvfs-daemon.service - Virtual filesystem service.
Feb 10 11:14:36 pulseaudio[1086]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Feb 10 11:14:36 pulseaudio[1086]: Most likely this is a bug in the ALSA driver '(null)'. Please report this issue to the ALSA developers.
Feb 10 11:14:36 pulseaudio[1086]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Feb 10 11:14:37 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating via systemd: service name='org.freedesktop.thumbnails.Thumbnailer1' unit='tumblerd.service' requested by ':1.17' (uid=1000 pid=1216 comm="xfdesktop")
Feb 10 11:14:37 systemd[1070]: Starting tumblerd.service - Thumbnailing service...
Feb 10 11:14:37 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating via systemd: service name='org.freedesktop.Notifications' unit='xfce4-notifyd.service' requested by ':1.21' (uid=1000 pid=1223 comm="xfce4-power-manager")
Feb 10 11:14:37 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating via systemd: service name='ca.desrt.dconf' unit='dconf.service' requested by ':1.19' (uid=1000 pid=1232 comm="light-locker")
Feb 10 11:14:37 systemd[1070]: Starting dconf.service - User preferences database...
Feb 10 11:14:37 systemd[1070]: Starting xfce4-notifyd.service - XFCE notifications service...
Feb 10 11:14:37 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.freedesktop.Notifications'
Feb 10 11:14:37 systemd[1070]: Started xfce4-notifyd.service - XFCE notifications service.
Feb 10 11:14:37 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'ca.desrt.dconf'
Feb 10 11:14:37 systemd[1070]: Started dconf.service - User preferences database.
Feb 10 11:14:37 xfce4-notifyd[1261]: Another notification daemon is running, exiting
Feb 10 11:14:37 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.20' (uid=1000 pid=1225 comm="/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd")
Feb 10 11:14:37 systemd[1070]: Starting gvfs-udisks2-volume-monitor.service - Virtual filesystem service - disk device monitor...
Feb 10 11:14:37 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating via systemd: service name='org.bluez.obex' unit='obex.service' requested by ':1.29' (uid=1000 pid=1230 comm="/usr/bin/python3 /usr/bin/blueman-applet")
Feb 10 11:14:37 systemd[1070]: Starting obex.service - Bluetooth OBEX service...
Feb 10 11:14:37 obexd[1364]: OBEX daemon 5.66
Feb 10 11:14:37 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.bluez.obex'
Feb 10 11:14:37 systemd[1070]: Started obex.service - Bluetooth OBEX service.
Feb 10 11:14:37 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='com.teamviewer.TeamViewer' requested by ':1.34' (uid=1000 pid=1325 comm="/opt/teamviewer/tv_bin/teamviewerd -d")
Feb 10 11:14:37 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Feb 10 11:14:37 systemd[1070]: Started gvfs-udisks2-volume-monitor.service - Virtual filesystem service - disk device monitor.
Feb 10 11:14:37 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1'
Feb 10 11:14:37 systemd[1070]: Started tumblerd.service - Thumbnailing service.
Feb 10 11:14:37 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.17' (uid=1000 pid=1216 comm="xfdesktop")
Feb 10 11:14:37 systemd[1070]: Starting gvfs-metadata.service - Virtual filesystem metadata service...
Feb 10 11:14:37 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.gtk.vfs.Metadata'
Feb 10 11:14:37 systemd[1070]: Started gvfs-metadata.service - Virtual filesystem metadata service.
Feb 10 11:14:37 systemd[1070]: Started pulseaudio.service - Sound Service.
Feb 10 11:14:37 systemd[1070]: Reached target default.target - Main User Target.
Feb 10 11:14:37 systemd[1070]: Startup finished in 1.764s.
Feb 10 11:14:37 pulseaudio[1086]: Could not find org.bluez.BatteryProviderManager1.RegisterBatteryProvider(), is bluetoothd started with experimental features enabled (-E flag)?
Feb 10 11:14:38 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'com.teamviewer.TeamViewer'
Feb 10 11:14:38 com.teamviewer.TeamViewer[1441]: qrc:/ui/MainWindow/OneUIToggle.qml:33: ReferenceError: oneUIToggleModel is not defined
Feb 10 11:14:38 com.teamviewer.TeamViewer[1441]: qrc:/ui/MainWindow/Meeting/MeetingJoinPanel.qml:69: TypeError: Cannot read property 'participantName' of null
Feb 10 11:14:38 com.teamviewer.TeamViewer[1441]: qrc:/ui/MainWindow/Meeting/MeetingJoinPanel.qml:17: TypeError: Cannot read property 'joinEnabled' of null
Feb 10 11:14:38 com.teamviewer.TeamViewer[1441]: qrc:/ui/MainWindow/Meeting/MeetingJoinPanel.qml:18: TypeError: Cannot read property 'joining' of null
Feb 10 11:14:38 com.teamviewer.TeamViewer[1441]: file:///opt/teamviewer/tv_bin/RTlib/qt/qml/QtQuick/Controls/Private/Style.qml:52: ReferenceError: __control is not defined
Feb 10 11:14:38 com.teamviewer.TeamViewer[1441]: file:///opt/teamviewer/tv_bin/RTlib/qt/qml/QtQuick/Controls/Styles/Base/ScrollViewStyle.qml:56: ReferenceError: __control is not defined
Feb 10 11:16:12 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='com.teamviewer.TeamViewer.Desktop' requested by ':1.51' (uid=1000 pid=1325 comm="/opt/teamviewer/tv_bin/teamviewerd -d")
Feb 10 11:16:12 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'com.teamviewer.TeamViewer.Desktop'
Feb 10 11:16:12 com.teamviewer.TeamViewer[1441]: qrc:/ui/MainWindow/MainBanner.qml:48:2: QML RowLayout: Binding loop detected for property "width"
Feb 10 11:24:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 11:24:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 11:34:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 11:34:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 11:44:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 11:44:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 11:54:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 11:54:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 12:04:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 12:04:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 12:14:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 12:14:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 12:24:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 12:24:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 12:34:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 12:34:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 12:44:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 12:44:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 12:54:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 12:54:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 13:04:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 13:04:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 13:14:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 13:14:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 13:24:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 13:24:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 13:34:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 13:34:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 13:44:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 13:44:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 13:54:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 13:54:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 14:04:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 14:04:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 14:14:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 14:14:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 14:24:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 14:24:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 14:34:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 14:34:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 14:44:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 14:44:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 14:54:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 14:54:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 15:04:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 15:04:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 15:14:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 15:14:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 15:24:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 15:24:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 15:34:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 15:34:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 15:44:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 15:44:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 15:54:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 15:54:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 16:04:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 16:04:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 16:14:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 16:14:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 16:24:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 16:24:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 16:34:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 16:34:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 16:44:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 16:44:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 16:54:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 16:54:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 17:04:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 17:04:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 17:14:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 17:14:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 17:24:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 17:24:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 17:34:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 17:34:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 17:36:25 com.teamviewer.TeamViewer[1441]: qrc:/ui/Widgets/SessionList.qml:57: TypeError: Cannot read property 'width' of null
Feb 10 17:36:25 com.teamviewer.TeamViewer[1441]: qrc:/ui/Widgets/SessionList.qml:46: TypeError: Cannot read property 'sessionListModel' of null
Feb 10 17:36:25 com.teamviewer.TeamViewer[1441]: qrc:/ui/Widgets/SessionList.qml:40: TypeError: Cannot read property 'meetingID' of null
Feb 10 17:36:25 com.teamviewer.TeamViewer[1441]: qrc:/ui/Widgets/SessionList.qml:15: TypeError: Cannot read property 'isMeeting' of null
Feb 10 17:44:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 17:44:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 17:54:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 17:54:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 18:04:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 18:04:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 18:14:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 18:14:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 18:24:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 18:24:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 18:34:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 18:34:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 18:44:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.xfce.Xfconf' requested by ':1.15' (uid=1000 pid=1203 comm="xfce4-panel")
Feb 10 18:44:36 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.xfce.Xfconf'
Feb 10 18:47:15 com.teamviewer.TeamViewer[1441]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1525, resource id: 8400103, major code: 40 (TranslateCoords), minor code: 0
Feb 10 18:47:31 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating via systemd: service name='org.freedesktop.portal.Desktop' unit='xdg-desktop-portal.service' requested by ':1.104' (uid=1000 pid=2442 comm="/usr/lib/firefox-esr/firefox-esr")
Feb 10 18:47:31 systemd[1070]: Starting xdg-desktop-portal.service - Portal service...
Feb 10 18:47:31 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating via systemd: service name='org.freedesktop.portal.Documents' unit='xdg-document-portal.service' requested by ':1.105' (uid=1000 pid=2489 comm="/usr/libexec/xdg-desktop-portal")
Feb 10 18:47:31 systemd[1070]: Starting xdg-document-portal.service - flatpak document portal service...
Feb 10 18:47:31 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating via systemd: service name='org.freedesktop.impl.portal.PermissionStore' unit='xdg-permission-store.service' requested by ':1.106' (uid=1000 pid=2493 comm="/usr/libexec/xdg-document-portal")
Feb 10 18:47:31 systemd[1070]: Starting xdg-permission-store.service - sandboxed app permission store...
Feb 10 18:47:31 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore'
Feb 10 18:47:31 systemd[1070]: Started xdg-permission-store.service - sandboxed app permission store.
Feb 10 18:47:31 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.freedesktop.portal.Documents'
Feb 10 18:47:31 systemd[1070]: Started xdg-document-portal.service - flatpak document portal service.
Feb 10 18:47:31 xdg-document-portal[2493]: Ignoring invalid max threads value 4294967295 > max (100000).
Feb 10 18:47:31 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating via systemd: service name='org.freedesktop.impl.portal.desktop.gtk' unit='xdg-desktop-portal-gtk.service' requested by ':1.105' (uid=1000 pid=2489 comm="/usr/libexec/xdg-desktop-portal")
Feb 10 18:47:31 systemd[1070]: Starting xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation)...
Feb 10 18:47:31 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.freedesktop.impl.portal.desktop.gtk'
Feb 10 18:47:31 systemd[1070]: Started xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation).
Feb 10 18:47:31 xdg-desktop-portal[2489]: pw.conf: can't load config client.conf: No such file or directory
Feb 10 18:47:31 xdg-desktop-portal[2489]: pw.conf: can't load default config client.conf: No such file or directory
Feb 10 18:47:31 xdg-desktop-por[2489]: Failed connect to PipeWire: Couldn't create PipeWire context
Feb 10 18:47:31 dbus-daemon[1097]: [session uid=1000 pid=1097] Activating service name='org.freedesktop.secrets' requested by ':1.105' (uid=1000 pid=2489 comm="/usr/libexec/xdg-desktop-portal")
Feb 10 18:47:31 systemd[1070]: Started gnome-keyring-daemon.service - GNOME Keyring daemon.
Feb 10 18:47:31 gnome-keyring-daemon[2515]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Feb 10 18:47:31 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.freedesktop.secrets'
Feb 10 18:47:31 gnome-keyring-daemon[2515]: The Secret Service was already initialized
Feb 10 18:47:31 gnome-keyring-d[2515]: The Secret Service was already initialized
Feb 10 18:47:31 gnome-keyring-daemon[2514]: discover_other_daemon: 1
Feb 10 18:47:31 org.freedesktop.secrets[2514]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Feb 10 18:47:31 dbus-daemon[1097]: [session uid=1000 pid=1097] Successfully activated service 'org.freedesktop.portal.Desktop'
Feb 10 18:47:31 systemd[1070]: Started xdg-desktop-portal.service - Portal service.

Thanks.

[M22]

Not sure why, but now, the mounting operation time dropped down to 6+ seconds. Though, this is still lot more than the other HDD that is mounted :

Code: Select all

6.503s run-media-<userName>-FILES.mount
2.956s NetworkManager-wait-online.service
1.163s resilio-sync.service
 890ms nvidia-persistenced.service
 886ms systemd-modules-load.service
 545ms run-media-<userName>-DATA.mount
 510ms e2scrub_reap.service

[fabien]

The important part of your logs is missing, i.e. the boot sequence.
On my system, these are the first lines at startup:

Code: Select all

Feb 10 16:36:49 kernel: microcode: microcode updated early to revision 0x21, date = 2019-02-13
Feb 10 16:36:49 kernel: Linux version 6.1.0-17-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.69-1 (2023-12-30)
Feb 10 16:36:49 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-17-amd64 root=UUID=8dcdb518-9bdb-47d2-9907-9c239ce55c59 ro quiet nmi_watchdog=0 libata.noacpi=1
Feb 10 16:36:49 kernel: BIOS-provided physical RAM map:
Feb 10 16:36:49 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
[...]

Not sure why, but now, the mounting operation time dropped down to 6+ seconds.

This may be an intermittent problem. You can go back through your startup logs as follows:

Code: Select all

#> journalctl --no-hostname -b -1
#> journalctl --no-hostname -b -2

and so on.
Please find a boot where the problem occurred and attach it to your next post, e.g.

Code: Select all

#> journalctl --no-hostname -b -2 | gzip >/tmp/mybootlog.gz

[CwF]

I would think a 4TB 2.5 drive is an SMR type drive. This type of drive has the heaviest firmware duties of any type of drive and are the slowest to 'take inventory'.

It's common for firmware to do housekeeping whenever powered, and idle. Since I use drive cages and often pass them to a vm the one thing different from a cold boot is the drive is powered for a decent amount of time before it is mounted. Over years of recovering problematic hard disc I've learned to power those first without a data link and listen or feel for activity for an extended period. This can give clues!

If the external case can be used for testing it would be a good way to power cycle and mount/umount in a terminal - so you can be quiet and put a finger on it, literally. You should be able to feel the spin up and activity during these actions. On power after spin up there should be some random activity, long or short random (as far as we know) is good. If you feel a repetitive pattern for an extended period -that's bad. During mount they may or not be a spin up, but there will be similar activity. Mounting in a terminal will give direct feedback as it pauses during mount until returning the prompt. You could also have another terminal up with a 'journalctl -f' active. During that time; random, pattern, or no activity. That is good, bad, or maybe not a drive issue.

It's my guess that varied startup times of smr disk depend on the pattern of activity before the last shut down. As time goes on if all is well the startup time may shorten. That day you move gigs of stuff over to this drive and happen to shutdown immediately after that, the next startup will have a delay.

Also journal, use search terms mount, sense, SStatus, ata, etc, depending....

Code: Select all

$ journalctl -b 0 -g mount --no-pager

[trinidad]

varied startup times of smr disk depend on the pattern of activity before the last shut down

Very much true of SMR drives. They always will require reorganizing time after large writes, but it's that tradeoff that allows for faster write time on big disks running NTFS. It is important to remember that SMR drives always require idle time, that is running without being written to in any substantial way. The bigger the previous write the longer the idle time.

TC

[fabien]

I've learned to power those first without a data link and listen or feel for activity for an extended period. [...] You should be able to feel the spin up and activity during these actions.

I like this! These little pets are alive and deserve a lot of attention
Thanks for your insight @CwF, maybe a shortcut to understanding what's going on.

[M22]

What I am puzzled of, is, why it suddenly happening now. Before the above incident, I didn't even notice any delay when booting.

(And hopefully I wrote my post to be clarified that I already removed the said drive from it's enclosure and is connected directly to the motherboard via the SATA interface.)
And again, I would like to reiterate that this delay only just recently popped up.

Anyway, I will post the output of the above new command as soon as I get back.

Thank you again.

[M22]

Here are the attachments of the outputs:

<system-analyze blame> shows it takes about 6 to 7+ seconds to mount the FILES drive.

Thanks.

[Aki]

Hello,

From your log, I suppose the affected disk is a Seagate Barracuda ST4000LM024 [1]:

Code: Select all

Feb 10 20:11:38 kernel: ata13: SATA max UDMA/133 abar m2048@0xfc400000 port 0xfc400300 irq 78
Feb 10 20:11:38 kernel: ata13: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 10 20:11:38 kernel: ata13.00: supports DRM functions and may not be fully accessible
Feb 10 20:11:38 kernel: ata13.00: ATA-10: ST4000LM024-2U817V, 0001, max UDMA/133
Feb 10 20:11:38 kernel: ata13.00: 7814037168 sectors, multi 1: LBA48 NCQ (depth 32), AA
Feb 10 20:11:38 kernel: ata13.00: Features: Trust
Feb 10 20:11:38 kernel: ata13.00: supports DRM functions and may not be fully accessible
Feb 10 20:11:38 kernel: ata13.00: configured for UDMA/133

In the first log, it takes 9 seconds to be mounted:

Code: Select all

$ grep sdb journalctl-1-su.txt
Feb 10 21:11:04 kernel: sd 12:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
Feb 10 21:11:04 kernel: sd 12:0:0:0: [sdb] 4096-byte physical blocks
Feb 10 21:11:04 kernel: sd 12:0:0:0: [sdb] Write Protect is off
Feb 10 21:11:04 kernel: sd 12:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Feb 10 21:11:04 kernel: sd 12:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 10 21:11:04 kernel: sd 12:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes
Feb 10 21:11:04 kernel:  sdb: sdb1
Feb 10 21:11:04 kernel: sd 12:0:0:0: [sdb] supports TCG Opal
Feb 10 21:11:04 kernel: sd 12:0:0:0: [sdb] Attached SCSI disk
Feb 10 21:11:12 ntfs-3g[871]: Mounted /dev/sdb1 (Read-Write, label "FILES", NTFS 3.1)
Feb 10 21:11:12 ntfs-3g[871]: Mount options: allow_other,nonempty,relatime,rw,fsname=/dev/sdb1,blkdev,blksize=4096
Feb 10 21:59:10 ntfs-3g[871]: Unmounting /dev/sdb1 (FILES)

and in the second log, it takes 7 seconds to be mounted:

Code: Select all

$ grep sdc journalctl-2-su.txt 
Feb 10 20:11:38 kernel: sd 12:0:0:0: [sdc] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
Feb 10 20:11:38 kernel: sd 12:0:0:0: [sdc] 4096-byte physical blocks
Feb 10 20:11:38 kernel: sd 12:0:0:0: [sdc] Write Protect is off
Feb 10 20:11:38 kernel: sd 12:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Feb 10 20:11:38 kernel: sd 12:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 10 20:11:38 kernel: sd 12:0:0:0: [sdc] Preferred minimum I/O size 4096 bytes
Feb 10 20:11:38 kernel:  sdc: sdc1
Feb 10 20:11:38 kernel: sd 12:0:0:0: [sdc] supports TCG Opal
Feb 10 20:11:38 kernel: sd 12:0:0:0: [sdc] Attached SCSI disk
Feb 10 20:11:45 ntfs-3g[870]: Mounted /dev/sdc1 (Read-Write, label "FILES", NTFS 3.1)
Feb 10 20:11:45 ntfs-3g[870]: Mount options: allow_other,nonempty,relatime,rw,fsname=/dev/sdc1,blkdev,blksize=4096
Feb 10 21:10:42 ntfs-3g[870]: Unmounting /dev/sdc1 (FILES)

Therefore, I confirm it takes about the same time (7-9 seconds).

You may consider connecting the disk to a computer running Windows to verify if the file system need to be fixed/optimized.

--
[1] Seagate® BarraCuda® 2.5-inch HDD

[M22]

Thank you for pointing it out. I will do that in Windows and report back.

[M22]

I booted back into my Windows drive, ran chkdsk /f on the FILES drive and it found no problems. I then run the GUI disk check, and it also found no problems.

I then booted back to my Debian drive, and can see that it boots immediately after grub, almost like before. It still takes more than 1 second to mount, unlike my other Seagate 2TB drive, but it's almost back to normal.

<system-analyze blame> now shows it takes 1.855secs to mount the FILES drive:

Code: Select all

5.084s NetworkManager-wait-online.service
1.855s run-media-<userName>-FILES.mount
1.122s resilio-sync.service
1.012s udisks2.service
 895ms nvidia-persistenced.service
 815ms systemd-modules-load.service
 560ms run-media-<userName>-DATA.mount
 470ms e2scrub_reap.service
 391ms apt-daily-upgrade.service
 377ms blueman-mechanism.service
 359ms systemd-journal-flush.service
 352ms dev-sdc1.device
 351ms logrotate.service
 250ms apt-daily.service
 215ms systemd-rfkill.service
 189ms systemd-udevd.service
 140ms ModemManager.service
 132ms cups.service
 124ms user@1000.service
 120ms teamviewerd.service
  96ms systemd-udev-trigger.service
... --snip--

I still don't know what the reason was for the prolonged delay to mount that drive before. I would like to troubleshoot the same problem if it happens again, and knowing what the reason was will be helpful in the future.

Thank you for pointing out some things to do, though. Maybe checking the drive helped.

Thank you all again.

[Aki]

Hello,

Maybe checking the drive helped.

Yes, it probably helped. The NTFS support in Debian GNU/Linux is not at the same level as Windows for speed and disk optimisation. Nor Debian GNU/Linux has scrub or optimization tools for it.

Do you use it mainly for reading or writing files to/from it?

[M22]

Hello,

Maybe checking the drive helped.

Yes, it probably helped. The NTFS support in Debian GNU/Linux is not at the same level as Windows for speed and disk optimisation. Nor Debian GNU/Linux has scrub or optimization tools for it.

Do you use it mainly for reading or writing files to/from it?

This drive used to store the data, mainly the music, video and backup ISOs of CDs for DOS and emulations and emulation roms. I guess it's mainly used for reading.

[Aki]

Hello,

As far I know, the NTFS file system should be avoided with Debian GNU/Linux unless you need to use/access the disk natively and mainly with Windows. And it seems the latter is not your main use case.

In my humble opinion, it is also not a good idea to use it for backups originating from Debian GNU/Linux.

[M22]

Hello,

As far I know, the NTFS file system should be avoided with Debian GNU/Linux unless you need to use/access the disk natively and mainly with Windows. And it seems the latter is not your main use case.

In my humble opinion, it is also not a good idea to use it for backups originating from Debian GNU/Linux.

Sorry for the extremely late reply. Don't know how I missed the last post.

Yes, my Windows drive also shares the above storage drive, hence using the NTFS format. I don't use Windows often but it's there for certain programs that are either difficult to work under WINE or unable to work at all without some hiccups and for certain Windows games that prove too difficult for a workaround under WINE.

[Aki]

I'm glad you sorted it out. :)

Please, mark the discussion as "solved" manually adding the text tag "[Solved]" at the beginning of the subject of the first message (after other tags, if any).

Happy Debian !