Stuck at "verifying bzroot checksum ..." but no errors on console

[TristanP]

I shutdown my unRAID machine to remove two unneeded disks and reroute cables. That went smoothly and the SAS controllers showed the right drives on the right interface.

 

While booting it spit out the following:

Quote

Checking /dev/sda1

fsck.fat 4.2 (2021-01-31)

There are differences between boot sector and its backup

This is mostly harmless. Differences: (offset:original/backup)

65:01/00

Not automatically fixing this

Dirty bit is set. Fs was not properly unmounted and some data may be lost

Automatically removing dirty bit.

/dev/sda1: 616 files, 92166/1874991 clusters

mount: /dev/sda1 mounted on /boot.

Verifying bzimage checksum ...

Verifying bzroot checksum ...

 

And there it sits. Pushing 30 minutes now.

 

Any ideas what may be going on? Do I interrupt it or let it run.

 

I am using unRAID v6.11.5.

 

Thanks.

Edited June 30, 2023 by TristanP

[JorgeB]

Try redoing the flash drive.

[TristanP]

I'll give it a shot. I thought the license was tied to some unique id on the USB stick though,

 

So I downloaded the USB creator, created a new flash drive with the correct version (6.11.5) and copied the old /config folder onto the USB /config.

 

Unfortunately it seems to have gotten worse. There are now dozens of listings after this text:

Quote

There are differences between boot sector and its backup

This is mostly harmless. Differences: (offset:original/backup)

 

instead of just the one prior. And there it sits.

 

It's wondering what is going on that annoys me. Sigh

Edited July 4, 2023 by TristanP
Additional info

[JorgeB]

I meant redo the same flash drive, if you use a different one you'll need to tranfer the key, but the new one should still boot.

[TristanP]

Just to make sure:

- Copy the /config directory off the flash drive

- Use the unRAID USB creator to rewrite the 6.11.5 version back on the stick

- Copy the /config directory back

 

Sorry for being dense but before I do destructive operations I want to make sure I understand the process.

[JorgeB]

Yes, that's it.

[TristanP]

Did the above. No change from the new one. Here's a screen shot of the console (Wish I could get the entire output):

 

[JorgeB]

If the same Unraid release booted before it suggests some hardware issue, I would start by resetting CMOS and removing any add-on cards and see if it boots like that.

[TristanP]

Thanks for the suggestion. Now off to trial and error

[TristanP]

Finally got time and puled the LSI SAS controller with no change. I them pulled the SAS Expander card (HP 468405-002) and disconnected it from the MB. Now I get a new error:

 

Quote

LZMA data is corrupt

-- System halted

 

That's after I redid the original USB with the latest unRAID writer (See above).

 

Gotta admit....This is a new error for me.