tomscharbach
i just figured out the error shows Buffer I/O error on dev sda, logical block 2
the error is in dev sda which is my hitachi(320gb)

is there any way i can stop system to access this hard drive ?

      is solus on the 320 gb hard drive or the 32 gb solid state drive. looks like the 320 gb hard drive is failing . have you used Disks to check the drive? Disks comes preinstalled on Solus. look for it in the menu and open it. next click on the 320 gb drive and then click on the hamburger ( 3 dots) menu and chose drive test from sub menu. it should tell you if your drive is okay . but from the readout you posted above i would say the drive is failing . can you remove the 320 gb hard drive from the system and leave only the 32 gb solid state drive ? once you do that reinstall solus on the 32 gb ssd and see if your problems are still present. good luck

        mw42815

        Solus budgie is installed on 32gb ssd (Samsung) and yes the drive with 320gb(Hitachi) has lot of bad sector and it starts to click when it is mounted. If i mount it and try to repair or run test i belive the os(solus) might crash. I tried to remove bad sectors in windows and the drive started to make clicking sound. I have no problem in deleting 320 gb hard drive and it doesnt have any of my data. I dont want to remove 320gb hdd manually i just want solus to not access it and try reading it.The problem with manually removing is that i am not good at disassembling laptop if it was in pc i could have easily removed it.

            pLaYeR45 is there any way i can stop system to access this hard drive ?

            I don't know. Solus is set up on the 32 GB Samsung, exactly as you said, and the boot partition (sdb1) is on that drive. I don't know why Solus is trying to access the 320 GB HJitachi (sda), unless there is something in the BIOS boot process that looks for a boot partition on sda first, and then, not finding a boot partition on sda, looks to sdb, where it finds the boot partition. But that is just a guess, and not an informed guess.

            pLaYeR45 I have no problem in deleting 320 gb hard drive and it doesnt have any of my data. I dont want to remove 320gb hdd manually i just want solus to not access it and try reading it.The problem with manually removing is that i am not good at disassembling laptop if it was in pc i could have easily removed it.

            I spent the morning coaching one of my grandsons through the process of disassembling his laptop so that he could install more RAM. He was all thumbs at first, of course, but as we went through the process, he got more confident and more skilled. But his laptop is an older Dell Latitude I gave him, and it has a metal case designed for easy disassembly. I'm all thumbs myself when it comes to the plastic cases, even though I've done it many times and have the plastic tools needed for the job. So I understand what you are saying.

            I have two thoughts that might help.

            (1) Go into BIOS (this document is a resource to find the right key combination to get into BIOS if you don't know it for your laptop) and see if you can disable the 320GB hard drive in BIOS. I can do it on my Dell computers, but BIOS capabilities vary, so you might not be able to do so. If you can disable the drive in BIOS, Solus might not look to it at all during the boot process.

            (2) If that doesn't work, and nobody else comes along with a better idea, you are probably going to have to get the drive out of the machine (better yet, replace it with a cheap SATA 2.5" SSD). That means you will will have to disassemble the laptop. Because I am not good at cracking the case on plastic laptops, one of the things I do is look for a YouTube video showing how to open the case for the make/model I'm working with, or a make/model that is close. There is usually a trick to it (start at a specific point, and so on), and once I know the trick, I can usually do it. Another possibility is to see if you can find a friend who is good at this stuff and get your friend to do it for you.

                  Try wiping the disk do not reformat it or anything just wipe it and try that system I think would not
                  see it then. (may not wipe if its to far gone)
                  I havent wiped any disks with linux not sure of program in linux maybe somebody knows
                  If the hitachi has any boot info on it the uefi probably grabbing it and causing the hang.
                  But I would do Like tom said disable it in bios,and I dont know your boot sequence either if that disk is first in list might be hanging it. Best thing do is remove it from laptop.

                    tomscharbach
                    No option found in bios to disable the hdd

                    Lets see if i can manually take out the hdd.

                    Axios
                    The problem is if i try to mount and clean the hdd. The laptop starts to make clicking noise and becomes very slow and unresponsive.

                    Btw thanks for helping me out is there any way i could close this discussion?

                          pLaYeR45 The problem is if i try to mount and clean the hdd. The laptop starts to make clicking noise and becomes very slow and unresponsive.

                          That clicking noise is the hard drive's death rattle.

                          Axios I dont know your boot sequence either if that disk is first in list might be hanging it.

                          @pLaYeR45 Consider going back into your BIOS, look for a BIOS entry labeled "Boot Sequence" or similar, and look to see what boot loaders are present.

                          Solus boot loader is normally called "Linux Boot Manager", Windows boot loader is normally called "Windows Boot Manager", and other Linux builds (the ones that use Grub) are called by different names (for example, on my computer, Ubuntu Budgie's bootloader is called "Ubuntu").

                          If you can identify the Solus boot loader (simple if it is named "Linux Boot Manager"), try two things: (1) move the Solus boot loader to the top of the boot sequence list, and (2) if your BIOS permits, see if you can disable/remove all the other boot loaders from the list. Either might move the Hitachi hard drive out of the boot path.

                                tomscharbach
                                My laptop's bios boot sequence consist hard drive names and LAN. Yes the priority is set in
                                1.Samsung 32gb ssd
                                2.LAN
                                3.Hitachi 320gb hdd
                                I searched on how to totally disable hdd and its says
                                The commands only run with root. I will try this method after completion of my upcoming exams.btw i was wondering if i can delete drivers for hard drive?

                                    tomscharbach knew what was on my mind...
                                    Yup click of death...

                                    pLaYeR45 I searched on how to totally disable hdd and its says
                                    The commands only run with root. I will try this method after completion of my upcoming exams.btw i was wondering if i can delete drivers for hard drive?

                                    Don't try this at home ... 😆

                                    Good luck on your exams.

                                      I did not comment To deep on UEFI because I only have 2 computers that use it out of all my windows machines
                                      and its something I am reading up on and finally this new machine I got has all the boot loader stuffs I read
                                      about on here (I am slow at change if it works I dont change it..lol) cant wait to mess it all up either...ROFL!

                                      This was good reading the guy works at Redhat..
                                      https://www.happyassassin.net/posts/2014/01/25/uefi-boot-how-does-that-actually-work-then/

                                        Axios I made the decision to use UEFI and disable CSM on all my computers, and use GPT formatting on all drives in my computers, several years ago. I will not install any OS that is not fully compatible with UEFI, period. If an OS is that far behind the curve, I don't trust it not to be behind the curve in other important respects.

                                        That sounds very dogmatic, I know. However, for the reasons explained in the article you posted, UEFI handles multi-boot, single-OS-per-disk setups more reliably than BIOS, in my opinion, and I have not had an issue with multi-boot on any of my computers since becoming hard-nosed about UEFI-only and following the single-OS-per-disk convention.

                                            Axios Not sure in my mind why installing kde solved your issue or just the way they install something I got to think on awhile.

                                            I wonder, too. It seems to me that the Solus, rather than either DE, controls the boot process, in the sense that whatever happens during the boot process to access the defective Hitachi drive precedes activation of either DE, so there should be no difference.

                                            Specifically, I wonder whether the Budgie issues would have been resolved by a clean -- that is, wipe the entire drive and start over from scratch -- installation of Budgie. I can't think of a reason why Budgie would try to access the defective Hitachi drive during boot and KDE would not.

                                            But speculating is water over the dam because the system is now working until the Hitachi blows up and causes the next problem.

                                                7 months later

                                                I don't mean to bump this thread but I also seem to be running into the same issue as a new user 😅
                                                I'm running Solus KDE on my desktop and using a 2tb Seagate SSD, with Solus being the only OS on it yet it takes about a minute and a half to get from bios to login screen. I've got a newer system with a Ryzen 5600x, where Windows on a different SSD only takes a few seconds to boot. I put Solus Budgie on my laptop as well and it boots in 8 seconds or less while being the only OS on the SSD there. I was able to run those logs the other day and see quite a few red and yellow lines throughout, but I'm not entirely sure what they mean. It doesn't seem like the forums like me uploading the logs as .txt files or .pdfs, so what would be the best way to share those?

                                                If someone could run the following it'd be really helpful for troubleshooting exactly what's taking so long.

                                                sudo journalctl -b0 --no-pager > boot.log
sudo systemd-analyze blame --no-pager > blame.log

                                                And then upload those to hastebin or something. You should skim your boot.log for anything sensitive that you might want to redact before doing this.