pLaYeR45 Did i just break the system?

Who knows, but your system isn't working right. None of the terminal commands we've been discussing in this thread could break anything. I doubt you broke anything. Something is wrong with your installation.

pLaYeR45 Do i need to install it again?🙁

If I were you, I would at this point. Your current installation isn't working and a reinstall might be the simplest solution.

If you decide to install again, don't do anything fancy. When you get to "How should I install?" point in the installation process, select the "wipe the entire drive and install a fresh version" option rather than the "install along side existing operating system" option. I don't remember the exact words, the but the choice should be obvious. The idea is to completely wipe your drive and start fresh.

        tomscharbach
        Yeah i will try to reinstall. I'll let u guyz know if the boot problem still exist after reinstallation🙂 btw thanks for helping me

          tomscharbach
          UPDATE: just reinstalled solus

          ran sudo journalctl -b
          found many red lines after reinstallation

          Apr 24 20:28:01 solus kernel: blk_update_request: I/O error, dev sda, sector 2 op 0x0🙁READ) flags 0x0 phys_seg 1 prio class 0
          Apr 24 20:28:01 solus kernel: Buffer I/O error on dev sda, logical block 2, async page read
          Apr 24 20:28:01 solus kernel: ata1: EH complete
          Apr 24 20:28:04 solus kernel: ata1.00: exception Emask 0x0 SAct 0x10c000 SErr 0x0 action 0x0
          Apr 24 20:28:04 solus kernel: ata1.00: irq_stat 0x40000008
          Apr 24 20:28:04 solus kernel: ata1.00: failed command: READ FPDMA QUEUED
          Apr 24 20:28:04 solus kernel: ata1.00: cmd 60/01:a0:00:00:00/00:00:00:00:00/40 tag 20 ncq dma 512 in
          res 51/40:01:00:00:00/00:00:00:00:00/40 Emask 0x409 (media error) <F>
          Apr 24 20:28:04 solus kernel: ata1.00: status: { DRDY ERR }
          Apr 24 20:28:04 solus kernel: ata1.00: error: { UNC }

          the following same red line alternating continued for like 2 min with different logical block.
          is my ssd full of bad sectors?

            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.