I work on computer with openSUSE 42.1 (I know, after all I’ll upgrade the system to 42.3). When I stuck a charge of my phone to the USB port, the machine froze immediately. It sometimes happened in the past, so nothing new for me. Only hard restart helped me. But today, after that, something went wrong and I see the following warning on the black screen:
Boot has failed. To debug this issue add rd.shell rd.debug to the kernel command line
I did what the command suggests and I see another message:
can't find command esetparams
Do you have any idea how to solve this bug? Of course I used Google but there is no information about that. When the last message disappeared the terminal showed up. I typed journalclt but there was too much information to rewrite it.
2.960922] user systemd[1]: Starting File System Check on /dev/disk/by-uuid/45feac9e-ab14-4508-b0ae-da3d4ab896ef...
3.011657] user systemd-fsck[337]: /dev/sda1 contains a file system with errors, check forced.
...
...
6.023529] user systemd-fsck[337]: /dev/sda1: Inodes that were part of a corrupted orphan linked list found.
6.023718] user systemd-fsck[337]: /dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
6.023868] user systemd-fsck[337]: (i.e., without -a or -p options)
6.060216] user systemd-fsck[337]: fsck failed with error code 4.
However, this is indicative of a hardware problem that you should investigate. It seems to be power-related, like faulty usb port isolation, current leak or earthing problems (do you get a small electric shock when touching the case?) or possibly a defective USB port (I’ve seen a few of those).
If you’re on a desktop, you could try using one of the motherboard ports in the back instead of the USB port(s) in the front of the case. IME these case ports are not always of good quality, and in time stop working correctly - which is worse than not working at all, as it may damage your device or short-circuit the motherboard power circuitry that feeds the USB extension headers.
When I have to use a motherboard port in the back, a good-quality usb extension cable is a good help.
Yes, you’re right. Thanks for the advice. As I wrote before there were problems with the USBs and indeed I used the front ports. I also got a small electric shock when touching the case. If fsck helps, I will upgrade my system to 42.3 and won’t use the front USB ports. Whatever happens we’ll be in touch. I always leave a solution for others.
Additionally, it may be worth a quick look at the smartctrl data for that drive.
sudo smartctl -data -A /dev/sdX
Although in this case I suspect the FS corruption was more likely due to the hard reset that was necessitated.
Also, and I apologise if I’m telling you something that you already know, and indeed may have done.
Prior to a hard reset it’s worth trying the “Magic SysRq” key sequence to try to recover from a crash with a proper shutdown:
Press and hold Alt + SysRq (Prt Scr), then in sequence r, e, i, s, u, b. Allow a few seconds after each key press, longer (90secs or so) after e.
Which should, if it’s successful:
r - Release the keyboard from the X-server
e - Shutdown processes (SIGTERM)
i - Forcibly shutdown any remaining processes (SIGKILL)
s - Sync the file system
u - Unmount the file system(s)
b - Reboot
If the system reboots then it’s worked, if not… then use the hard reset option.
I made fsck manually and the program has fixed some bugs. The message disappeared but the emergency mode showed up:
Welcome to emergency mode! After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" to try again
to boot into default mode.
Give root password for maintenance
(or press Control-D to continue):
Control-D, jorunalctl reboot and default don’t work. Journalctl -xb prints a log and I can log in as root. I read Google again and finally I used DVD with 42.1 to make upgrade. During mounting partitions the installer tells me that cannot find a specific UUID. The installer propose me mounting a new partition as /home2. I have two additional disks in my PC mounted as /home2 and /home3 without system but before fixing I plugged out both. I see I can continue mounting disk on /home4. I don’t know why it is impossible on /home. What I should to do? I want to restore the current system and make upgrade to 42.3.
So I should make partition on /home2? As I understand, when I try to upgrade a system from DVD it means that I want to restore default files, i.e. before actualization, and replace them with the current files which can be damaged. There is no advanced option of the partitioner when you use an upgrade option from DVD. I can only indicate the mount point. The default is /home2, when I try to set /home and press continue the installer displays the window again and sets the default mount point as /home3 and so on.
OK… Sorry I’ve not done a DVD upgrade, I was assuming the partition/format options would be the same as a new install.
You’re still using the 42.1 DVD? Or am I mistaken?
Would this not be a good opportunity to make a fresh install using 42.3. Then you could use the Advanced/Expert partitioner to read the existing partitions and mount points. Format only the root partition and keep your existing /home(s). That way you benefit from a fresh install of 42.3 whilst still retaining your user data in the home partition(s).
Otherwise I would wait for someone who is familiar with the DVD upgrade process to offer advice.
The better solution is to restore 42.1 and then upgrade. Why? Because I won’t lose any executable programs. I’m a scientist and I use a lot of software. Of course I can install them again but a configure process is time consuming. We don’t limit to the upgrade option. I can run another instructions but I don’t know which to use.
Ah!! That was actually evident from SUSE Paste but I failed to spot it! :embarrassed:
Nov 10 14:46:17 user kernel: EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
Nov 10 14:47:42 user systemd[1]: Job dev-disk-by\x2duuid-79e99b61\x2d74d5\x2d4942\x2d9194\x2d1805ebf1e689.device/start timed out.
Nov 10 14:47:42 user systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-79e99b61\x2d74d5\x2d4942\x2d9194\x2d1805ebf1e689.device.
-- Subject: Unit dev-disk-by\x2duuid-79e99b61\x2d74d5\x2d4942\x2d9194\x2d1805ebf1e689.device has failed
-- Defined-By: systemd
--
-- Unit dev-disk-by\x2duuid-79e99b61\x2d74d5\x2d4942\x2d9194\x2d1805ebf1e689.device has failed.
--
-- The result is timeout.
Nov 10 14:47:42 user systemd[1]: Dependency failed for /home2.
-- Subject: Unit home2.mount has failed
-- Defined-By: systemd
--
-- Unit home2.mount has failed.
With a similar entry for home3.mount.
EDIT: how to mark the thread as SOLVED?
This forum doesn’t support that I’m afraid. Suffice to say you’ve told us the problem is solved.
