#Polkit.service error

96 messages · Page 1 of 1 (latest)

vagrant spruce
#

So I just finished installing Arch, booted into it, and went to reboot. Get the error:

"Call to reboot failed: unit polkit.service failed to load properly, please adjust/correct and reload service manager: Input/output error" and "Failed to talk to init daemon: Input/output error"

Shutdown isn't working either. I have no idea how to fix this and Google isn't helping. Please help teach me how to resolve this kind of error

inland lotus
vagrant spruce
vagrant spruce
inland lotus
inland lotus
vagrant spruce
#

I just installed it I don't know how I'd have already corrupted it. This drive is used maybe it's faulty

inland lotus
#

What is the output from

dmesg
vagrant spruce
#

-bash: /usr/bin/dmesg: Input/output error

vagrant spruce
inland lotus
vagrant spruce
#

The only other command I've entered has been sbctl to try to enroll in secure boot

#

One sec

inland lotus
#

Can you try some common commands to see if they work at all?

vagrant spruce
vagrant spruce
#

Input output errors theyre not working

inland lotus
vagrant spruce
#

I don't it's freshly wiped

#

So far is this a borked drive situation or a reinstall situation?

inland lotus
vagrant spruce
#

It only broke after running sbctl

#

Okay I have no idea how to check I'm a total noob

inland lotus
inland lotus
vagrant spruce
#

Is it safe to do a hard shutdown it won't shut off any other way

inland lotus
vagrant spruce
#

Okay

#

So mount /dev/sda3 then fsck?

inland lotus
# 
fsck /dev/sda3
vagrant spruce
#

Oh okay

inland lotus
#

What type of drive is it and when did you start using it?

vagrant spruce
inland lotus
#

press y

vagrant spruce
#

It's a generic 2TB hard drive that I've been using for game storage for the last two or three years

inland lotus
vagrant spruce
#

Had to press y on a couple things

#

No mechanical drive

inland lotus
# 
pacman -S --needed smartmontools
vagrant spruce
#

I'm not sure, assuming that command is the tool to check with?

inland lotus
#

If the drive supports S.M.A.R.T., we can run a self-test on it.

vagrant spruce
#

That's the first half do I need to post the rest?

inland lotus
#

It will give you a URL, which you can enter here instead of taking picutres

vagrant spruce
#

Ohh. And "command" is just the command I want to run?

inland lotus
#

Yes, and in case you don't know, the | is a pipe, which is used to pipe the output of the left command to the input of the right command.

vagrant spruce
#

Gotcha I use pipes for less and that's about it lol

#

I used the command but it didn't spit out a link

inland lotus
# 
 smartctl -a /dev/sda | curl -F 'f:1=<-' ix.io
vagrant spruce
#

Don't think so

rn_image_picker_lib_temp_ec10f548-c0f6-423d-a9d4-735c85b4de67.jpg
inland lotus
vagrant spruce
#

No

inland lotus
vagrant spruce
#

Is that an @

inland lotus
#

Yes it's an @

vagrant spruce
inland lotus
#

If you are wondering what VALUE WORST THRESH means, here is an explanation from stackexchange

S.M.A.R.T. reports normalized qualitative values for Current (VALUE), Worst (WORST), and Threshold(THRESH) metrics, indicating how good or bad a metric's value is on a scale. Higher Current and Worst values are generally better, and the scale used may vary by manufacturer. If Current falls below Threshold, the manufacturer considers the drive to have failed. However, even if the value hasn't fallen below Threshold, a value under 100 on certain metrics may indicate a possible future failure.

vagrant spruce
#

Ah dip so my drive is close to failing

inland lotus
#

In a healthy drive, most of the VALUES should be 100 (except for temperature of course).

vagrant spruce
#

Gotcha

inland lotus
#

The command

sudo smartctl -H /dev/sda

can be used to display the current state of the self-test.
The self-test may take some time

vagrant spruce
inland lotus
# vagrant spruce Http://0x0.st/HeiJ.bin

Seems that 0x0.st ironically crashed

<pre>Process 24 stopped
* thread #1: tid = 24, 0x00007f1aca4cc550, name = 'fhost'
    frame #0:
Process 24 stopped
* thread #8: tid = 24, 0x00007f1b3bf97b80 fhost`get(path='/HeiJ.bin') + 27 at fhost.c:139, name = 'fhost/responder', stop reason = invalid address (fault address: 0x30)
    frame #0: {3:#018x} fhost`get(path='/HeiJ.bin') + 27 at fhost.c:139
   136   get(SrvContext *ctx, const char *path)
   137   {
   138       StoredObj *obj = ctx->store->query(shurl_debase(path));
-> 139       switch (obj->type) {
   140           case ObjTypeFile:
   141               ctx->serve_file_id(obj->id);
   142               break;
(lldb) q</pre>%
vagrant spruce
#

Okay it's not showing me the test tho

rn_image_picker_lib_temp_f16d3fa2-9b7e-4bb6-86d7-b644dd3b0faf.jpg
#

Oh wait

inland lotus
vagrant spruce
#

That's what the other command was for

inland lotus
#

You will need to wait, the drive self-test is running in the background.

vagrant spruce
#

Says it passed

inland lotus
vagrant spruce
#

Yeah

#

I think I'm just going to go to pop_os honestly, since my attempts to get arch to boot with secure boot have so spectacularly failed :/

inland lotus
vagrant spruce
#

Kk

inland lotus
#

I suggest you don't use this drive for anything important for the time being.

vagrant spruce
#

Jeez okay

#

So it looks like I'm just not gonna get to use my computer tonight :/

inland lotus
vagrant spruce
#

Okay

inland lotus
#

And I see you also have nvme drives, its health can also be checked with e.g. smartctl -A /dev/nvme0.

vagrant spruce
#

The nvmes are brand new I don't think I'm gonna run a long test on them both

inland lotus
#

Yes, but it's a good habit to check it regularly, looking for a value such as Percentage Used. If this value approaches %100, the nvme drive should be replaced.

vagrant spruce
#

Okay good to know

inland lotus
#

And Available Spare:, if this value approaches 0%, your drive will start to fail.

vagrant spruce
#

Gotcha

inland lotus
#

So let this unfortunate incident be a warning, no drive is ever reliable, check its health regularly and make backups.