System startup does not continue after hard disk detection.

English Install/Boot/Login
#1

Yesterday I saw “a surprise” on my current Tumbleweed (or “factory”) system after a reboot.

It seems that the system startup does not continue after hard disk detection.

  OK  ] Started Show Plymouth Boot Screen
  OK  ] Reached target Paths.
  OK  ] Reached target Basic System.
  OK  ] Found device "disk 1"
  OK  ] Found device "disk 2"
  OK  ] Found device "disk 3"

Now I am very curious to find and resolve my technical difficulties here.
How are the chances to fix this error?

#2

On 2014-12-08 04:46, elfring wrote:
>
> Yesterday I saw “a surprise” on my current Tumbleweed (or “factory”)
> system after a reboot.

Then please ask a moderator to move your post to the tumbleweed forum.
Use the triangle button.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

#3

Can explanations be found for the observed trouble also without the suggested movement?

#4

On 2014-12-08 06:16, elfring wrote:
>
> Can explanations be found for the observed trouble also without the
> suggested movement?

I’m sorry, but Tumbleweed has specific problems, brand new problems,
often different than those from the stable release. You have to ask the
people that are using that (experimental) release.

If your problem description suggested anything to me I would have said
it, of course, regardless of version.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

#5

A few hours later I was also surprised by an abrupt system shutdown. It was determined by a detailed hardware analysis yesterday that my power supply unit and graphic card became accidentally broken.
I replaced these components so that my computer runs mostly as expected again.

How are the chances to fix this error?

Further technical adjustments will be needed to get my openSUSE installation running again as usual.

Another boot try brought this system start a few steps further a moment ago. It seems that it hangs after “a pause” at the following step so far.

  OK  ] Reached target System Initialization.

I would appreciate your help and further advices.

#6

Bad shut down do to failing power supply can cause major problem with file systems

Basically you need to run fsck program agenst each partition. The best way is to use a live Linux boot with the same OS and ver then in a console as root run fsck against each Linux partition.It may be able to fix things but note that if too bad it may not be able to peace things together. You will find the file fragments that it could not deal with in the lost&found directory. In theory thing can be glued back together but practically it is not worth the time.

#7

Since it is Tumbleweed, you are more likely to find help in the Tumbleweed forum.

#8

I observed during a few more boot tries that the achieved system startup step depends on the specification of the parameter “quiet” from the kernel boot command line somehow.

It can also happen that the openSUSE startup hangs on my computer after the display of messages like the following.

...
[136.687587] end_request: I/O error, dev sr0, sector 64
[136.691818] Buffer I/O error on device sr0, logical block 8