0

I have been using systemd for about a month without any problems on my Debian Jessie. I installed it according to the Debian wiki. But all of a sudden today I got this error:

   ss of error

Original: http://i.imgur.com/DWqZVIz.jpg

How can I fix this?

7
  • are you sure it's not your hard disk? – JohannesM Feb 13 '14 at 1:02
  • 4
    That looks a lot more like a physical disk problem (or your disk controller) than a software issue. – casey Feb 13 '14 at 1:06
  • Agreed it looks like your HDD is dying/failing. – slm Feb 13 '14 at 1:10
  • I would immediately run something like HDAT2 or Spinrite on the HDDs. See my prior A's: unix.stackexchange.com/search?q=user%3Ame+hdat2 – slm Feb 13 '14 at 1:13
  • here is a more vertical picture of the errors: i.imgur.com/MHqvI86.jpg (excuse the quality) – sterz Feb 13 '14 at 1:17
1

The lack of systemd is the point where the system gave up because there was no more way to recover. When you see a series of errors, you need to go backward until you hit the root cause.

The lack of systemd was due to an inability to mount the root filesystem.

mount: mounting … on /root failed: invalid argument

This inability to mount was due to the block device containing the root filesystem (which here is identified by a UUID) not being available.

It is highly likely that the block device in question is a partition on the disk concerned by the error messages immediately above. A series of messages like

end_request: I/O error, dev sdc, …

is a bad sign about the disk that is identified as /dev/sdc. The CPU detects that a disk drive is present isn't able to read data from the drive. The cable or the drive is failing (or, a lot less likely because you'd have noticed before, the driver is buggy).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.