I am experiencing a serious problem that I have no familiarity with. Hoping somebody here might be able to help.
Here's the story: Earlier today, I restarted my Kubuntu machine, as I periodically do. After the manufacturer screen had come and gone as usual, I was left with a blinking cursor, which persisted for several minutes. Normally, it takes only a few seconds for the login screen to come up, but the system seemed stuck. At last something happened. Kubuntu started spitting out what appeared to me to be a bunch of kernel errors. Lines like this:
devd-work[365]: open /dev/null failed: No such file or directory
and this:
ata1.01: exception eMask 0x0 SAct 0x0 SWee 0x0 action 0x0 frozen
ata1.01 failed command: READ DMA
ata1.01: status { DRDY }
ata1.01 cmd c8/00:08:08:08:c0/00:00:00:00/50 Emask 0x4 (timeout)
... and lots of other lines beginning with numbers and then immediately followed by "ata1.01". I couldn't write them all down because they eventually disappeared.
A sequence of errors like this cascaded several times before the Kubuntu blue screen suddenly showed up, and was replaced in turn by the login screen.
I attempted to login, and KDE loaded, but then it froze. I used the magic sysreq combination to get the computer to restart. But the same thing happens. Blinking cursor for several minutes. Then several minutes worth of error messages. Then I see the login screen. Now I can't even login. Kubuntu freezes when I try to do so.
Something is seriously wrong. That much is evident. But what is wrong, I don't know.
I tried booting into the Ubuntu Live CD (using an actual CD) but it got stuck after I clicked "Try Ubuntu". After about ten minutes I used the magic sysreq keys to again force a restart.
I next tried a USB thumb drive. Miraculously, this worked. I got in and I checked my disks using the Disk Utility. The SMART test reported the SDD that Kubuntu runs on as healthy. A filesystem check (run with the drive unmounted) also produced no errors.
I restarted again, hoping the problem might have fixed itself. It hasn't. And I am unsure as to what my next steps should be. Advice?
Here's the story: Earlier today, I restarted my Kubuntu machine, as I periodically do. After the manufacturer screen had come and gone as usual, I was left with a blinking cursor, which persisted for several minutes. Normally, it takes only a few seconds for the login screen to come up, but the system seemed stuck. At last something happened. Kubuntu started spitting out what appeared to me to be a bunch of kernel errors. Lines like this:
devd-work[365]: open /dev/null failed: No such file or directory
and this:
ata1.01: exception eMask 0x0 SAct 0x0 SWee 0x0 action 0x0 frozen
ata1.01 failed command: READ DMA
ata1.01: status { DRDY }
ata1.01 cmd c8/00:08:08:08:c0/00:00:00:00/50 Emask 0x4 (timeout)
... and lots of other lines beginning with numbers and then immediately followed by "ata1.01". I couldn't write them all down because they eventually disappeared.
A sequence of errors like this cascaded several times before the Kubuntu blue screen suddenly showed up, and was replaced in turn by the login screen.
I attempted to login, and KDE loaded, but then it froze. I used the magic sysreq combination to get the computer to restart. But the same thing happens. Blinking cursor for several minutes. Then several minutes worth of error messages. Then I see the login screen. Now I can't even login. Kubuntu freezes when I try to do so.
Something is seriously wrong. That much is evident. But what is wrong, I don't know.
I tried booting into the Ubuntu Live CD (using an actual CD) but it got stuck after I clicked "Try Ubuntu". After about ten minutes I used the magic sysreq keys to again force a restart.
I next tried a USB thumb drive. Miraculously, this worked. I got in and I checked my disks using the Disk Utility. The SMART test reported the SDD that Kubuntu runs on as healthy. A filesystem check (run with the drive unmounted) also produced no errors.
I restarted again, hoping the problem might have fixed itself. It hasn't. And I am unsure as to what my next steps should be. Advice?
Comment