[opensuse] updated tumbleweed today and find myself to a emergency console
Not very informative. The file it says to copy does not exist. Apparently there is an inconsistency with sda3 but does not tell me nothing, as I do not know what the system really calls sda3 now. (fstab is empty it seems?). which command (in rescue mode) can tell me what is sda3 (in terms of hardware / partition. In bios all discs appear, so it is not a cable. The problem happened after the tw update today . I am a bit lost. Not even a dir command works? _________________________________________________________________ ________________________________________________________ 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 12/12/2018 19.39, stakanov wrote:
Not very informative. The file it says to copy does not exist. Apparently there is an inconsistency with sda3 but does not tell me nothing, as I do not know what the system really calls sda3 now. (fstab is empty it seems?).
which command (in rescue mode) can tell me what is sda3 (in terms of hardware / partition. In bios all discs appear, so it is not a cable. The problem happened after the tw update today . I am a bit lost. Not even a dir command works?
Maybe "lsblk" is available? Otherwise, I suppose "ls" works, so you can look at the symlinks under /dev/disk-by/ -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 12/12/2018 19.39, stakanov wrote:
Not very informative. The file it says to copy does not exist. Apparently there is an inconsistency with sda3 but does not tell me nothing, as I do not know what the system really calls sda3 now. (fstab is empty it seems?).
which command (in rescue mode) can tell me what is sda3 (in terms of hardware / partition. In bios all discs appear, so it is not a cable. The problem happened after the tw update today . I am a bit lost. Not even a dir command works?
Maybe "lsblk" is available?
Otherwise, I suppose "ls" works, so you can look at the symlinks under /dev/disk-by/ he tells me that he lost inodes on /dev/sda3 (and I cannot really know that / dev/sda3 is, while /dev/disk/by-id etc does not give me any solution, all but
In data mercoledì 12 dicembre 2018 19:59:29 CET, Carlos E. R. ha scritto: the old way of nominating. However, he tells me run fsck manually. presuming ext4, and having the issue, from the rescue input what would be the command? fsck /dev/sda3? _________________________________________________________________ ________________________________________________________ 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
Le 12/12/2018 à 20:10, stakanov a écrit :
he tells me that he lost inodes on /dev/sda3 (and I cannot really know that / dev/sda3 is, while /dev/disk/by-id etc does not give me any solution,
compare with /etc/fstab all but
the old way of nominating. However, he tells me run fsck manually. presuming ext4, and having the issue, from the rescue input what would be the command? fsck /dev/sda3?
yes. the better wish is to have a swap disk having changed UID (being formatted by an other install?), because else it's a failing disk and you are in trouble :-( jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data mercoledì 12 dicembre 2018 20:18:02 CET, jdd@dodin.org ha scritto:
Le 12/12/2018 à 20:10, stakanov a écrit :
he tells me that he lost inodes on /dev/sda3 (and I cannot really know that / dev/sda3 is, while /dev/disk/by-id etc does not give me any solution, compare with /etc/fstab
all but
the old way of nominating. However, he tells me run fsck manually. presuming ext4, and having the issue, from the rescue input what would be the command? fsck /dev/sda3?
yes.
the better wish is to have a swap disk having changed UID (being formatted by an other install?), because else it's a failing disk and you are in trouble :-(
jdd yes, but a failing disc should have given a smart warning. I tried cat /etc/fstab but "file does not exist". Hummmm
I am trying fsck _________________________________________________________________ ________________________________________________________ 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 mercoledì 12 dicembre 2018 20:22:08 CET, stakanov ha scritto:
In data mercoledì 12 dicembre 2018 20:18:02 CET, jdd@dodin.org ha scritto:
Le 12/12/2018 à 20:10, stakanov a écrit :
he tells me that he lost inodes on /dev/sda3 (and I cannot really know that / dev/sda3 is, while /dev/disk/by-id etc does not give me any solution,
compare with /etc/fstab
all but
the old way of nominating. However, he tells me run fsck manually. presuming ext4, and having the issue, from the rescue input what would be the command? fsck /dev/sda3?
yes.
the better wish is to have a swap disk having changed UID (being formatted by an other install?), because else it's a failing disk and you are in trouble :-(
jdd
yes, but a failing disc should have given a smart warning. I tried cat /etc/fstab but "file does not exist". Hummmm
I am trying fsck
_________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de exactly fsck.ext4 -nv So it should give me output without doing anything definite When I know whats up I will do -p because I have little knowledge.
_________________________________________________________________ ________________________________________________________ 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
Le 12/12/2018 à 20:22, stakanov a écrit :
yes, but a failing disc should have given a smart warning.
not in my experience
I tried cat /etc/fstab but "file does not exist". Hummmm
error on root mounting?? may be a faulty update? try doing it again. No "boot previous snapshot"? jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data mercoledì 12 dicembre 2018 20:28:14 CET, jdd@dodin.org ha scritto:
Le 12/12/2018 à 20:22, stakanov a écrit :
yes, but a failing disc should have given a smart warning.
not in my experience
I tried cat /etc/fstab but "file does not exist". Hummmm
error on root mounting??
may be a faulty update? try doing it again. No "boot previous snapshot"?
jdd hmmm, no, I get only failsafe. Which stop after a while. But he complains about inodes. So I would think it is the file system.
I try with zypper but I do not know if it is available, a good idea maybe. _________________________________________________________________ ________________________________________________________ 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
Le 12/12/2018 à 20:37, stakanov a écrit :
I try with zypper but I do not know if it is available, a good idea maybe.
can be done from rescue system with this system you can see each partition by itself (mount them and see what is in them) eventually: http://dodin.org/wiki/pmwiki.php?n=Doc.AccesRootAvecOpensuseRescue I try never to use fsck if I can avoid it, can completely kill a partition and should never be necessary after a simple update jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 12/12/2018 à 20:37, stakanov a écrit :
I try with zypper but I do not know if it is available, a good idea maybe.
can be done from rescue system
with this system you can see each partition by itself (mount them and see what is in them)
eventually:
http://dodin.org/wiki/pmwiki.php?n=Doc.AccesRootAvecOpensuseRescue
I try never to use fsck if I can avoid it, can completely kill a partition and should never be necessary after a simple update
jdd
In data mercoledì 12 dicembre 2018 20:42:49 CET, jdd@dodin.org ha scritto: this is true. I did fsck.ext4 -c -y to get the inodes and the damages repaired. The /dev/sda3 is root on an ADATA ssd. out of 50 GB of the disc a fstrim -av after the repair showed 43 GB trimmed?? In all cases the system is up and "seems normal". I checked for missed update but only a few vlc codecs. I am not really assured for the health of the ssd but do not really know how I could check for lifetime. _________________________________________________________________ ________________________________________________________ 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
Le 12/12/2018 à 20:55, stakanov a écrit :
for the health of the ssd but do not really know how I could check for lifetime.
smartmon? do not really prevent failure but gives some clues jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/12/2018 20.55, stakanov wrote:
I did fsck.ext4 -c -y to get the inodes and the damages repaired. The /dev/sda3 is root on an ADATA ssd. out of 50 GB of the disc a fstrim -av after the repair showed 43 GB trimmed?? In all cases the system is up and "seems normal". I checked for missed update but only a few vlc codecs. I am not really assured for the health of the ssd but do not really know how I could check for lifetime.
smartctl -a /dev/sda One of the lines will tell you. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 12/12/2018 20.37, stakanov wrote:
In data mercoledì 12 dicembre 2018 20:28:14 CET, jdd@dodin.org ha scritto:
hmmm, no, I get only failsafe. Which stop after a while. But he complains about inodes. So I would think it is the file system.
I try with zypper but I do not know if it is available, a good idea maybe.
Don't try! Not while there is a problem with disks. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 12/12/2018 20.22, stakanov wrote:
In data mercoledì 12 dicembre 2018 20:18:02 CET, jdd@dodin.org ha scritto:
the better wish is to have a swap disk having changed UID (being formatted by an other install?), because else it's a failing disk and you are in trouble :-(
yes, but a failing disc should have given a smart warning.
Sometimes.
I tried cat /etc/fstab but "file does not exist". Hummmm
You are trying to see the fstab of the rescue system, not of the real system. That's why it doesn't exist. Chances are sda3 is your root. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
In data mercoledì 12 dicembre 2018 23:28:29 CET, Carlos E. R. ha scritto:
On 12/12/2018 20.22, stakanov wrote:
In data mercoledì 12 dicembre 2018 20:18:02 CET, jdd@dodin.org ha scritto:
the better wish is to have a swap disk having changed UID (being formatted by an other install?), because else it's a failing disk and you are in trouble :-(
yes, but a failing disc should have given a smart warning.
Sometimes.
I tried cat /etc/fstab but "file does not exist". Hummmm
You are trying to see the fstab of the rescue system, not of the real system. That's why it doesn't exist.
Chances are sda3 is your root. you were right. sda3 was my root. Not easy to capture when you are sweating :-) Well, I did run smartctl. It does not really say something is wrong. No line complains, no failure. So something has gone wrong by restarting when unmounting the file system of root it seems. /var is on another disk. So, I do not know, I think I should monitor but I do not expect this to be a major problem. Probably some program sigsevd after update and was disturbing. Anyway, I will know soon when I will start up the machine today after larger usage. Currently no complains it seems but I will monitor the journal too.
_________________________________________________________________ ________________________________________________________ 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 13/12/2018 09.48, stakanov wrote:
In data mercoledì 12 dicembre 2018 23:28:29 CET, Carlos E. R. ha scritto:
On 12/12/2018 20.22, stakanov wrote:
In data mercoledì 12 dicembre 2018 20:18:02 CET, jdd@dodin.org ha scritto:
the better wish is to have a swap disk having changed UID (being formatted by an other install?), because else it's a failing disk and you are in trouble :-(
yes, but a failing disc should have given a smart warning.
Sometimes.
I tried cat /etc/fstab but "file does not exist". Hummmm
You are trying to see the fstab of the rescue system, not of the real system. That's why it doesn't exist.
Chances are sda3 is your root. you were right. sda3 was my root. Not easy to capture when you are sweating :-) Well, I did run smartctl. It does not really say something is wrong. No line complains, no failure. So something has gone wrong by restarting when unmounting the file system of root it seems. /var is on another disk. So, I do not know, I think I should monitor but I do not expect this to be a major problem. Probably some program sigsevd after update and was disturbing. Anyway, I will know soon when I will start up the machine today after larger usage. Currently no complains it seems but I will monitor the journal too.
Yes, my bets are that for some unknown reason the system was not properly umounted the last time. Maybe the system crashed and rebooted without umounting. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
In data giovedì 13 dicembre 2018 11:55:41 CET, Carlos E. R. ha scritto:
In data mercoledì 12 dicembre 2018 23:28:29 CET, Carlos E. R. ha scritto:
On 12/12/2018 20.22, stakanov wrote:
In data mercoledì 12 dicembre 2018 20:18:02 CET, jdd@dodin.org ha scritto:
the better wish is to have a swap disk having changed UID (being formatted by an other install?), because else it's a failing disk and you are in trouble :-(
yes, but a failing disc should have given a smart warning.
Sometimes.
I tried cat /etc/fstab but "file does not exist". Hummmm
You are trying to see the fstab of the rescue system, not of the real system. That's why it doesn't exist.
Chances are sda3 is your root.
you were right. sda3 was my root. Not easy to capture when you are sweating
:-)
Well, I did run smartctl. It does not really say something is wrong. No line complains, no failure. So something has gone wrong by restarting when unmounting the file system of root it seems. /var is on another disk. So, I do not know, I think I should monitor but I do not expect this to be a major problem. Probably some program sigsevd after update and was disturbing. Anyway, I will know soon when I will start up the machine today after larger usage. Currently no complains it seems but I will monitor the journal too. Yes, my bets are that for some unknown reason the system was not
On 13/12/2018 09.48, stakanov wrote: properly umounted the last time. Maybe the system crashed and rebooted without umounting. Thinking of it, I did not recall having restarted the system. The more I think of it, it was actually running with TV and then when I came back (after the upgrade) it was on the login of the bios for the HDD. So probably for some reasons a quite catastrophic crash.
_________________________________________________________________ ________________________________________________________ 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 12/12/2018 20.10, stakanov wrote:
On 12/12/2018 19.39, stakanov wrote:
Not very informative. The file it says to copy does not exist. Apparently there is an inconsistency with sda3 but does not tell me nothing, as I do not know what the system really calls sda3 now. (fstab is empty it seems?).
which command (in rescue mode) can tell me what is sda3 (in terms of hardware / partition. In bios all discs appear, so it is not a cable. The problem happened after the tw update today . I am a bit lost. Not even a dir command works?
Maybe "lsblk" is available?
Otherwise, I suppose "ls" works, so you can look at the symlinks under /dev/disk-by/ he tells me that he lost inodes on /dev/sda3 (and I cannot really know that / dev/sda3 is, while /dev/disk/by-id etc does not give me any solution, all but
In data mercoledì 12 dicembre 2018 19:59:29 CET, Carlos E. R. ha scritto: the old way of nominating.
which is why you should have put labels on the partitions.
However, he tells me run fsck manually. presuming ext4, and having the issue, from the rescue input what would be the command? fsck /dev/sda3?
Yes, just that. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
participants (3)
-
Carlos E. R. -
jdd＠dodin.org -
stakanov