On 05/18/2017 02:40 PM, William wrote:
> Good afternoon,
>
> Yesterday evening, a third IT grad student (PhD candidate specializing
> in cloud computing) came to help with this problem. After I showed him
> the log file and the discussion in this list, we booted, and of course
> it failed and dropped us into the dracut shell. He examined the
> rdsosreport.txt file. He ran "fdisk", but he typed too fast for me to
> see the whole command line. He responded 'y' to a few things, but it
> was too fast for me to see what. He then exited the dracut shell (I did
> not see him enter any "mount" commands.), and hit the hardware reset
> button. The system booted up successfully.
Are you sure he ran "fdisk" and not "fsck"? fdisk wouldn't ask for "y"
confirmations too often, whereas fsck ("file system check") that
would prompt for "y" when it was trying to fix file system errors. You
might ask your friend just what he did. This isn't a black art and
since it's your machine, you should have some idea as to what he did.
> Later in the night, I shut the system down for the night. This morning
> it booted up fine. Early this afternoon, I did the weekly "dnf
> upgrade". Since the kernel was among the things patched, I shut the
> system down, and then booted it back up again. It booted successfully.
> I'm now willing to say the core problem is solved>
> There are related questions that remain unanswered; I'll open new
> separate topics on them in the next few days. I see 10 list members
> (plus 4 off-list helpers) participated in this topic. I knew when the
> problem surfaced that this would be difficult. It turned out much more
> difficult, tedious, and time-consuming than I anticipated. But y'all
> got me through. Thank-you very much.
Just really glad you got it sorted out.
> On 05/11/2017 02:21 PM, Bill Mattison wrote:
>> Good afternoon,
>>
>> This is an f24 system. I just (about 1pm US mountain time) completed my
>> weekly "dnf upgrade", and I saw no hint of failure or trouble. But when
>> I shut down the system, and then powered back up, the boot failed. The
>> grub menu looked ok. The blue-and-white bar at the bottom of the boot
>> screen did go most of the way normally. But it never got to the log in
>> screen. There was some text being displayed, but I have no way of
>> capturing it, and I don't remember what it said.
>>
>> I'm no sys. admin. I have no idea what to do. Please help. (I'm using
>> a windows 7 system for this e-mail.)
>>
>> Thank-you in advance.
>> Bill.
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
--
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
----------------------------------------------------------------------
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
