Project

General

Profile

Bug #20819

Possible Errors with Grub?? Compression algorithm 104 not supported

Added by Larry Rosenman over 3 years ago. Updated over 2 years ago.

Status:
Closed: Third party to resolve
Priority:
No priority
Assignee:
Sean Fagan
Category:
Middleware
Target version:
Seen in:
Severity:
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:

Dell T310

ChangeLog Required:
No

Description

https://forums.freenas.org/index.php?threads/possible-errors-with-grub-compression-algorithm-104-not-supported.49887/#post-345507

Hi

Re: FreeNAS 9.10.2-U1.iso

I have recently installed the latest version of FreeNAS on to a 8GB USB drive for my NAS.

The installation appears to install OK, however when booting from the USB, I receive the following messages: (see attached)

GRUB Loading
Welcome to GRUB!

4x error: compression algorithm 104 not supported
2x error: unknown device 264865096
4x error: compression algorithm 104 not supported
1x error: unknown device 264865096

Grub seems to then load fine and I receive the console setup screen as normal.

see the referenced thread for more info.

grub.cfg (12.5 KB) grub.cfg grub.cfg from my box Larry Rosenman, 02/03/2017 07:51 AM

Related issues

Related to FreeNAS - Bug #23275: Compression algorithm error messages shown before grub boot menuClosed: Duplicate2017-04-11

History

#1 Updated by Larry Rosenman over 3 years ago

  • Seen in changed from 9.10.2-U2 to 9.10.2-U1

#2 Updated by Bonnie Follweiler over 3 years ago

  • Subject changed from Home Forums > FreeNAS Forum > Help & Support > Installation and Updates > Possible Errors with Grub?? Compression algorithm 104 not supported to Possible Errors with Grub?? Compression algorithm 104 not supported
  • Assignee set to Sean Fagan

#3 Updated by Bonnie Follweiler over 3 years ago

Would you be able to provide a debug from System -> Advanced -> Save Debug. It could be helpful.

#4 Updated by Larry Rosenman over 3 years ago

Bonnie Follweiler wrote:

Would you be able to provide a debug from System -> Advanced -> Save Debug. It could be helpful.

while it is booted or from where in the process?

#5 Updated by Sean Fagan over 3 years ago

  • Assignee changed from Sean Fagan to Kris Moore

I've seen multiple reports of this on the fora, but I haven't seen it in life.

Kris, comments? I do wonder if it's due to flash going bad.

#6 Updated by Larry Rosenman over 3 years ago

Sean Fagan wrote:

I've seen multiple reports of this on the fora, but I haven't seen it in life.

Kris, comments? I do wonder if it's due to flash going bad.

In my case, brand new flash......

#7 Updated by Larry Rosenman over 3 years ago

  • File debug-freenas-20170202124007.tgz added

debug attached...

Hostname freenas.local
Edit

Build FreeNAS-9.10.2-U1 (86c7ef5)
Platform Intel(R) Xeon(R) CPU E5645 @ 2.40GHz
Memory 49113MB
System Time Thu Feb 02 12:41:15 CST 2017
Uptime 12:41PM up 1 day, 14:53, 0 users
Load Average 0.20, 0.14, 0.06

#8 Avatar?id=14398&size=24x24 Updated by Kris Moore over 3 years ago

  • Status changed from Unscreened to Closed: Third party to resolve
  • Assignee changed from Kris Moore to Sean Fagan

I've seen this at random other machines. It's always seemed "cosmetic" and I believe it comes down to grub trying to sample other disks incorrectly for boot data. I think its probably a bad idea to silence the warnings for now (in case we do find a system that wont boot with this error). I'm going to close it as a GRUB issue to resolve upstream fo rnow.

#9 Updated by Larry Rosenman over 3 years ago

ok -- So, it just delays the boot?

What can I provide before I make this system production to help the grub folks?

#10 Avatar?id=14398&size=24x24 Updated by Kris Moore over 3 years ago

Are you seeing any major delay before the GRUB menu loads? When I've run across this before it made no noticeable difference in speed that I could tell.

But I would start by attaching your /boot/grub/grub.cfg here if possible and that should be what the grub folks would ask for as well.

#11 Updated by Larry Rosenman over 3 years ago

grub.cfg attached.

#12 Updated by Larry Rosenman over 3 years ago

Kris Moore wrote:

Are you seeing any major delay before the GRUB menu loads? When I've run across this before it made no noticeable difference in speed that I could tell.

But I would start by attaching your /boot/grub/grub.cfg here if possible and that should be what the grub folks would ask for as well.

I'll have to watch it again tonight for the delay. I've attached the grub.cfg here above

#13 Updated by Larry Rosenman over 3 years ago

Larry Rosenman wrote:

Kris Moore wrote:

Are you seeing any major delay before the GRUB menu loads? When I've run across this before it made no noticeable difference in speed that I could tell.

But I would start by attaching your /boot/grub/grub.cfg here if possible and that should be what the grub folks would ask for as well.

I'll have to watch it again tonight for the delay. I've attached the grub.cfg here above

takes about 5-7 MINUTES to get into a FreeBSD Kernel. NOT HAPPY.

#14 Avatar?id=14398&size=24x24 Updated by Kris Moore over 3 years ago

That is quite long. Your grub.cfg looks entirely normal though. Do you have any extra storage attached not apart of the boot or primary zpool? Would you be willing to test boot with the boot pool devices detached? I need to determine if it's boot disk corruption or issues reading the wrong disks.

#15 Updated by Larry Rosenman over 3 years ago

Nothing attached storage wise. I've started copying data to the 10x3T array I guess I could detach the mSATA->Sata adapter. This DID work quickly for the first boots.

(all the HW details are linked in the forum post).

Would what you want to do put my data at risk?

#16 Updated by Larry Rosenman over 3 years ago

interestingly, I moved the system dataset to the boot pool (it's a mirrored set of mSATA 64GB drives), and the delay is gone. I just get one compression 104 whine.

#17 Updated by Rolf van Trigt over 3 years ago

  • Hardware Configuration updated (diff)

At the moment i have the same issue. 4 times the error that the compression algorithm 104 is not supported. It only does not boot at all. Its stuck at this screen.

Some background:
Had is working server, but the USB stick had hardware issues. So the ngigx did not start anymore correctly. My guess was a bad USB stick. FreeNAS was a very old versions. I don't know exactly the version.
Got a new USB stick, put it in server, unplugged al 5 SATA harddisks.
Installed latest ISO from FreeNAS without any issues.
booted without any issues.
Pluggedin all SATA harddisks again.
Server did not boot at all. It stayed on GRUB
Changed within BIOS the USB mode from Floppy to Harddisk.
And now GRUB stays with the Compression algorithm 104 not supported message and does not boot.

#18 Updated by Warren Block over 3 years ago

  • Related to Bug #23275: Compression algorithm error messages shown before grub boot menu added

#19 Updated by Ken Perchuk over 3 years ago

I'm getting the same error as Rolf Van Trigt. (4 x error compression algorithm 104 not supported and the system just hangs) Is there any solution yet or do I need to reinstall?

#20 Updated by Dru Lavigne almost 3 years ago

  • File deleted (debug-freenas-20170202124007.tgz)

#21 Updated by Dru Lavigne almost 3 years ago

  • Target version set to N/A

#22 Updated by T F over 2 years ago

Hi all. I'm not sure if this is related, but I saw some similar errors on a test FreeNAS system that had been upgraded from 9.10.2-U1 -> 11.1-U1 running on an Intel NUC with an Internal mSATA SSD boot drive & an external USB data drive for. In my case the messages looked like this:

error: compression algorithm 95 not supported
error: compression algorithm 95 not supported
error: compression algorithm 95 not supported
error: compression algorithm 95 not supported
error: compression algorithm 16 not supported
error: compression algorithm 16 not supported
error: compression algorithm 95 not supported
error: compression algorithm 95 not supported
error: compression algorithm 95 not supported
error: compression algorithm 95 not supported
error: compression algorithm 16 not supported
error: compression algorithm 16 not supported

I rebooted once to see if it was transient and the errors were displayed again (can't be 100% certain they were all the same as I only managed to get a picture the second time around, but I'm pretty sure I saw the 95 lines again). However, subsequent reboots have been quiet, with no mention of these errors.

Also available in: Atom PDF