superdecker64 The thing that trips most folks up seems to be the UEFI/BIOS thing. Always worth a quick look at a tutorial here just to make sure you are on the right track.
If you are hoping to dual boot with Windows there are various hibernation variants that make any access to the hard drive more difficult. Always make sure you have shut down fully from windows. This should be adequately discussed elsewhere on this forum.
issue installing souls
BuzzPCSOS I did look up how to check and my PC is definitely running on UFEI. Tried etcher and still no luck. I've checked a few tutorials but I don't think I've looked at one on this form specifically, mostly just the official guide, reddit, and some from YouTube.
Hmmmm, if I completely wipe my PC of windows and everything would that help at all? I'm not looking to dual boot for the moment, the only thing I think I'd outright need windows for is VR with oculus and I probably need to wait till I can build my own PC for that. I have a laptop I can use to make a new windows install media afterwards if it fails
BuzzPCSOS after a few more attempts, I think I'm gonna give Linux mint a shot for now and try Solus whenever I get around to building my own PC. Thanks for your help, and sorry for wasting your time
- Edited
superdecker64 Hardware issue try noacpi in the live boot. (noapic is wrong no such thing)
Oh just saw your current post nobody wastes our time everybody is here to help and everybody
usually learns something in the process to.
good luck
- Edited
Axios Hardware issue try noacpi in the live boot. (noapic is wrong no such thing)
I think I trust the Red Hat documentation more than you.
https://access.redhat.com/solutions/58790
According to that document there is in fact no such thing as noacpi, while noapic very much exists. What you mean would be acpi=off, as mentioned (and tried) by the OP.
@superdecker64 I hope that you have an easier run with mint, feel free to come back and ask some more when you are ready. Solus is one of many great Linux operating systems and a very good choice for a newbie but also a great OS to stay with.
BuzzPCSOS hello again, have an an update! I had the same issue when trying to install mint, I then tried Ubuntu and got a similar error. After getting frustrated I just started toggling a bunch of bios settings. Probably not a great idea but it ended up working! I think I disabled the onboard sata controller and also TPM (which I know I knew what that meant at some point but I sure do not remember anymore). Ubuntu installer seems to actually load now! Gonna give Solus installation another shot and see if it works now!
- Edited
Okay it's not recognizing the drive with windows now (probably the sata controller disabling did that which yeah probably should have seen that coming xD), gonna reenable sata controller and see if it still works and tpm was the issue or if it's some weird drive issue. I've run a couple disc checks and even downloaded a disk health manager and it all ran fine so not sure why it would be the drive, it's less than a year old. Only thing I could think of is when I installed the drive I was kinda of lazy and installed it into a new slot instead of removing the old broken one because whoever designed this case really did not want the original hard drives to be removed because wow the hard drive dock area is a mess of screws.
Update: annnnd Windows is acting weird, says it lost my pin and to set it up again but everytime I try it just restarts and says the same thing, trying safe mode boot. If that doesn't work I think I'm gonna call an exorcist at this point. Don't need help quite yet, just documenting this in case someone else has this issue so they don't make the same mistakes I did
Update 3: yeahhh I think the drive is just in the process of failing. Weird since every check passed and it's only a couple of months old. Think I'm gonna expedite trying to get hands on parts to build a new PC from scratch and salvage what I can from this cause I don't really trust it at this point
- Edited
I am guessing that your hard drive is an SSD, I have had an SSD in the past which gave good smart data but was failing badly all the same. If you have a spare hard drive that can be used to try instead then that would be a good thing to try.
Edit: I have seen SSD drives on Windows with a proper installation go bad and couldn't find a reason for it. No virus, no torrenting, not a whole lot of anything except the registry was all over the place with crosslinks everywhere. Maybe an update failed at the wrong moment due to power outage or a forced restart. It could just be down to bathtub curve failure.
Also it would be worthwhile to test the ram on your PC, there may be a pre boot option to do this in your UEFI/BIOS setup utility.
[deleted]
- Edited
superdecker64 What drive is it (make/model)? Does the Solus live ISO boot if you disconnect the drive?
superdecker64 After getting frustrated I just started toggling a bunch of bios settings. Probably not a great idea but it ended up working! I think ...
Are you sure you have corrected what you did in BIOS. ? Then I would suggest go for a clean install of Solus.
- Edited
[deleted]
Western Digital 1TB WD Blue PC Internal Hard Drive HDD - 7200 RPM, SATA 6 Gb/s, 64 MB Cache, 3.5" - WD10EZEX https://a.co/d/9UKsoKP
This is the drive
Disabling the sata controller makes the live launcher boot, yeah, altough there are two drives listed despite me only using one. I thought the one that was listed was my old broken drive I was too lazy to remove but I just opened up my PC and removed it today and it wasn't actually plugged in and now both drives are still listed in the bios. I didn't see any drive in there, googling the device name brings up an SSD but I didn't see one in there and looking at my PC model up it didn't come with one, and I didn't install one, so no idea what's going on there. Is there a way to disable SATA ports individually through like a command or something so I can test whether it's the phantom drive doing this or not?
If the SSD was unplugged it shouldn't have made a difference to Solus booting, it is still worth unplugging the WD drive and trying to boot again from your USB stick with no hard drive connected.
Usually the only place your previous drives will be listed is where the bios records the path to the boot image. This should not cause any problems with booting from a USB.
[deleted]
- Edited
superdecker64 Where exactly are the drives listed in the BIOS? Is there a possibility you could provide a photo of that list containing the phantom drive?
BuzzPCSOS I think the Solus boot is waiting the broken drive for something, times out and fails the boot.
- Edited
If the defective drive was at one time set manually it would still be listed in bios probably
and not set to auto detect.
If it was set auto it should not be shown if it was unplugged.
So maybe it is hanging looking for that drive because its set manually.
Remove it in bios the defective one.
But bios should have complained about it at boot
I agree post a screen shot
- Edited
Hi, sorry for the delay, and I appreciate everyone replying! I fixed it, there was in fact an SSD installed, little bastard was hiding under the graphics card which was the only thing I didn't take out when trying to trouble shoot until now. Thing wasn't on any of the specs I saw around online and for some reason Acer took down the manual that actually showed a motherboard diagram that I used last time (to put in the drive im now currently using) and replaced it with a generic one, so there was absolutely no way I would have found that on my own, thank you Tech Deals on youtube! Anyways everything's working great now! Live loaders all work just fine, and booting up is way faster too! Windows also isn't being a weird janky mess anymore too, so it really was just that one SSD fucking everything up I guess.
Anyways thanks you all for your help! Really appreciate you all replying, helped me stay somewhat sane through the frustration lmao. I'm running the solus installer now, and it's seeming to work fine! Will pop back in if something different breaks but the original problem is resolved, thank you all for your help again and I'm sure I'll see you all around on the forum again at some point!
Off topic question, but there's nothing I can do with the broken SSD right? At this point I kinda want to buy a bunch of safety gear and take a hammer to the thing after dealing with all that lol
- Edited
Okay, already back, oof xD
So installer gets like, 70% and throws up an error saying "the bootloader could not be installed. the installation command <pre>clr-boot-managet update</pre> returned error code 1."
Here's my install log
https://termbin.com/xj5d
I think it might just be storage corruption, I had tried to install it once more before this point but while waiting for it to finish, I didn't realize the live loader auto locks after five minutes of inactivity, and while fumbling around in the password thing I think I glitched something cause it got stuck on a black screen and I had to restart. Trying formatting the drive now, but figured I'd go ahead and put the log up in case it's not the storage thing and any of you recognize it
- Edited
Rather embarrassingly, I can't figure out how to format the partition. Windows doesn't have the partition show up now (which fair enough since that's technically Linux territory even if said Linux is borked), KDE partition manager in the live loader doesn't seem to want to let me do anything with it either, there's a lock icon and the only thing selectable for it is unmount (which just tells me I can't unmount)
Sorry for the additional bother Dx
Update, restart fixed that issue, partition deleted, gonna try installing again.
Update 2: nope, same error Dx