Linux not booting up receiving error

Mike FYI

Forum Assistance is for asking questions about this Forum and how it displays, etc., not for support questions on Linux.

I am moving this to the Other Distributions subforum.

Cheers

Chris Turner
wizardfromoz
 


If it's an E5 series acer, it is reasonably easy, and would take me under 5 mins to swap, but I would expect you to take your time and be extra careful, and take about 15 mins, the only tools you need are the right size screwdriver,
turn laptop over, remove battery, remove the screws from the long plate being careful when you un clip it, remove the 2 retaining screws to the hard drive caddy slide and lift out hard drive, now remove the 2 retaining screws holding the HDD to the caddy and note which way round it is fitted, remove old HDD, place in new HDD and then reverse everything you have just done. Do not over tighten any screws, or you could damage the plastic post they screw into.
 
Last edited:
KGIII said:
Yours is old enough so that it *might* have it's own access panel on the bottom of the laptop. It'll be like one screw, maybe more, and the panel will open and the drive can be swapped in a few minutes.

This is not true for all modern laptops, but it's worth flipping your laptop over and looking. You can also put the model number into your favorite search engine and someone's sure to have replaced the drive on it and put directions - perhaps even video - online.
Click to expand...
I have never owned a laptop that didn't have an hdd compartment with a screw. My current Inspiron I bought was 2016ish. I assumed NVMe ssds would be onboard... But wait, hdds, like mechanical storage? Iinside the main chassis? That's asking for shite to break... hmm, then you'd need a new one... Oh, I see what they did there, lol.

Sudo It said:
As other folks already mentioned, buy a ssd not a hdd. It is bit expensive but you are going to be very glad later you made that choice since ssd's have more life expectancy and also have better write and read results
Click to expand...
For mobiles, yes, no moving parts. For desktops, I keep my OS and software on an SSD and my LT data on an HDD with a clone. Usually, I do my work on my HDD, too, but when I can grab a new NVMe, I'll put the OS on that and work on the regalur SSD and only use the main HDD for archiving and DB. I trust HDDs more with LT storage and they're cheaper per TB, plus they have better redundancy coz they support constant writes/reads better -- something you need with 2x 8TB (1 main, 1 backup). So I think life expectancy is more use-case specific. I could never go back to booting from an HDD on my main machine, though, let alone running my OS.
 
Mike Oxmall said:
Ill don't even know how to check the diagnostics im that basic at this stuff
Click to expand...
It's pretty simple and a good opportunity to learn essential know-how.

For example:
// check and repair XFS partition
# xfs_repair /dev/sda1
// check and fix EXT* partition
# fsck /dev/sda1
// Specify it is EXT4 explicitly (99% will be in now on 2022)
# fsck -t ext4 /dev/sda1

If there are still warning/errors starting an X session from your live boot, it's likely hardware (not necessarily broken, could be missing firmware of some weird GFX card with an unheard of GPU -- wouldn't surprise me to see some video cards with Mediatek chips clustered on them from China after some of the hardware I've seen on Linus Tech Tips -- otherwise you botched drivers, config, etc. on your local install.

If your sound now works, same as above.

... And so on. A lot is deductive reasoning to narrow a cause. It's worth learning. It'll save you time and money. Consider it an investment.
 
Big thanks guys, I will probably opt for a SSD then and buy it online, but before I do I will take a pic of the back of my laptop and post it here so I can be sure to get the correct SSD later.
 
Fanboi said:
// Specify it is EXT4 explicitly (99% will be in now on 2022)
Click to expand...

Not too sure about that. Redhat and clones use XFS by default. Fedora workstation uses EXT4, but Fedora server uses XFS by default. OpenSuSE uses XFS by default.
 
dos2unix said:
Not too sure about that. Redhat and clones use XFS by default. Fedora workstation uses EXT4, but Fedora server uses XFS by default. OpenSuSE uses XFS by default.
Click to expand...
I meant "[of the EXT* family filesystems] 99% use EXT4". Context was: fsck could guess, as I said in the comment above, or be explicitly stated as in this example (oh, BTW, you likely won't need to since most EXT systems are 4 and I'll add an arbitrary percentage that means "a shitload")... That kinda thing, lol.
 
First Error is No IRQ handler for Vector

This is usually caused by the IOMMU being set to Auto or Enabled in EFI/BIOS. Disabling it gets rid of the error messages

Second Error

Problem Loading X.509 certificate -65

It might be a bad disk. This can happen for new or existing installations.
To verify that your disk works properly you can use next commands:
Code: 
sudo fdisk -l

This is my output from the above command

Disk /dev/sda: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: Micron_1100_MTFD
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x65739f47

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 1050623 1048576 512M b W95 FAT32
/dev/sda2 1050624 500117503 499066880 238G 83 Linux

Now that we have identified our disk as /dev/sda we need to check for badblocks on that disk
Code: 
sudo badblocks -sv /dev/sda
Note: that this process might take time for bigger disks!
If badblocks are detected we can try to fix them by running
Code: 
sudo fsck /dev/sda1
 
4
Lord Boltar said:
First Error is No IRQ handler for Vector

This is usually caused by the IOMMU being set to Auto or Enabled in EFI/BIOS. Disabling it gets rid of the error messages

Second Error

Problem Loading X.509 certificate -65

It might be a bad disk. This can happen for new or existing installations.
To verify that your disk works properly you can use next commands:
Code: 
sudo fdisk -l

This is my output from the above command

Disk /dev/sda: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: Micron_1100_MTFD
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x65739f47

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 1050623 1048576 512M b W95 FAT32
/dev/sda2 1050624 500117503 499066880 238G 83 Linux

Now that we have identified our disk as /dev/sda we need to check for badblocks on that disk
Code: 
sudo badblocks -sv /dev/sda
Note: that this process might take time for bigger disks!
If badblocks are detected we can try to fix them by running
Code: 
sudo fsck /dev/sda1
Click to expand...

Hi mate 4 bad blocks were found i tried to repair them but unfortunately I don't think it worked. I cant even copy and paste as the internet doesnt seem to working either
 
You must log in or register to reply here.

Members online

Total: 616 (members: 3, guests: 613)

Latest posts

Top