On Tue, 2018-12-18 at 13:20 -0700, home user via users wrote:
> Patrick said
> > > So you're still having the problem?...
> > Yes.
> and
> > I update my system every morning. Not sure how
> > grub2-mkconfig would help.
>
> Then I think it was just a coincidence for me.
>
> This is now way ov
Patrick said
> > So you're still having the problem?...
> Yes.
and
> I update my system every morning. Not sure how
> grub2-mkconfig would help.
Then I think it was just a coincidence for me.
This is now way over my pay-grade, and way beyond my training and
experience. Can someone else help P
On Sun, 2018-12-16 at 20:24 -0700, home user via users wrote:
> So you're still having the problem? (I notice your messages are dated
> Dec. 15.)
Yes.
> Either the weekly patches (dnf upgrade) fixed the problem on
> my workstation, or just maybe doing "grub2-mkconfig -o /etc/grub2.cfg"
> to g
> > (f-28) I closed this about a year and a half ago because a bug was
> > already filed regarding the issue. For the past few days, both
> > before and after doing my latest weekly patches, I noticed that
> > those "ACPI Error" messages no longer show up while the workstation
> > is booting.
On Sun, 2018-12-16 at 15:04 -0700, home user via users wrote:
> Good afternoon,
>
> (f-28) I closed this about a year and a half ago because a bug was
> already filed regarding the issue. For the past few days, both before
> and after doing my latest weekly patches, I noticed that those "ACPI
Good afternoon,
(f-28) I closed this about a year and a half ago because a bug was
already filed regarding the issue. For the past few days, both before
and after doing my latest weekly patches, I noticed that those "ACPI
Error" messages no longer show up while the workstation is booting. S
't doing before.
I thank each of you who tried to help for your time and effort; you were
a good help.
Bill.
On 05/24/2017 09:38 AM, William wrote:
Good morning,
The "f24 boot fails; need help" problem set me back a week. I'm still
catching up. I seriously believe it woul
I think you're probably right on both counts. I thought so before my Thursday
night post, but really thought it best to check with the experts.
thanks,
Bill.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-
It's believed that the main problems were i-node problems identified by "fsck"
during boot. The first time, they were on sda6; the second time, they were on
sda7.
A few follow-up questions about the hard drive... I used the long but
non-destructive test options of both "badblocks" and "smartc
Allegedly, on or about 09 June 2017, William Mattison sent:
> * Hard drive? Somewhat unlikely. Two 4-hour non-destructive disk
> checks found no issues. System cleaned; cables dis- and re-connected;
> hard drive removed and put back in; no kinky cables seen. Destructive
> testing and replacing
On Fri, 2017-06-09 at 02:51 +, William Mattison wrote:
> I did my weekly patches this afternoon, and this time the system
> booted up fine. So I'm back to what caused the problems.
> * Motherboard battery? Quite unlikely, but not 100%
> certain. Battery replaced anyway.
> * Hard drive? Some
I did my weekly patches this afternoon, and this time the system booted up
fine. So I'm back to what caused the problems.
* Motherboard battery? Quite unlikely, but not 100% certain. Battery replaced
anyway.
* Hard drive? Somewhat unlikely. Two 4-hour non-destructive disk checks found
no is
Allegedly, on or about 03 June 2017, William Mattison sent:
> Before I took the system apart, I checked the CMOS clock and the
> voltages reported by the motherboard in the UEFI BIOS display:
> * CPU voltage varied, but was 0.98 +/- less than 0.01 volts.
> * "3.3V Voltage" was 3.392 volts.
> * "5V
Allegedly, on or about 03 June 2017, Louis Lagendijk sent:
> I have not followed this thread closely, but did you check the
> harddisk cable. They are often a source for problems...
That's certainly true. Not just badly plugged in leads, but also
ill-fitting connectors, and bent and folded SATA
The smartctl long test took about 4 hours (I think!). I wish it would notify
me when it was actually finished! As best as I could tell (by using "smartctl
-l error /dev/sda", it found no problems.
thanks,
Bill.
___
users mailing list -- users@lists.f
While changing the motherboard battery yesterday (Friday), most cables were
disconnected and then later re-connected. That included the hard drive
connection to the motherboard. I also disconnected and reconnected both the
power cable and the data cable where they plug in to the hard drive its
According to the man page, the "-n" option is non-destructive; the "-w" option
is what you described.
Regardless, it's too long.
Bill.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproje
On Sat, 2017-06-03 at 01:32 +, William Mattison wrote:
> I tried badblocks last night. I didn't realize how long it would
> take. After over 3 hours, I had to abort it to do something else.
>
> This morning, I retried it, this time with options to show its
> progress. It took between 3 1/2
On 06/02/2017 06:32 PM, William Mattison wrote:
> I tried badblocks last night. I didn't realize how long it would take.
> After over 3 hours, I had to abort it to do something else.
>
> This morning, I retried it, this time with options to show its progress. It
> took between 3 1/2 and 3 3/4
Well, the battery has been replaced this afternoon. It took between 2 and 2
1/2 hours. The system seems to be functioning ok so far, but I haven't yet
booted up in windows-7, and I haven't yet tried a "dnf upgrade".
Before I took the system apart, I checked the CMOS clock and the voltages
rep
I tried badblocks last night. I didn't realize how long it would take. After
over 3 hours, I had to abort it to do something else.
This morning, I retried it, this time with options to show its progress. It
took between 3 1/2 and 3 3/4 hours. Here are the results:
===
bash.3[~]:
Tim:
>> Yes, an update can be more stressful than other PC activities, for
>> *some* users. But for other users, they're always subjecting their
>> PC to a heavy workload, so a prolonged update session is nothing
>> different from normal use.
William Mattison:
> I don't understand what you're say
> Look up S.M.A.R.T., though be aware that some controllers may not
> co-operate, but that tends to be things like outboard USB interfaces, or
> RAID. Ordinary hard drives plugged straight into the motherboard are
> likely to be checkable. It's the hard drive, itself, that checks its
> health an
I did "smartctl --all /dev/sda > smartctl_out.txt". I got over 200 lines of
output. The most recent error reported in the output file is this one:
===
Error 66 occurred at disk power-on lifetime: 13741 hours (572 days + 13 hours)
When the command that caused the error occurred, th
Allegedly, on or about 31 May 2017, William Mattison sent:
> I recall hearing and reading that the output of lithium batteries is
> almost flat (better than any other type of battery), but then very
> quickly drops (faster than any other type of battery) as it reaches
> end-of-life.
I can't say th
On 05/30/2017 09:09 PM, William Mattison wrote:
> I wasn't fully convinced these problems are due to the battery. That's why I
> listed the four things I found "odd". On the other hand, I recall hearing
> and reading that the output of lithium batteries is almost flat (better than
> any other
Bill,
Power supplies can fail at any time, and they are less reliable than any
other parts in my PC's.
PC's are more reliable if you leave them on, configured to go into sleep
mode when left unused (this statement will spark a discussion).
Most spinning disk drives these days support smartd
I wasn't fully convinced these problems are due to the battery. That's why I
listed the four things I found "odd". On the other hand, I recall hearing and
reading that the output of lithium batteries is almost flat (better than any
other type of battery), but then very quickly drops (faster th
On Tue, 2017-05-30 at 02:42 +, William Mattison wrote:
> The fix on Thursday, May 18 did not last. This past Thursday, my
> workstation again failed to boot. This time, it dropped me into an
> emergency shell, not the dracut shell. This time, the log file was
> almost twice as long. But it
So let's close this topic. Further discussion is in the topic
"post-mortem: f24 boot fails; need help.".
Thank-you for your help.
Bill.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
On 05/29/2017 07:42 PM, William Mattison wrote:
The clock was about 5 seconds slow compared to my "atomic" clock. I adjusted
that. This morning, the clock seemed barely noticeably slow compared to that atomic
clock, but by less than a second. So I'm agreeing with your suspicions that the bat
Good evening,
Hardware problems have seriously tied me up for about a week now. My apologies
for my silence on this topic. The hardware issue is not really fixed yet. I
likely will be forced off-line again for several days to a few weeks. If I'm
not responding; assume that that's what's hap
On 05/26/2017 04:52 AM, Tim wrote:
I'm still not convinced with the cargo-cult idea that the BIOS clock is
actually designed to run slow, rather than that simply being a common
side-effect. I've certainly had a motherboard where that effect did not
happen.
I've had several slow-clock issues ov
On 05/26/2017 10:48 AM, Tom Killian wrote:
> Some years ago I had an IBM ThinkPad that one day failed to boot, and
> every subsystem diagnostic that ran at power-up (keyboard, memory, disk
> controller, ...) reported a problem. On a whim I put in a new clock
> battery and everything was fine. Now
Some years ago I had an IBM ThinkPad that one day failed to boot, and every
subsystem diagnostic that ran at power-up (keyboard, memory, disk
controller, ...) reported a problem. On a whim I put in a new clock
battery and everything was fine. Now any time a machine suddenly goes
flakey, the clock
On Thu, 2017-05-25 at 12:47 -0700, Rick Stevens wrote:
> Otherwise, with a weak battery the BIOS will usually revert to default
> settings which are generally considered conservative and "safe".
I'm not so sure that's the case. In many PCs, the BIOS clock, BIOS
memory, and perhaps other BIOS hard
On 05/24/2017 11:40 PM, Joe Zeff wrote:
> On 05/24/2017 09:20 PM, William Mattison wrote:
>> The clock (and the CMOS battery) got some attention while trying to
>> fix the boot problem. I have not yet replaced the battery, but I'm
>> not seeing any problems. What is the likelihood that the batter
On 05/24/2017 09:20 PM, William Mattison wrote:
The clock (and the CMOS battery) got some attention while trying to fix the
boot problem. I have not yet replaced the battery, but I'm not seeing any
problems. What is the likelihood that the battery or the clock caused the boot
failure?
If t
My friend was here earlier tonight. The command was "fsck /dev/sda6" (no
options). He also said he's seen this kind of thing before.
Bill.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedora
Thank-you Sam and Rick.
For the next 2 questions, I'm not looking for numerical answers. Qualitative
probability terms on a scale going from "highly improbably" to "almost
certainly" would be great.
The clock (and the CMOS battery) got some attention while trying to fix the
boot problem. I h
On 05/24/2017 08:38 AM, William wrote:
> Good morning,
>
> The "f24 boot fails; need help" problem set me back a week. I'm still
> catching up. I seriously believe it would be foolish for me to just
> forget it. I should for the benefit of others try to get at
William writes:
A few hours before the failure, I received and looked at an e-mail that I'm
almost certain was at least a spoof, and possibly malicious. I know it
contained html and links. I did *** not ***
click any of the links. I looked at it, and deleted it. It was viewed in
Thunder
Good morning,
The "f24 boot fails; need help" problem set me back a week. I'm still
catching up. I seriously believe it would be foolish for me to just
forget it. I should for the benefit of others try to get at the real
cause and possible prevention.
A few hours before
boots discussed in the "f24 boot fails; need help" topic
was a set of "ACPI" errors. Here are the relevant lines (with added
line numbers) from that log file (the first and last lines are just for
context):
--
862[1.218683] coyote kernel: ata4: SATA link up
On Mon, 22 May 2017 02:15:59 -
"William Mattison" wrote:
> 1. For several weeks, I've been seeing text fly by early during the
> boot process, before the blue and white line grows left to right at
> the bottom of the screen. But the text scrolls by too fast and
> disappears too fast for me t
1. For several weeks, I've been seeing text fly by early during the boot
process, before the blue and white line grows left to right at the bottom of
the screen. But the text scrolls by too fast and disappears too fast for me to
catch more than an isolated word or two. I also had no idea how t
On Fri, 19 May 2017 18:09:21 -0600
William wrote:
> Good evening,
>
> One of the problems reported in the log file "rdsosreport.txt"
> generated by the failed boots discussed in the "f24 boot fails; need
> help" topic was a set of "ACPI" errors. H
Allegedly, on or about 19 May 2017, William Mattison sent:
> After groping through papers in a moving box, I found the user's guide
> for the motherboard. Amazing: something I kept actually proved
> useful!
When space permitted, I'd ziplock bag things like that, and jam them
into the PC case, rea
Good evening,
One of the problems reported in the log file "rdsosreport.txt" generated
by the failed boots discussed in the "f24 boot fails; need help" topic
was a set of "ACPI" errors. Here are the relevant lines (with added
line numbers) from that log file
After groping through papers in a moving box, I found the user's guide for the
motherboard. Amazing: something I kept actually proved useful! It's a ASUS
Sabertooth Z77, bought in early 2013. Well, no index, no mention of battery in
the table of contents. I skimmed through once, no hint of b
You're right.
I should see my friend sometime next week or two. He wants me to help him
practice his cloud computing paper before he presents it at some conference.
(He's an international student.) I'll ask him about the fsck options then.
Bill.
___
u
Well, as you yourself said in an earlier post on this topic, " Memory is the
second thing to go, but I can't remember the first!"! You are almost certainly
correct - it was "fsck", not "fdisk". I just typed the wrong thing into my
posting. Another "senior moment".
> This isn't a black art
Allegedly, on or about 18 May 2017, William sent:
> 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 in
On Fri, 19 May 2017 23:22:30 +0930
Tim wrote:
> Allegedly, on or about 18 May 2017, stan sent:
> > The kernel sets system time from the saved time, and then corrects
> > it from the web when net access is up. If it is too far off, it
> > won't correct it.
>
> Hey, what?!
>
> You can't set a
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 dro
Allegedly, on or about 18 May 2017, William sent:
> "I didn't know workstations nowadays had batteries. When the system is
> back on its feet, I'll try to check that. It was bought in 2013."
>
> I knew that the older motherboards had batteries. But I thought the
> newer ones used something like
Allegedly, on or about 18 May 2017, stan sent:
> The kernel sets system time from the saved time, and then corrects it
> from the web when net access is up. If it is too far off, it won't
> correct it.
Hey, what?!
You can't set a clock from a stored value, time is a moving thing, it's
(now) not
On 18 May 2017 at 23:25, William wrote:
> Fedora seems to have a huge number of commands. Does Fedora have a command
> to report the condition of a full-sized tower motherboard battery? If yes,
> what is that command?
I don't think there's any way to check on the status of a motherboard
battery
On Thu, 18 May 2017 16:25:34 -0600
William wrote:
[snip]
> I knew that the older motherboards had batteries. But I thought the
> newer ones used something like flash (or other persistent) memory.
> It did not occur to me that booting might want the date/time before
> the boot process reached th
Good afternoon,
In the "f24 boot fails; need help" topic, a log file extract had these 2
lines:
1533 [ 4.022605] coyote systemd-fsck[428]: /dev/sda6: Superblock last
mount time is in the future.
1534 [ 4.022745] coyote systemd-fsck[428]: (by less than a day, probably
due to th
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
Allegedly, on or about 17 May 2017, William Mattison sent:
> I don't have a LiveUSB, and I get the impression it would take hours
> to make one.
That all depends...
If you kept an install ISO file somewhere (it doesn't have to be the
most recent), you can probably use that to make a live USB from
On 05/17/2017 05:11 PM, Rick Stevens wrote:
Based on those guesses, if you're trying to mount the root filesystem of
the drive to do some doctoring under a rescue boot, you'd want to mount
/dev/sda6 at the /mnt/sysimage location:
mount /dev/sda6 /mnt/sysimage
First, however, you need t
On 05/17/2017 04:01 PM, William Mattison wrote:
>> It isn't home you want to mount, it's /, the root filesystem.
> I wanted /home as a place to copy log files to so I could then access them
> from the windows box. I originally wanted to copy them to a USB stick, but I
> couldn't get that to wor
> It isn't home you want to mount, it's /, the root filesystem.
I wanted /home as a place to copy log files to so I could then access them from
the windows box. I originally wanted to copy them to a USB stick, but I
couldn't get that to work.
I didn't know workstations nowadays had batteries.
I have three active versions of f24 - the 3 most recent weekly patches. All
three fail the same way and drop me into the dracut mode. I didn't know I had
a rescue mode until some long-time IT friend suggested it to me last Friday.
It wasn't obvious in the grub menu. It actually proved helpfu
I don't have a LiveUSB, and I get the impression it would take hours to make
one. This incident teaches me that once I get the system back on its feet, and
I've upgraded to f25, I'll want to make one. About how long should it take?
___
users mailing l
From what I've seen in the website you referenced, and what I posted here
earlier today, it seems similar to what you experienced, but not identical. It
seems fsck says something is wrong with one of the partitions. Take a look.
Feel free to chime in along with the others.
Thank-you.
___
On Wed, 17 May 2017 18:18:38 -
"William Mattison" wrote:
> Finally, I hope, a few useful clues. Rescue mode gave me enough
> information to make a lucky guess as to how to mount "/home" from
> within the dracut shell.
It isn't home you want to mount, it's /, the root filesystem. One of
m
Finally, I hope, a few useful clues. Rescue mode gave me enough information to
make a lucky guess as to how to mount "/home" from within the dracut shell.
With that, I could try the boot again (which of course failed and dropped me
into the dracut shell), and then mount "/home", and then copy
On Mon, 15 May 2017 21:44:53 -
"William Mattison" wrote:
> I've wrestled with this for some 3(?) days now. I'm still stuck.
Trials and tribulations are good for the soul. ;-) Except when they
happen to me. :-D
> I did find a "rescue" mode, and I was able to get in to it. But it
> didn'
On 05/15/2017 02:44 PM, William Mattison wrote:
I installed Fedora on this dual-boot workstation about 4 years ago. It took a
few days, mostly wrestling with the first few steps. I still don't know what I
finally did different so that it worked. I do not recall what kind of file
system this
Good afternoon.
I've wrestled with this for some 3(?) days now. I'm still stuck.
I did find a "rescue" mode, and I was able to get in to it. But it didn't
really help.
Two IT grad students came and tried to help, but couldn't.
In the rescue mode, I tried to use "fdisk" to get the device ID fo
> 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
On Fri, 12 May 2017 02:42:56 -
"William Mattison" wrote:
> Good evening,
>
> Based on what y'all said, I'd say I'm in a "dracut shell". I cannot
> reach any login whatsoever, using any of the techniques y'all
> suggested.
Sure sounds like it.
> The directory "/usr/bin/" does not have many
Hi, Bill,
I am not sure what causes your problem, but it does sound like your system
cannot identify the root system so it cannot boot. I happened to have similar
problem as you do after dnf update a few weeks ago, although slightly
differently. I did have to fsck my partition before my system
Good evening,
Based on what y'all said, I'd say I'm in a "dracut shell". I cannot reach any
login whatsoever, using any of the techniques y'all suggested.
The "/var/log/" directory is empty.
There is no "/var/cache/" directory.
The directory "/usr/bin/" does not have many things in it. It do
On 05/11/2017 04:57 PM, Patrick O'Callaghan wrote:
Not so. Unless I'm living in a time warp, F24 and F25 are the currently
maintained versions. F23 is EOLed and F26 is in development (not to
mention Rawhide, which will eventually be F27).
Thank you; I sit corrected.
On Thu, 2017-05-11 at 16:50 -0700, Joe Zeff wrote:
> On 05/11/2017 04:29 PM, stan wrote:
> > It is surprising that an update would cause this problem in F24, since
> > it is in maintenance mode, and should be receiving only security
> > updates. If you can get to a console, either by Rick's method
On 05/11/2017 04:29 PM, stan wrote:
I think vi is there, but
unless you are used to modal editors, it is confusing to use.
You may find it easier to use nano if you aren't comfortable with vi.
One if the nice things about it is that the most important commands are
listed at the bottom of the
On 05/11/2017 04:29 PM, stan wrote:
It is surprising that an update would cause this problem in F24, since
it is in maintenance mode, and should be receiving only security
updates. If you can get to a console, either by Rick's method or mine,
you could also look at /var/cache/dnf.rpm.log* to see
On 05/11/2017 03:36 PM, Rick Stevens wrote:
If you have a disk activity LED, watch it...it may be on solid or
flickering really fast. That's indicative of the akmods being built and
loaded. I notice this a lot if I use a nVidia blobs for my video cards
and/or having the system build rescue initrd
On Thu, 11 May 2017 15:36:07 -0700
Rick Stevens wrote:
> On 05/11/2017 01:34 PM, Samuel Sieb wrote:
> > On 05/11/2017 01:21 PM, Bill Mattison wrote:
> >> 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
> >> trou
On 05/11/2017 01:34 PM, Samuel Sieb wrote:
> On 05/11/2017 01:21 PM, Bill Mattison wrote:
>> 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
All three fedora versions in the grub menu appear to yield the same results.
So whatever the "dnf upgrade" did, it affected all three. The windows-7 boot
still works (this is a dual boot system, a desktop).
My camera died over a year ago, and I have no portable devices. Having been
unemploye
On 05/11/2017 01:21 PM, Bill Mattison wrote:
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-a
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 o
87 matches
Mail list logo
