Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Yesterday when I got home, my laptop was acting crazy, programs were not working properly. First time I have seen that. I thought 'reboot and everything will be ok'.
When I did, I ended up in initramfs. It said 'you need to run fsck manually' I guessed and entered fsck /dev/sda9 (which is the partition for Ubuntu 16.04) fsck found various orphaned inodes, whatever that is, and afterwards I could boot again.
Does this mean my HD is going home? Time to buy a new laptop? This one is 3 years old. What causes the system to drop to initramfs?
During the day I often just shut the lid on the laptop at the end of a class. That, combined with connecting to overhead projectors might get the system confused I suppose.
Orphaned inodes are benign and perfectly normal whenever you have an unclean dismount. They are simply files that had been deleted, but were still open when the fs was remounted read only. They are not the cause, but merely a symptom. You need to check your kernel logs to see what the actual problem was that caused the read only remount. You also might want to run some SMART diagnostics to make sure the drive isn't failing.
ohdoho's answer was good, but I don't believe it provided a technically complete answer to this question. It dropped to initramfs because the root filesystem had errors that could not be automatically corrected. Thus it could not be mounted, which left you with only the filesystem and tools contained within the initramfs to work with. "Acting crazy" before rebooting could very well mean the HD is "going home", which is more likely than the whole laptop going bad.
During the day I often just shut the lid on the laptop at the end of a class.
This is the likely cause if you run out of battery after closing the lid.
Make sure you have you power events set correctly - I haven't used Ubuntu in years, so I can't advise.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.