Re: Had a major issue with machine not booting fully.

"Michael D. Setzer II via users" <[email protected]>
Newsgroups gmane.linux.redhat.fedora.general
Message-ID <[email protected]>
On 27 May 2026 at 7:43, Sam Varshavchik wrote:

From:	Sam Varshavchik <[email protected]>
To:	Community support for Fedora users <[email protected]>
Subject:	Re: Had a major issue with machine not booting fully.
Date sent:	Wed, 27 May 2026 07:43:16 -0400
Send reply to:	Community support for Fedora users <[email protected]>

> Michael D. Setzer II via users writes:
> 
> > Had a typhoon go thru, and power was out for 6 days.
> > All but one machine came up, but power is still having lots of
> > issues.
> >
> > The one machine that wasn't booting had its power supply get fired,
> > but replacing it got machine to start booting, but would just hang.
> > Would not boot from default kernel or others, and not with rescue.
> > Machine would boot fine from my g4l kernel and its initramfs with
> > no problem. So grub is working. Ran fsck on all the partitions, and
> > it fixed some minor things on some. But reboot still was hanging.
> 
Did bit level copies of partitions sda1 sda2 and sda3 (/boot swap / )
so should be no corruption in any files. The G4L files boot just fine, 
but it is a smple kernel and initramfs boot. Doesn't use UUID or 
other things.

Changed fstab to make sure all blkids match from partitions.
Machine 103 has duplicate partition except for the /home partition.

> There's no such thing as "minor things" when it comes to filesystem  
> corruption, especially when it results from a power loss.
> 
> Your filesystem suffered unknown corruption and damage. The list of possible  
> reasons why the system fails to boots is an infinite list.
> 
> Your only realistic option for you is to boot from a live image, mount the  
> partitions, copy whatever files you find, and need, to a USB stick, then  
> reformat and reinstall from scratch.
> 
> Don't be surprised if you find that some of the files are bad, and are  
> filled in whole or in part with random binary garbage. Take that  
> observation, apply it to the kernel, the ramdisk, and everything you find  
> in /bin and lib(64)?, and you pretty much have a good idea of what's  
> happening.
>
 
> When things are back to normal, consider investing in a UPS, that will give  
> your systems time to shut down normally in the event of a power loss.
> 
Machines all have UPS units, but typhoon had power or for 6 days. 
Even now the system has outages. On this notebook, I create a full 
disk image of drive about once a month. My G4L takes the 1TB 
boot drive /dev/sdb and creates a raw image file of about 70G 
containing all the data of partition in about 30 minutes.

sfdisk -l /dev/sdb
Disk /dev/sdb: 953.87 GiB, 1024209543168 bytes, 2000409264 
sectors
Disk model: Fanxiang S101Q 1
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: gpt
Disk identifier: 70647742-8953-40B3-8BDE-1C14F7B6D51B

Device          Start        End    Sectors   Size Type
/dev/sdb1        2048    1230847    1228800   600M EFI System
/dev/sdb2     1230848    4376575    3145728   1.5G Linux filesystem
/dev/sdb3     4376576  192071679  187695104  89.5G Linux 
filesystem
/dev/sdb4   192071680 1590808575 1398736896   667G Linux 
filesystem
/dev/sdb5  1590808576 2000408575  409600000 195.3G Linux 
filesystem

Latest image file.
68640583757 Apr 26 16:35 /data2/sdb-zst-test2.zst

Looks like time to create a new one.

Again, Thanks for info.

> 


+------------------------------------------------------------+
 Michael D. Setzer II - Computer Science Instructor (Retired)     
 mailto:[email protected]                            
 mailto:[email protected]
 mailto:[email protected]
 Guam - Where America's Day Begins                        
 G4L Disk Imaging Project maintainer 
 http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+



-- 
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.