Sunday 3 January 2021

Annoying

This morning I found my VM I use for my web development work wouldn't boot. When I viewed it in Virtualbox it would get as far as EXT4-fs error loading journal then stop. Unlike my previous issues I've had, it wasn't even getting as far as being able to mount the filesystem read-only.

I first ran a Windows chkdsk on the physical disk the VM HD was stored on, which said it fixed some issues. I then rebooted the PC, but still had the same issue on starting the VM.

With no way to get to a console with the VM in its current state, I had to wait for ages while I downloaded an Ubuntu ISO, as I didn't have a linux ISO handy to boot the VM from. After eventually getting that downloaded, I booted from that and ran an fsck, which fixed various issues. I also ran e2fsck -C0 -p -f -v /dev/sda1 as per Fix EXT4-fs error loading journal - I'm not sure if this step was necessary, but I thought it wouldn't hurt to run it since the error I was getting was related to this.

With this done I managed to boot the VM okay.

While I was waiting for the Ubuntu ISO to download I decided to take a look at an HP Pavilion 360 laptop that I'd reinstalled Windows on but was missing some drivers. From looking up the vendor and device IDs for the missing drivers I knew these were the Intel Bluetooth and Trusted Execution Engine drivers. The drivers on HP's website (both Win 10 and Win 8) didn't work, neither did any Intel drivers I could find.

Both HP and Intel's software that is meant to automatically find and install updated drivers for your system didn't find the correct drivers either. (Actually the HP software was one of the first things I installed on it when first setting it up after reinstalling Win 10, and it only found 1 driver I think out of the many that were needed).

The drivers listed on HP's website for the laptop seem pretty bad - the card reader drivers didn't work and I ended up having to find some from a Lenovo website to install.

So today I figured I'd put back in the original drive (I replaced the original SSHD with an SSD to try and speed the laptop up as it is extremely slow, though it didn't actually help much). Then in device manager view the driver files for the bluetooth and TXE devices, find them, and copy them. Then put the SSD back in, and install the copied drivers.

But after getting the laptop unscrewed and apart, and removing the SSD, I realised that this was a pretty stupid way of doing it. Why not just boot off the SSD, have the original disk on a USB to SATA dongle, then tell Windows to look for the drivers on the original disk. So I tried that but the original disk kept losing connection.

So I ended up having to plug the original disk via SATA to USB into my PC, copying the system32 (and I also copied the system and SysWOW64 dirs in case) onto a USB stick, then putting that USB stick into the laptop so it could grab the drivers from there. Thankfully though, this did work and I now have all the drivers on the laptop.

Before finishing with it, I ran hwinfo on it to see if the CPU temps were getting really high, but they weren't. Around 40-50 when idle, or 50-60 when watching a YouTube video. So I still don't know why it's so slow.

I did manage to get some work done in the afternoon. Then in the evening I had an annoying issue where I couldn't get one of my local dev sites I was trying to work on to load. So I spent ages trying to fix that, in the end it turned out that some of the .htaccess rules had been removed, messing things up. This was with a WordPress site, I presume either WordPress or a plugin had updated the file and removed some of the rules needed for the site to be accessible. This must've happened at least a day ago as my backup from yesterday was the same, I had to grab the .htaccess file from the live site to get my local site up and running again.

So I didn't get much work done today, but it wasn't a total disaster / waste of time.

No comments: