Core 123 update from Core 120

Help on building IPFire & Feature Requests
Post Reply
User avatar
H&M
Posts: 430
Joined: May 29th, 2014, 9:38 pm
Location: Europe

Core 123 update from Core 120

Post by H&M » September 14th, 2018, 3:50 pm

Hi,


I just launched the update on my 2 IpFire machines that were on core 120.

First one hang after update: this was was updated by launching twice pakfire upgrade because after first round it told me that it reached only core 121 ( 120->121)

Code: Select all

1. AHCI/0: SATA SSD ATA-10 Hard-Disk (15272 MiBytes)
2. USB MSC Drive Multiple Card  Reader 1.00
3. iPXE (PCI 00:00.0)
4. AHCI/1: HITACHI HTS723232A7A364 ATA-8 Hard-Disk (298 GiByte
5. Payload [setup]
6. Payload [memtest]

Searching bootorder for: HALT
drive 0x000f2500: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=31277232
drive 0x000f2480: PCHS=0/0/0 translation=lba LCHS=975/128/63 s=7864320
drive 0x000f24b0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=625142448
Space available for UMB: c1000-ee800, f0000-f2480
Returned 245760 bytes of ZoneHigh
e820 map has 6 items:
  0: 0000000000000000 - 000000000009fc00 = 1 RAM
  1: 000000000009fc00 - 00000000000a0000 = 2 RESERVED
  2: 00000000000f0000 - 0000000000100000 = 2 RESERVED
  3: 0000000000100000 - 000000007e14c000 = 1 RAM
  4: 000000007e14c000 - 000000007f000000 = 2 RESERVED
  5: 00000000f8000000 - 00000000f9000000 = 2 RESERVED
enter handle_19:
  NULL
Booting from Hard Disk...
Booting from 0000:7c00
GRUB loading.

The second displayed after update that was installed core 121 (120 ->121), reboots ok, but in /opt/pakfire/db/core/mine I ended up with value 123.

How dows actually work the update from 120 - can it jump direvctly to 123 (although the update told me core 121)?
Second - is the first machine bricked?
How can I solve that nasty Grub halt?

Thank you,
H&M

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests