Returning to my office after the Easter break, I found machine Bach had frozen - no activity at all. On reboot, there was a message "Cannot
start mdmonitor.service". Seems mdadm.config suddenly needs a MAILADDR
entry. Next reboot, freezes on "Checking for new hardware". Gave up but
left it switched on. Today, added "nomodeset" to grub line, now I get "checking for new hardware [ OK ]"
but it still freezes. The blue "disk activity" LED flashes irregularly
so there is still something going on.
But, this is the bizarre bit: I got a confirmation email from Bach at
04:06 this morning saying the daily dnf run had upgraded 9 packages!
(Machine Haydn next door to Bach upgraded 10 packages)
Thoughts:something has upset the video setup so startx can't/won't work? Can't rule out fiddle fingers, because my grandson slept there for a
couple of nights - 17 so he should know better, but still, he's a boy.
Any ideas anyone please?
On Tue, 07 Apr 2026 11:04:26 -0400, Grimble <grimble@nomail.afraid.org> wrote:Thanks, Dave. I found a depressing number of red/orange lines in the
Returning to my office after the Easter break, I found machine Bach had
frozen - no activity at all. On reboot, there was a message "Cannot
start mdmonitor.service". Seems mdadm.config suddenly needs a MAILADDR
entry. Next reboot, freezes on "Checking for new hardware". Gave up but
left it switched on. Today, added "nomodeset" to grub line, now I get
"checking for new hardware-a-a-a [-a OK-a ]"
but it still freezes. The blue "disk activity" LED flashes irregularly
so there is still something going on.
But, this is the bizarre bit: I got a confirmation email from Bach at
04:06 this morning saying the daily dnf run had upgraded 9 packages!
(Machine Haydn next door to Bach upgraded 10 packages)
Thoughts:something has upset the video setup so startx can't/won't work?
Can't rule out fiddle fingers, because my grandson slept there for a
couple of nights - 17 so he should know better, but still, he's a boy.
Any ideas anyone please?
Boot to run level 3 by appending " 3" to the boot time command line
options, and check
"journalctl -b -1 --no-h" to see what messages there are.
Just fyi, run level 3 is a symlink for multi-user.target.
Regards, Dave Hodgins
Thanks, Dave. I found a depressing number of red/orange lines in the journal, including:
Advice to switch to NetworkManager (not my problem surely?)
"Argh! No valid geometry found" for each of my 3 Raid5 discs
HDIO_GETGEO on /dev/sda succeeded (also sdb, sdc, sdd), followed by
running blkid -o-a udev -p /dev/sda1 etc etc
unknown line (DRIVER2_NEEDS_OPEN_KERNEL_MODULES-a-a-a (8 times)
kvm_amd: SVM disabled (by BIOS) in MSR_VM_CR on CPU3
ACI Warning: SystemIO range conflicts-a with OpRegion......
systemd[1]: mem_fdcreate() called without MFD _EXEC or MFD_NOEXEC_SEAL set
I guess the place to start is to check all 4 disks for errors.
Graeme
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 65 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 00:53:22 |
| Calls: | 862 |
| Files: | 1,311 |
| D/L today: |
10 files (20,373K bytes) |
| Messages: | 264,186 |