Jump to content
nocotek

Upgraded OS - Kernel Panic (SOLVED)

3 posts in this topic Last Reply

Recommended Posts

Posted (edited)

Was operating 6.5.1 without any issues. 

Decided this AM up try the latest release candidate 6.5.2 RC2

Rebooted and noticed nothing was coming up. Connected monitor to find the following attached image.

Thinking that it might have been an issue with the version, I restored the 'Previous' folder to the main USB directory but still ended up with similar results. 

I'm currently riding out that 'uh oh' phase. 

As the only other thing I can see in the recent syslog.txt is the following near the end of the file.

 

May 14 07:09:59 RaidBox emhttpd: import flash device: sda
May 14 07:10:01 RaidBox emhttpd: shcmd (54831): modprobe md-mod super=/boot/config/super.dat
May 14 07:10:01 RaidBox emhttpd: shcmd (54831): exit status: 135
May 14 07:10:01 RaidBox kernel: SQUASHFS error: xz decompression failed, data probably corrupt
May 14 07:10:01 RaidBox kernel: SQUASHFS error: squashfs_read_data failed to read block 0x31e6a0
May 14 07:10:01 RaidBox kernel: SQUASHFS error: xz decompression failed, data probably corrupt
May 14 07:10:01 RaidBox kernel: SQUASHFS error: squashfs_read_data failed to read block 0x31e6a0
May 14 07:10:01 RaidBox emhttpd: Device inventory:
May 14 07:10:01 RaidBox emhttpd: WDC_WD10EZRX-00A8LB0_WD-WCC1U1319543 (sdj) 512 1953525168
May 14 07:10:01 RaidBox emhttpd: WDC_WD20EZRX-00D8PB0_WD-WMC4M1047586 (sdk) 512 3907029168
May 14 07:10:01 RaidBox emhttpd: Hitachi_HUA723020ALA641_YFHHTLVA (sdg) 512 3907029168
May 14 07:10:01 RaidBox emhttpd: Hitachi_HUS724030ALE641_P8H8682V (sdh) 512 5860533168
May 14 07:10:01 RaidBox emhttpd: KINGSTON_SV300S37A120G_50026B77490970E1 (sdd) 512 234441648
May 14 07:10:01 RaidBox emhttpd: Hitachi_HUA722020ALA331_BFG997SF (sde) 512 3907029168
May 14 07:10:01 RaidBox emhttpd: SanDisk_SD8SN8U128G1001_171483801303 (sdb) 512 250069680
May 14 07:10:01 RaidBox emhttpd: Hitachi_HUA723020ALA641_YGHKK6BA (sdf) 512 3907029168
May 14 07:10:01 RaidBox emhttpd: KINGSTON_SV300S37A120G_50026B775B000522 (sdc) 512 234441648
May 14 07:10:01 RaidBox emhttpd: Hitachi_HUA723020ALA641_YFGU9ALA (sdl) 512 3907029168
May 14 07:10:01 RaidBox emhttpd: Hitachi_HUA723020ALA641_YFG20GAA (sdi) 512 3907029168
May 14 07:10:01 RaidBox emhttpd: JetFlash_Transcend_16GB_3063392MQKF9MP8X-0:0 (sda) 512 31703040
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: error: mdcmd, 2635: No such file or directory (2): open
May 14 07:10:01 RaidBox emhttpd: import 30 cache device: (sdc) KINGSTON_SV300S37A120G_50026B775B000522
May 14 07:10:01 RaidBox emhttpd: import 31 cache device: (sdd) KINGSTON_SV300S37A120G_50026B77490970E1
May 14 07:10:01 RaidBox emhttpd: import 32 cache device: (sdb) SanDisk_SD8SN8U128G1001_171483801303
May 14 07:10:01 RaidBox emhttpd: import flash device: sda
 

 

Suggestions?

kp.jpg

raidbox-diagnostics-20180514-0709.zip

Edited by nocotek
solved

Share this post


Link to post

Your syslog indicates you haven't rebooted since April. Were these diagnostics before the attempted upgrade? You just found them on the flash drive?

 

Put your flash in your PC and let it checkdisk, then download 6.5.1 from the limetech website, unzip it, and copy all bz* files to the root of the flash and see if it works.

Share this post


Link to post

I think that diagnostic file was before the upgrade as after the upgrade it did the panic. 

I did manage to copy the bz* files from the 6.5.1 zip file and copied them onto the thumb drive. 

Booted right up and everything seems functional. 

 

Thanks for the quick response and helping with the resolution.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now