Re: can't boot F19 system

On 03/20/2014 08:04 PM, Chris Murphy wrote: On Mar 20, 2014, at 6:11 PM, pgaltieri . > wrote: When I run fsck on the disk it comes back clean. Try fsck.ext4 -f It's possible the journal is clean but the file system is not. So how does Linux decide if a drive

Re: can't boot F19 system

On Mar 20, 2014, at 6:11 PM, pgaltieri . wrote: > > When I run fsck on the disk it comes back clean. Try fsck.ext4 -f It's possible the journal is clean but the file system is not. > > > So how does Linux decide if a drive can be safely removed versus unmounted? If it's unmounted it's sa

Re: can't boot F19 system

On Wed, Mar 19, 2014 at 11:22 PM, Chris Murphy wrote: > > On Mar 19, 2014, at 9:08 PM, pgaltieri . wrote: > > > > > > > On Wed, Mar 19, 2014 at 11:12 AM, Chris Murphy > wrote: > > > > What do you get for > > smartctl -x /dev/sda > > > > > > Here's the link > > > > https://www.amazon.com/clouddri

Re: can't boot F19 system

On 03/19/2014 11:22 PM, Chris Murphy wrote: Like I said before this device has major file system problems. Because it's in your fstab, and fails to mount, you are dropped to emergency shell.*Any* volume in fstab that fails to mount at boot time causes the system to behave this way. Use nofail

Re: can't boot F19 system

On Mar 19, 2014, at 9:08 PM, pgaltieri . wrote: > > > On Wed, Mar 19, 2014 at 11:12 AM, Chris Murphy > wrote: > > What do you get for > smartctl -x /dev/sda > > > Here's the link > > https://www.amazon.com/clouddrive/share?s=K76mJvZKSG0mr5pSoDGM7k No obvious problems there. I'm suspici

Re: can't boot F19 system

On Wed, Mar 19, 2014 at 11:12 AM, Chris Murphy wrote: > > On Mar 19, 2014, at 11:24 AM, "pgaltieri ." wrote: > > > The above series of commands do not power off the system, it resets it. > Same with the poweroff command. > > What's strange is I was running 3.13.5-103 kernel without issues until I

Re: can't boot F19 system

On Mar 19, 2014, at 11:24 AM, "pgaltieri ." wrote: > > The above series of commands do not power off the system, it resets it. Same > with the poweroff command. > > What's strange is I was running 3.13.5-103 kernel without issues until I > turned the power off by hitting the switch. > > I

Re: can't boot F19 system

On Tue, Mar 18, 2014 at 11:06 PM, Chris Murphy wrote: > > On Mar 18, 2014, at 6:19 PM, pgaltieri . wrote: > > > > When I looked at the grub.cfg the enforcing=0 was there. > > In you previous email this URL contains a log with a command line that > doesn't include enforcing=0. > https://www.amazon

Re: can't boot F19 system

On Mar 18, 2014, at 6:19 PM, pgaltieri . wrote: > > When I looked at the grub.cfg the enforcing=0 was there. In you previous email this URL contains a log with a command line that doesn't include enforcing=0. https://www.amazon.com/clouddrive/share?s=4LDATpk0T3IoK1jb-pKshY > > rpm -q selinux

Re: can't boot F19 system

On Tue, Mar 18, 2014 at 3:01 PM, Chris Murphy wrote: > > On Mar 18, 2014, at 12:53 PM, pgaltieri . wrote: > > Please unplug everything from this laptop, except power. You need to get > the basic setup working reliably first. No external hard drives. No mouse. > Nothing, except power. > > You have

Re: can't boot F19 system

On Mar 18, 2014, at 12:53 PM, pgaltieri . wrote: > Please unplug everything from this laptop, except power. You need to get the > basic setup working reliably first. No external hard drives. No mouse. > Nothing, except power. You haven't done this like I asked. [0.860472] scsi 0:0:0:0: Di

Re: can't boot F19 system

On Tue, Mar 18, 2014 at 10:07 AM, Chris Murphy wrote: > > On Mar 17, 2014, at 11:15 PM, pgaltieri . wrote: > > > > complained about dirty bit being set and that backup version didn't > match current version. > > And if you run it a second time with: > # fsck.msdos -av /dev/sda1 > > > > > > > I'd

Re: can't boot F19 system

On Mar 17, 2014, at 11:15 PM, pgaltieri . wrote: > > complained about dirty bit being set and that backup version didn't match > current version. And if you run it a second time with: # fsck.msdos -av /dev/sda1 > > I'd like to see the result of a boot with boot parameters rhgb quiet remov

Re: can't boot F19 system

On Mon, Mar 17, 2014 at 9:37 PM, Chris Murphy wrote: > > On Mar 17, 2014, at 9:53 PM, "pgaltieri ." wrote: > > > modprobe vfat > > returns with no messages at all. The vfat module is not loaded. > > > Seems important to find out why the kernel isn't loading fat.ko+vfat.ko. > > Emergency shell yo

Re: can't boot F19 system

On Mar 17, 2014, at 9:53 PM, "pgaltieri ." wrote: > > modprobe vfat > > returns with no messages at all. The vfat module is not loaded. Seems important to find out why the kernel isn't loading fat.ko+vfat.ko. Emergency shell you can run: fsck.msdos -a /dev/sda1 See where that gets you, and

Re: can't boot F19 system

On Mon, Mar 17, 2014 at 7:28 PM, Chris Murphy wrote: > > On Mar 17, 2014, at 8:24 PM, Chris Murphy wrote: > > > > > On Mar 17, 2014, at 8:15 PM, Chris Murphy > wrote: > > > >> > >> On Mar 17, 2014, at 7:57 PM, Chris Murphy > wrote: > >>> But maybe once /boot/efi is mounted, it's worth doing dra

Re: can't boot F19 system

On Mar 17, 2014, at 8:24 PM, Chris Murphy wrote: > > On Mar 17, 2014, at 8:15 PM, Chris Murphy wrote: > >> >> On Mar 17, 2014, at 7:57 PM, Chris Murphy wrote: >>> But maybe once /boot/efi is mounted, it's worth doing dracut -f to rebuild >>> the initramfs, and then reboot. >> >> It's not

Re: can't boot F19 system

On Mar 17, 2014, at 8:15 PM, Chris Murphy wrote: > > On Mar 17, 2014, at 7:57 PM, Chris Murphy wrote: >> But maybe once /boot/efi is mounted, it's worth doing dracut -f to rebuild >> the initramfs, and then reboot. > > It's not worth it. I just used lsinitrd on my working system and neither

Re: can't boot F19 system

On Mar 17, 2014, at 7:57 PM, Chris Murphy wrote: > But maybe once /boot/efi is mounted, it's worth doing dracut -f to rebuild > the initramfs, and then reboot. It's not worth it. I just used lsinitrd on my working system and neither fat.ko or vfat.ko are in the initramfs. So somehow on your sy

Re: can't boot F19 system

On Mar 17, 2014, at 6:12 PM, "pgaltieri ." wrote: > > If I look at /usr/lib/modules on the non working system I get: > > 3.12.11-201.fc19.x86_64/ > 3.12.9-201.fc19.x86_64/ > 3.13.5-101.fc19.x86_64/ > 3.13.5-103.fc19.x86_64/ > > uname -a shows > > Linux peglaptopnew 3.13.5-103.fc19.x86_64 #1 S

Re: can't boot F19 system

On Mon, Mar 17, 2014 at 4:31 PM, Chris Murphy wrote: > > > > Chris, > > here is the output for journal -b > > > > https://www.amazon.com/clouddrive/share?s=yuVEpW13SV0n_TIJKaokLs > > Mar 17 14:14:57 peglaptopnew systemd[1]: Mounting /boot/efi... > Mar 17 14:14:57 peglaptopnew mount[460]: mount:

Re: can't boot F19 system

> > Chris, > here is the output for journal -b > > https://www.amazon.com/clouddrive/share?s=yuVEpW13SV0n_TIJKaokLs Mar 17 14:14:57 peglaptopnew systemd[1]: Mounting /boot/efi... Mar 17 14:14:57 peglaptopnew mount[460]: mount: unknown filesystem type 'vfat' Mar 17 14:14:57 peglaptopnew systemd

Re: can't boot F19 system

On Mon, Mar 17, 2014 at 2:17 PM, pgaltieri . wrote: > > On Mon, Mar 17, 2014 at 2:02 PM, Chris Murphy wrote: > >> >> On Mar 17, 2014, at 2:13 PM, pgaltieri . wrote: >> >> > On Mon, Mar 17, 2014 at 12:56 PM, Chris Murphy >> wrote: >> > >> > On Mar 17, 2014, at 1:37 PM, "pgaltieri ." wrote: >> >

Re: can't boot F19 system

On Mon, Mar 17, 2014 at 2:02 PM, Chris Murphy wrote: > > On Mar 17, 2014, at 2:13 PM, pgaltieri . wrote: > > > On Mon, Mar 17, 2014 at 12:56 PM, Chris Murphy > wrote: > > > > On Mar 17, 2014, at 1:37 PM, "pgaltieri ." wrote: > > > > > Here's the output > > > > > > BootCurrent: 0015 > > > Timeou

Re: can't boot F19 system

On Mar 17, 2014, at 2:13 PM, pgaltieri . wrote: > On Mon, Mar 17, 2014 at 12:56 PM, Chris Murphy > wrote: > > On Mar 17, 2014, at 1:37 PM, "pgaltieri ." wrote: > > > Here's the output > > > > BootCurrent: 0015 > > Timeout: 0 seconds > > BootOrder: > > ,0001,0016,0013,0014,0015,0012,001

Re: can't boot F19 system

On Mon, Mar 17, 2014 at 12:56 PM, Chris Murphy wrote: > > On Mar 17, 2014, at 1:37 PM, "pgaltieri ." wrote: > > > Here's the output > > > > BootCurrent: 0015 > > Timeout: 0 seconds > > BootOrder: > ,0001,0016,0013,0014,0015,0012,0010,0011,0019,001A,001B,0017,0018 > > Boot* fedora > > HD

Re: can't boot F19 system

On Mar 17, 2014, at 1:37 PM, "pgaltieri ." wrote: > Here's the output > > BootCurrent: 0015 > Timeout: 0 seconds > BootOrder: > ,0001,0016,0013,0014,0015,0012,0010,0011,0019,001A,001B,0017,0018 > Boot* fedora > HD(1,800,fa000,a37591b8-de99-44c3-9eb8-e7de6f28d62d)File(\EFI\fedora\gr

Re: can't boot F19 system

Here's the output BootCurrent: 0015 Timeout: 0 seconds BootOrder: ,0001,0016,0013,0014,0015,0012,0010,0011,0019,001A,001B,0017,0018 Boot* fedora HD(1,800,fa000,a37591b8-de99-44c3-9eb8-e7de6f28d62d)File(\EFI\fedora\grubx64.efi) Boot0001* Windows Boot Manager HD(1,800,fa000,a37591b8-de99-44c

Re: can't boot F19 system

On Mar 17, 2014, at 10:47 AM, pgaltieri . wrote: > This didn't work. I still get the access denied error. The > /boot/efi/EFI/fedora directory contains a file > > gcdx64.efi > > and > > grubx64.efi > > They are both the same size. The first is dated July 2 2013 the other is > dated toda

Re: can't boot F19 system

This didn't work. I still get the access denied error. The /boot/efi/EFI/fedora directory contains a file gcdx64.efi and grubx64.efi They are both the same size. The first is dated July 2 2013 the other is dated today. I tried renaming grubx64.efi to gcdx64.efi but it also failed. Paolo

Re: can't boot F19 system

On Mar 16, 2014, at 11:19 PM, pgaltieri . wrote: > Well I tried to re-install grub per the link in a previous email. I booted > from DVD, went into rescue mode and did the chroot. I ran > > /sbin/grub2-install /dev/sda > > and on rebooting I get: > > Secure Boot > Image failed to verify wi

Re: can't boot F19 system

Well I tried to re-install grub per the link in a previous email. I booted from DVD, went into rescue mode and did the chroot. I ran /sbin/grub2-install /dev/sda and on rebooting I get: Secure Boot Image failed to verify with Press any key to continue So now what? Anyway to recover from thi

Re: can't boot F19 system

On Mar 16, 2014, at 12:05 PM, pgaltieri . wrote: > Today I needed to power off one of my F19 systems. So I logged out and > selected shutdown from the top right button. Instead of powering off as I > expected, and was told it was going to do from the message that appeared on > the screen, m

Re: can't boot F19 system

On 03/16/2014 02:05 PM, pgaltieri . wrote: > Today I needed to power off one of my F19 systems. So I logged out > and selected shutdown from the top right button. Instead of powering > off as I expected, and was told it was going to do from the message > that appeared on the screen, much to my am

can't boot F19 system

Today I needed to power off one of my F19 systems. So I logged out and selected shutdown from the top right button. Instead of powering off as I expected, and was told it was going to do from the message that appeared on the screen, much to my amazement it didn't. Instead it restarted and went b