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.

Modify handling of "Unformatted" status

Featured Replies

Currently, any device that does not mount is marked as being 'Unformatted', causing the webGui to present a 'Format' button.

 

Normally this is correct because the only way a mount should fail is if indeed there is no recognized file system present.  However "stuff happens" and for whatever reason if a valid disk should ever not mount, there is possibility of user clicking that Format button and wiping out their file system.

 

We are therefore adding additional safeguards as follows.

- If the MBR of the disk is entirely all zeros OR if the MBR of the disk has the "precleared" signature present, then will will go ahead and mark device as "Unformated" and present the Format button.

 

- If the MBR is not the above, but device does not mount, we mark the device with a new status, call it "Unformatted*".  Devices marked Unformatted* will not be included with those marked Unformatted.  Instead, user can click on device info page for that device and learn why unraid thinks it's unformatted.

 

We also are adding a button called 'Wipe FS' which will wipe any file system from a device and clear the MBR.  This can be used to change a device Unformatted* status to Unformatted.

 

new status, call it "Unformatted*".  Devices marked Unformatted*

 

Wouldn't unmountable be a better status?

 

The device could be formatted, but unmountable due to unclean shutdown.

 

 

Unformatted and Unformatted* Seem too close to one another to help discern the real state

Agree with WeeboTech => the names are too close.

 

  • Author

Agree with WeeboTech => the names are too close.

 

How about instead of Unformatted we have [glow=red,2,300][shadow=red,left]Unformatted[/shadow][/glow]

 

Yeah I wasn't really going to use unformatted*, just a placeholder.

Agree with WeeboTech => the names are too close.

 

I had to read it twice to spot the difference. You absolutely cant use these two names they are too close. unmountable is WAY better

Based on Tom's latest comment, I think it's clear his original suggestion for an alternate name was a big "tongue-in-cheek"  :)

 

Not sure just what he'll really use, but I think it's safe to say it will also NOT be [glow=red,2,300][shadow=red,left]Unformatted[/shadow][/glow]

 

'

Agree with WeeboTech => the names are too close.

 

How about instead of Unformatted we have [glow=red,2,300][shadow=red,left]Unformatted[/shadow][/glow]

 

Yeah I wasn't really going to use unformatted*, just a placeholder.

how about "not mounted" or "cannot be mounted"

"mount failed"

 

How about a poll ;)

How about "a drive formally known as unmounted"

How about "a drive formally known as unmounted"

 

fixed that for ya  :P

maybe the term that could be used from unraid's perspective is claimed / unclaimed?

Archived

This topic is now archived and is closed to further replies.

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.