[opensuse] Puzzling timeout for a non existing disc - how to find the culprit?
I am running a system with a single ssd (notebook). /etc/fstab is as follows cat /etc/fstab /dev/system/root / ext4 acl,user_xattr 0 1 /dev/system/home /home ext4 data=ordered,acl,user_xattr 0 2 /dev/system/swap swap swap defaults 0 0 So far so good. During startup I have a 1.30 minute job running for a disc that times out. This is normally sign that a) the disc denomination is wrong our b) double. I am not understanding were I have to search for the entry. Goes like this: Timed out waiting for device dev-disk-by\x2duuid-69fb75a4\x2d7dc0\x2d4dbf \x2d9db> I looked in cat /etc/crypttab cr_sda2 UUID=cab3c018-394e-4ee8-83bc-82096111e4b2 cr_ata-WDC_WD10JPVX-22JC3T0_WD-WXW1A372PSED-part1 UUID=69fb75a4-7dc0-4dbf-9db4-724e35370033 this ata-WDC is not really understandable to me, as I have a samsung ssd. I think here could be the reason. Can I simply comment that out? I am puzzled as I do not even understand were this entry comes from. Could it be a non well unmounted encrypted external backup disk? _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data martedì 8 gennaio 2019 17:53:40 CET, stakanov ha scritto:
I am running a system with a single ssd (notebook). /etc/fstab is as follows cat /etc/fstab /dev/system/root / ext4 acl,user_xattr 0 1 /dev/system/home /home ext4 data=ordered,acl,user_xattr 0 2 /dev/system/swap swap swap defaults 0 0
So far so good. During startup I have a 1.30 minute job running for a disc that times out. This is normally sign that a) the disc denomination is wrong our b) double. I am not understanding were I have to search for the entry. Goes like this: Timed out waiting for device dev-disk-by\x2duuid-69fb75a4\x2d7dc0\x2d4dbf \x2d9db>
I looked in cat /etc/crypttab cr_sda2 UUID=cab3c018-394e-4ee8-83bc-82096111e4b2 cr_ata-WDC_WD10JPVX-22JC3T0_WD-WXW1A372PSED-part1 UUID=69fb75a4-7dc0-4dbf-9db4-724e35370033
this ata-WDC is not really understandable to me, as I have a samsung ssd. I think here could be the reason. Can I simply comment that out? I am puzzled as I do not even understand were this entry comes from. Could it be a non well unmounted encrypted external backup disk?
O.K. I was bold and I simply tried to erase the entry. That worked. That changes a bit the content of my question: Is a crypttab entry usually surviving when an luks encrypted USB external backup disc is connected and then for whatever reason detached (e.g. cable is torn out by chance). It would be very good to know this, in case it should represent itself. Also if there is a way to prevent it. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/01/2019 17.53, stakanov wrote:
I am running a system with a single ssd (notebook). /etc/fstab is as follows cat /etc/fstab /dev/system/root / ext4 acl,user_xattr 0 1 /dev/system/home /home ext4 data=ordered,acl,user_xattr 0 2 /dev/system/swap swap swap defaults 0 0
So far so good. During startup I have a 1.30 minute job running for a disc that times out. This is normally sign that a) the disc denomination is wrong our b) double. I am not understanding were I have to search for the entry. Goes like this: Timed out waiting for device dev-disk-by\x2duuid-69fb75a4\x2d7dc0\x2d4dbf \x2d9db>
I looked in cat /etc/crypttab cr_sda2 UUID=cab3c018-394e-4ee8-83bc-82096111e4b2 cr_ata-WDC_WD10JPVX-22JC3T0_WD-WXW1A372PSED-part1 UUID=69fb75a4-7dc0-4dbf-9db4-724e35370033
this ata-WDC is not really understandable to me, as I have a samsung ssd.
That's the one :-) First, unwrap it: cr_ata-WDC_WD10JPVX-22JC3T0_WD-WXW1A372PSED-part1 UUID=69fb75a4-7dc0-4dbf-9db4-724e35370033 That would be typically simplified as (the first word is arbitrary): cr_ata-WDC_p1 UUID=69fb75a4-7dc0-4dbf-9db4-724e35370033 Then take the line in the logs: dev-disk-by\x2duuid-69fb75a4\x2d7dc0\x2d4dbf\x2d9db> Remove noise (each '\x2d' i a '-'): dev-disk-by-uuid-69fb75a4-7dc0-4dbf-9db Do you see now the similarities? :-)
I think here could be the reason. Can I simply comment that out?
Certainly.
I am puzzled as I do not even understand were this entry comes from. Could it be a non well unmounted encrypted external backup disk?
Maybe. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
participants (2)
-
Carlos E. R.
-
stakanov