ENOFLASH7 in random intervals

[Janniqz]

I've been running UNRAID for a few months now and have been struggling with the system constantly going completely unresponsive.

At this point the system can't be reached via SSH, Samba, HTTP or anything else.

Recently I've been able to at least see the Login Interface although that didn't work either.

 

The intervals in which the system goes unresponsive seem to go from 1 day to 1 week.

 

Looking at the syslog the problem seems to generally "announce" itself with the following:

Jun 25 12:06:37 Tower-NAS emhttpd: Unregistered - flash device error (ENOFLASH7)
Jun 25 12:06:56 Tower-NAS emhttpd: Unregistered - flash device blacklisted (EBLACKLISTED2)
Jun 25 12:06:57 Tower-NAS emhttpd: Unregistered - flash device error (ENOFLASH7)
Jun 25 12:06:59 Tower-NAS emhttpd: Basic key detected, GUID: 090C-1000-0374-422030002317 FILE: /boot/config/Basic.key
Jun 25 12:07:00 Tower-NAS emhttpd: Unregistered - flash device error (ENOFLASH7)
Jun 25 12:07:01 Tower-NAS crond[1034]: unable to fork (user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null)
Jun 25 12:07:01 Tower-NAS crond[1034]: unable to fork (user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null)
Jun 25 12:07:04 Tower-NAS emhttpd: Basic key detected, GUID: 090C-1000-0374-422030002317 FILE: /boot/config/Basic.key
Jun 25 12:07:06 Tower-NAS emhttpd: Unregistered - flash device error (ENOFLASH7)
Jun 25 12:07:22 Tower-NAS emhttpd: Basic key detected, GUID: 090C-1000-0374-422030002317 FILE: /boot/config/Basic.key
Jun 25 12:07:31 Tower-NAS emhttpd: Unregistered - flash device error (ENOFLASH7)
Jun 25 12:07:36 Tower-NAS emhttpd: Basic key detected, GUID: 090C-1000-0374-422030002317 FILE: /boot/config/Basic.key
Jun 25 12:07:38 Tower-NAS emhttpd: Unregistered - flash device error (ENOFLASH7)
Jun 25 12:07:39 Tower-NAS emhttpd: Basic key detected, GUID: 090C-1000-0374-422030002317 FILE: /boot/config/Basic.key
Jun 25 12:07:45 Tower-NAS emhttpd: Unregistered - flash device error (ENOFLASH7)

 

This pretty much repeats itself with a few other log messages until I reboot the system.

 

I've already tried various things and at this point I'm kinda out of ideas. I've tried the following:

• Use different USB Ports (Front / Back)
• Use different USB Sticks (Cheap Intenso and Samsung FIT Plus)
  • Currently still using the Samsung
• Disable XMP

 

I've also moved the system to another room as the original one has a Mini Fridge in it. Maybe some EMI messing with the USB Stick?

 

Looking at my syslog file I've had crashes at the following dates:

• ...
• May 30th
  • Disabled mirroring sometime after that because it worked for like a week
• June 20th
• June 24th
• June 25th

 

---

 

Specs:

Unraid Version: 6.10.3

CPU: Intel Core i3-12100

RAM: G.Skill Ripjaws V (2x 8GB DDR4-3200)

MB: ASRock H610M-ITX/ac

 

tower-nas-diagnostics-20220625-2022.zip

Edited June 25, 2022 by Janniqz
Added System Specifications

[Squid]

From during the bootup sequence:

Jun 25 19:55:14 Tower-NAS kernel: FAT-fs (sda1): error, clusters badly computed (450 != 449)

 

In theory, a reboot *should* fix you up, but for the best success, shut down the server, pull the flash and toss it into a Windows / Mac box and run it's file system checks on it (Win: right click on drive, properties, tools, Check) and then try the server again.

 

Worst case scenario, replace the flash https://wiki.unraid.net/Manual/Changing_The_Flash_Device

[Janniqz]

13 minutes ago, Squid said:

From during the bootup sequence:

Jun 25 19:55:14 Tower-NAS kernel: FAT-fs (sda1): error, clusters badly computed (450 != 449)

 

In theory, a reboot *should* fix you up, but for the best success, shut down the server, pull the flash and toss it into a Windows / Mac box and run it's file system checks on it (Win: right click on drive, properties, tools, Check) and then try the server again.

 

Worst case scenario, replace the flash https://wiki.unraid.net/Manual/Changing_The_Flash_Device

 

I've let Windows run its check and repair the Flash Drive.

UNRAID doesn't report the Flash Drive as read-only anymore so that did fix something 😄

 

From what I can tell the problem with the flash itself was caused due to all the unclean shutdowns to get the system working again but maybe the EMI did actually contribute?

As mentioned this is already the second flash drive I've tested. I only bought it a few weeks ago to combat this exact problem so I'd hope it's not dead already 😉

 

I'll report back when something happens again!

[Janniqz]

Crashed again. I've included an excerpt of the syslog including all the error messages.

The last restart before this was on the 25th at 19:55 so it survived a few days this time.

syslog-28-06.txt