Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Unraid 7.2.0. Unexpected clean(?) shutdown on mounting unassigned USB3 SSD

Featured Replies

I was checking the contents of a SSDs via my USB3 cradle (it never was trouble), working directly with the server's display and keyboard. Once appearing as an Unassigned drive, I attempted to mount it. Instantly, the GUI was replaced by the console and a flurry of lines, and the system shut down in maybe ten seconds.

Fearing the worst, I booted and logged in, but I saw no warnings about any need to rebuild the parity data anywhere. Not restarting the Array just yet, I tried mounting the SSD's volume again, and this time it worked normally. After perusing its contents, I unmounted it and switched the cradle off.

Then I started the Array. Again, no warnings of anything wrong with the parity data. The only notification was one of the SSD having showed an inordinate amount of CRC errors (although I seem to remember those not being real but some kind of artifact).

I'm checking syslog-previous. As I'm a complete novice, I don't understand it, but I can see the references to the "SuperSpeed USB device" (the SSD), and what feels like an orderly shutdown process. I would be grateful if somebody could give it a look and opine on it.

syslog-previous.txt

Edited by MetricTonto

Solved by JorgeB

  • MetricTonto changed the title to Unraid 7.2.0. Unexpected clean(?) shutdown on mounting unassigned USB3 SSD
  • Community Expert
  • Solution

According to the syslog, the power button was pressed:

Nov 9 13:55:52 NAS elogind-daemon[1819]: Power key pressed short.

Nov 9 13:55:52 NAS elogind-daemon[1819]: Powering off...

Nov 9 13:55:52 NAS elogind-daemon[1819]: System is powering down.

  • Author
23 minutes ago, JorgeB said:

According to the syslog, the power button was pressed:

That's worrisome 🤨. The PC case is set in such a way that the button is difficult to reach. The cradle has one of those buttons meant to trigger a Windows HDD cloner app, though. I wonder if I pressed that one without meaning to and it produced a similar reaction. I'll have to test that.

In any case, thank you for giving it a look 🙂.

  • Author

OK, so, it was the no-name PC keyboard's power down button 😑 (I never use such, and I used to have a Mac keyboard there instead). I wonder if I can disable that in the BIOS or somewhere else.

  • Author

This motherboard's BIOS at the very least allows for setting it to require a four seconds button press for it to act.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.