action #35976
closed[sle][functional][hard] Fix loewe.arch.suse.de
0%
Description
All machines in srv2 where powered down due to the AC outage in the extension of the server-room.
Now the machine cannot boot any longer since it cannot find its / :
[ 23.711676] List of all partitions:
[ 23.711679] No filesystem could mount root, tried:
[ 23.711683] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 23.711688] CPU: 32 PID: 1 Comm: swapper/0 Not tainted 4.4.120-45-default #1
IPMI of this machine is unfortunately no longer reachable:
f194 ~ » dig loewe-sp.arch.suse.de +short
10.161.15.192
f194 ~ » ping 10.161.15.192
PING 10.161.15.192 (10.161.15.192) 56(84) bytes of data.
From 10.160.255.253 icmp_seq=1 Destination Host Unreachable
From 10.160.255.253 icmp_seq=2 Destination Host Unreachable
^C
--- 10.161.15.192 ping statistics ---
2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 1001ms
Therefore I've to relay on cscreen to fix this machine. A first try with rd.shell rd.break=pre-mount was unfortunately just ignored.
Updated by nicksinger almost 6 years ago
I was able to boot into a TW live rescue enviroment and discovered that the cmdline contained root=/dev/sda2. I've replaced it by root=UUID=e270dc2c-1c4a-4239-b3a5-2917b685277b.
However, after the reboot my cscreen was broken (unrelated):
ssh_exchange_identification: Connection closed by remote host
=== Command terminated with exit status 255 (Mon May 7 13:37:49 2018) ===
Connection closed by 10.161.0.107 port 22
=== Command terminated with exit status 255 (Mon May 7 13:45:19 2018) ===
Updated by nicksinger almost 6 years ago
- Status changed from Workable to In Progress
I was able to fix it by regenerating the initramfs from a TW rescue system. Afterwards it accessed the disc by UUID. The non-persistent br0-config was also fixed at this occasion.
Updated by nicksinger almost 6 years ago
- Status changed from In Progress to Feedback
Updated by nicksinger almost 6 years ago
- Status changed from Feedback to Resolved