ok I’ll do that, but what happened here? I was expecting no more issues once I used a new drive. If I just reinstall again using livemedia, is this going to persist?
The first block of a disk or of a partition is called the superblock. A superblock can be damaged for example in a sudden power outage, but there are backup copies of the superblock in a block group. Let’s hope fsck will repair it.
omg, I hope fsck will, because I just invested some for an SSD. ok I’ll do what you said, I just inserted the SSD just yesterday and tried to install, the SSD hasn’t experience a Power outage yet.
I was thinking it got affected by the previous HDD because of the phrase “ACPI Error Aborting method due to previous error” but I’m no Expert.
The message /dev/sda2: clean, 286631/6111232 files, 2586472/24413952 blocks has the following meaning:
The partition that was checked is “/dev/sda” The file system is “clean”, i.e. there are no inconsistencies “286631/6111232 files”: The file system has been created to allow a maximum of 6,111,232 files, and currently there are 286,631 files, “2586472/24413952 blocks”: The storage capacity of the file system is 24,413,952 blocks (probably 4096 bytes each), and 2,586,472 blocks currently are in use.
This is an informational message confirming that the file system is ok. There is nothing that needs to be resolved or repaired.
While I honestly don’t know what to do about it, according to this website:
ACPI specifies how a computer’s basic input/output system, operating system, and peripheral devices communicate with each other about power usage.
So it seems to me, that the error is caused by something to do with power usage. I don’t know what, though. Could be the power supply, in fact, it probably is. Not an official diagnosis, but that’s my opinion.
Edit:
I really don’t think you have anything to worry about, from the message you provided, it seems it’s caused by a bug, not a fault with your system.
I see, if that’s the case, then it’s pinpointing my Battery because it has gone bad and I have salvage it last year for my flashlights.
I also found this, so I’m trying to go for an LTS Kernel (anyway, I’m always on LTS). It’s quite a recent issue, that’s why I have been wondering, I though I had a bad SSD. Phew.
I just really want to restore my daily driver without any issues and then I stumbled on this ACPI Error and fsck checks that I never saw before.
This annoying message is caused by fsck on recent installations (because by default there is the fsck hook in mkinitcpio). You can hide it by forcing a different log level in grub parameters (but that might hide other messages too, to be verified).
But in my opinion this message shouldn’t be shown at all when there is no issue during the check (which is the case here from the message), I think it is a problem from fsck itself outputting a ‘warning’ type of message for what should be a simple ‘notice’.
For the ACPI messages though I can’t really tell. Maybe trying other kernel can help.
It is definitely annoying as when you set quiet splash Grub boot parameter, it doesn’t respect it, and shows you this message to say ‘nothing wrong’. This is dumb.
It’s always amazing how people get annoyed by such a simple and short message. Are you booting your system every half hour? Why is it so difficult for you to simply ignore it?
It is annoying because I set my system in a specific way, no boot message, and splash screen of my motherboard until I reach desktop, and if I let this as is, it “breaks” my configuration because it forces output of a console message when it shouldn’t (there is no error so why should it give a Warning message? default log level is 4 in Manjaro right? So this is a level 4 log message?).
I could have same way of thinking with your reply: “why are people so annoyed by people affected by an illogical issue”.
//EDIT: ho I see, clicking the yawning emoji is the best you can reply to that… take this -1 emoji then. I gave you proper points about why it is annoying, you can’t beat that because this is an actual issue and makes no sense.
