Hi Peter,
No the Ipfire before the problem was running on a normal but yet old(2008) WD SATA HDD, because I noticed it’s a old HDD when I took it out I decided to upgrade the HDD to a SSD.
The HDD was 350GB.
The SSD is 500GB.
The HDD is stil in the box as a backup if something goes wrong.
Best regards.
Neopegasus.
Peter,
My emulation (Serial, MacOS) had weird behavior. Menues were barely readable. I have played around with the terminal config but no success. There was also an error on non supported graphic mode but I have not captured the message 
After some trial and error I was able to initiate the installation. From then on, the menues were readable and installation worked smoothly. No more issues with Grub.
Sh… happens. I will consider a backup hardware.
Hi all,
so bad flash storage isn’t it, either.
To be honest, I am out of ideas by now. If anybody comes up with a reasonable one, please let us know.
Thanks, and best regards,
Peter Müller
I think it’s a bunch of uncorrelated issues involving several people, including myself. I believe, this has nothing to do with 157 release.
I posted in this thread after I got informed from a friend of mine that his IPFire (apu1) could not boot after the 156 to 157 update. Therefore I wrote here (big mistake) before checking what was really going on at the time. My apologies for wasting your time @pmuller
After I went ahed and decided to update, my own machine updated without any problem. My friends machine, using his backup hard disk, did the same. It turned out that the main hard disk of my friend did not boot properly because a file system error:
EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
dracut: Checking ext4: /dev/disk/by-uuid/cea89658-1ad9-49dc-bded-c7f1184ac72b
dracut: issuing e2fsck -a /dev/disk/by-uuid/cea89658-1ad9-49dc-bded-c7f1184ac72b
random: fast init done
ata1.00: READ LOG DMA EXT failed, trying PIO
ata1.00: exception Emask 0x0 SAct 0x7ffff8 SErr 0x0 action 0x0
ata1.00: irq_stat 0x40000008
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/28:20:d6:6b:d5/01:00:00:00:00/40 tag 4 ncq dma 151552 in
res 53/40:08:f6:6c:d5/00:00:00:00:00/40 Emask 0x409 (media error) <F>
ata1.00: status: { DRDY SENSE ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sd 0:0:0:0: [sda] tag#4 Sense Key : Medium Error [current]
sd 0:0:0:0: [sda] tag#4 Add. Sense: Unrecovered read error - auto reallocate failed
sd 0:0:0:0: [sda] tag#4 CDB: Read(10) 28 00 00 d5 6b d6 00 01 28 00
print_req_error: I/O error, dev sda, sector 13987062
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x60000003 SErr 0x0 action 0x0
ata1.00: irq_stat 0x40000008
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/02:e8:f6:6c:d5/00:00:00:00:00/40 tag 29 ncq dma 1024 in
res 53/40:02:f6:6c:d5/00:00:00:00:00/40 Emask 0x409 (media error) <F>
ata1.00: status: { DRDY SENSE ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] tag#29 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sd 0:0:0:0: [sda] tag#29 Sense Key : Medium Error [current]
sd 0:0:0:0: [sda] tag#29 Add. Sense: Unrecovered read error - auto reallocate failed
sd 0:0:0:0: [sda] tag#29 CDB: Read(10) 28 00 00 d5 6c f6 00 00 02 00
print_req_error: I/O error, dev sda, sector 13987062
Buffer I/O error on dev sda4, logical block 6326104, async page read
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x1000000 SErr 0x0 action 0x0
ata1.00: irq_stat 0x40000008
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/02:c0:f6:6c:d5/00:00:00:00:00/40 tag 24 ncq dma 1024 in
res 53/40:02:f6:6c:d5/00:00:00:00:00/40 Emask 0x409 (media error) <F>
ata1.00: status: { DRDY SENSE ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] tag#24 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sd 0:0:0:0: [sda] tag#24 Sense Key : Medium Error [current]
sd 0:0:0:0: [sda] tag#24 Add. Sense: Unrecovered read error - auto reallocate failed
sd 0:0:0:0: [sda] tag#24 CDB: Read(10) 28 00 00 d5 6c f6 00 00 02 00
print_req_error: I/O error, dev sda, sector 13987062
Buffer I/O error on dev sda4, logical block 6326104, async page read
ata1: EH complete
/dev/disk/by-uuid/cea89658-1ad9-49dc-bded-c7f1184ac72b: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e.dracut Warning: e2fsck returned with 4
, without -a or -p options)
dradracut Warning: /dev/disk/by-uuid/cea89658-1ad9-49dc-bded-c7f1184ac72b contains a file system with errors, check forced.
cut Warning: e2fdracut Warning: Error reading block 1581526 (Input/output error) while reading directory block.
sck returned with 4
dracut Warndracut Warning: *** An error occurred during the file system check.
ing: /dev/disk/bdracut Warning: *** Dropping you to a shell; the system will try
y-uuid/cea89658-dracut Warning: *** to mount the filesystem(s), when you leave the shell.
1ad9-49dc-bded-cdracut Warning: filesystem)
7f1184ac72b contains a file system with errors, check forced.
dracut Warning: Error reading block 1581526 (Input/output error) while reading directory block.
dracut Warning: *** An error occurred during the file system check.
dracut Warning: *** Dropping you to a shell; the system will try
dracut Warning: *** to mount the filesystem(s), when you leave the shell.
dracut Warning: filesystem)
Generating "/run/initramfs/rdsosreport.txt"
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot
after mounting them and attach it to a bug report.
To get more debug information in the report,
reboot with "rd.debug" added to the kernel command line.
Dropping to debug shell.
(Repair:/#
Thanks for helping us out. I will try to be more careful next time. I think we should close this thread.
Hi all,
for the records: The only thing that occurred to me regarding this problem was a missing sync statement in the extract_files() function (see here for it’s source code).
On systems having either
this might be useful to ensure we have actually written down upgraded files to disk, before letting Grub search for a new kernel.
Its somewhat homeopathic, but I guess it is better than nothing. I will suggest this on the mailing list.
EDIT: Done, please refer to this patch, which resulted in this commit.
Thanks, and best regards,
Peter Müller
Hi @cfusco,
thank you for reporting back. 
Indeed, that disk seem to have reached its technical lifetime. Input/output errors are never a good sign when it comes to mass storage failures…
There is absolutely need to apologise: I am glad for this constructive discussion, people reporting back, providing logfiles - everything went exactly as I like supporting/debugging.
Given the fact that we still have two other users in this thread experiencing the same or a similar error, I still suspect some quirk being shipped with Core Update 157. I would be odd to see three hard drives die at the same time… 
Thanks, and best regards,
Peter Müller
Hello all,
I was running 157 on my NanoPi R1 and now I can’t boot. This is what I have on the screen (see attached text file in zip). Can anyone help please?
Thanks in advance…
ipfire_error.zip (5.1 KB)
is indicating that the ext4 filesystem on your main partition has errors.
If you are running from uSD card, then probably time to replace the card.
If you are running from eMMC, then you could try installing to uSD card, booting from that and trying to run fsck on the eMMC partitions.