Hi, 

I trying to start my unRaid server again after long off-time (close to a year... 😕).

But it will not start.

I get: 

Loading /bzimage... ok

Loading /bsroot...ok

LZMA data is corrupt

-- System halted_

 

What is the best (simplest) way to get the server up & running again? 

 

I tried to backup the files on the USB stick but can't copy the file "bzroot-gui". That might be the problem? (I get "Error 0x8007045D: I/O device error")  

I can't find what version I have.. I bought the key 4 aug. 2018. Can i find the version in the USB-stick? (If it is necessary.)

Hm.. 

In the filen "Changed" I find: 
### Version 6.5.3 2018-06-12

Linux kernel: version 4.14.49

 

Please help 

 

BR /Tom

Just now, TomH said:

That might be the problem? (I get "Error 0x8007045D: I/O device error")  

Most likely, try backing up the config folder and then re-create the flash, if it fails transfer the key.

Thanks!

1. Tried to just replace the "bzroot-gui" but that didn't help. Same error. 

2. Formatted the USB stick,

3. Downloaded the latest version on unraid 

4. Copied to the USB stick

5. Replaced the config folder,

6. Run file "make_bootable.bat" 

7. Server up and running again! 😃

 

Didn't need to do anything with the key(?) 

Edited January 9, 20215 yr by TomH

2 hours ago, TomH said:

Didn't need to do anything with the key(?)

Key in the config folder is linked to the flash ID embedded in hardware, so as long as you use the same physical USB stick, the license key will work. Doesn't matter if you reformat.

I faced the same error yesterday when rebooting after only 1 month's up-time. I backed up the config folder as mentioned and created a new Unraid installation with the USB Creation Tool, copied back the config folder and the error was gone. Does somebody know why this "LZMA CORRUPT" error occurs?

 

First time I saw that error I was shocked and scared if my USB drive was killed, but turns out everything is fine with the USB drive.

On 5/5/2022 at 8:28 PM, Skylinar said:

I faced the same error yesterday when rebooting after only 1 month's up-time. I backed up the config folder as mentioned and created a new Unraid installation with the USB Creation Tool, copied back the config folder and the error was gone. Does somebody know why this "LZMA CORRUPT" error occurs?

 

First time I saw that error I was shocked and scared if my USB drive was killed, but turns out everything is fine with the USB drive.

To me this happen every time I have not used the server for a while. And I am using high quality USB drives...  😕

I know it’s an old post but… Just curious. Do you by any chance host your unRAID on HP micro server hardware?

 

if not, what hardware are you running it on?

 

Thanks a lot for replying!

On 5/5/2022 at 1:28 PM, Skylinar said:

I faced the same error yesterday when rebooting after only 1 month's up-time. I backed up the config folder as mentioned and created a new Unraid installation with the USB Creation Tool, copied back the config folder and the error was gone. Does somebody know why this "LZMA CORRUPT" error occurs?

 

First time I saw that error I was shocked and scared if my USB drive was killed, but turns out everything is fine with the USB drive.

This is caused by usb age and bad flash:

What happens is:
Kernel Panic; syncing VFS; unable to mount root fs on unknown-block.

Since uraid loads that into ram this could also be early signs of ram hardware failure / Ram ecc corrections....

Formatting the flash drive moves the "super block" that is read from. Moving data off corrupted flash memory.

It is Best to replace your flash drive and contact support with key transfers.

Edited April 30, 20242 yr by bmartino1

The thing about flash drive age and quality is just BS. I tried to boot of a virtually created USB-flash backed by NVME-drive. Same issue. Had to create the disk 3 times and it just worked. This was on an IBM NVME SAN Volume that runs hundreds of VM's in ESXi. I would say there is something fishy with unraid install maker. I had the same thing happening on my Macbook pro M4 pro.