Re: Doing sudo fedup --network 19 --debuglog fedupdebug.log screwed up my system

2014-01-13 Thread pgaltieri .
I see no grub menu, and I can't ping the system from another system. During startup I hit F12 to go to the boot menu. If I try to boot from the hard disk I do see the grub menu, but when I try to boot I get a kernel panic. Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(

Re: Doing sudo fedup --network 19 --debuglog fedupdebug.log screwed up my system

2014-01-13 Thread Chris Murphy
On Jan 13, 2014, at 4:33 PM, "pgaltieri ." wrote: > I decided to upgrade my F18 system to F19. After updating the F18 system to > the latest updates and installing fedup I ran: > > sudo fedup --network 19 --debuglog fedupdebug.log > > > This completed without errors. > > I then rebooted and

Doing sudo fedup --network 19 --debuglog fedupdebug.log screwed up my system

2014-01-13 Thread pgaltieri .
I decided to upgrade my F18 system to F19. After updating the F18 system to the latest updates and installing fedup I ran: sudo fedup --network 19 --debuglog fedupdebug.log This completed without errors. I then rebooted and selected the option to upgrade the system. After several hours there wa