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
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 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
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
31 matches
Mail list logo
