Added 'Remove Global Format Button' to the OP.  Also very important, and I completely agree that it is an issue.

 

If FTP is already a part of unRAID and it works, then I agree that it should not be removed.  However, I've heard users state that it doesn't really work out of the box, and it therefore more of an add-on.  In this light, I don't see it as much of a priority.

 

Delete Existing Parity Data and Disk Configuration.

 

Yes, it is longer, but more accurate, and perhaps as unlikely to be pressed when a disk has failed.

Joe L.

 

I'm happy with that.  My logic is that anything with the word 'delete' in it will discourage users from pressing it without being 100% sure about what they are doing.

 

My only thought is that we might see a bunch of posts from new users asking 'why is there a button that will delete all my data?'  We would then have to explain parity, etc, etc.  A small price to pay, IMO.

 

Both of those should be put in a patch and distributed.  The rest could probably be addons in unRAID 5.0.

Agreed.  However, the purpose of this thread is to push for the items on this list to be part of the stock unRAID 5.0 package, NOT add-ons.

I'd have to totally agree with Rajahal's first post of this thread and say that those commonly used addons should for sure be integrated into the newer version of unRAID release v5.0. The renaming of some critual buttons is a very good point and should of been addressed a while a go seeing it causes problems for the some inexperienced users.

The 'not' so required addons mentioned, I would to agree and say yeah leave them as still addons, like unMENU and VMware Server. Other points mentioned in this thread about basic help functions would be a great idea too. You could have both a PDF file as part of the unRAID OS download when it is downloaded in a single zipped file but I strongly feel that having an embedded HTML help built into the unRAID web GUI on features like a hyperlink underneath a certain function or option and when you click on it it opens a new tab/windows in your browser and gives you the meaning, what it does and how to use instructions, an example would be Endian Community Firewall web interface and the way it integrates the help into it's web GUI. Good point Rajahal and others about this topic thus far.

Rename the RESTORE button - SET INITIAL CONFIGURATION. 

Added to the top of the list, can't believe I forgot that one.  It isn't really an add-on, I suppose, but in some ways it is more important that the rest.  However, to my mind 'Set Initial Configuration' sounds too complex as well.  As an inexperienced unRAIDer, I'm not sure I would understand what that means.  I would propose instead renaming it to something simple like:

'Delete Parity Data'

Then in the description the reason why one may want to do this could be outlined.

 

Rename the RESTORE button - SET INITIAL CONFIGURATION. 

Yes!!!!!!!

Add to the description: DO NOT USE IF YOU INTEND TO RECONSTRUCT THE CONTENTS OF A FAILED DRIVE ONTO A REPLACEMENT, AS PRESSING THIS BUTTON IMMEDIATELY INVALIDATES PARITY. IF YOU INVALIDATE PARITY, YOU WILL NOT BE ABLE TO USE PARITY TO RECONSTRUCT AN OLD DISK's CONTENTS.

I agree with your description, but again, I don't agree with the new proposed button name.  I would name it 'Delete Parity Data' and add in a line to your description:

ONLY PRESS THIS BUTTON IF YOU WANT TO DECREASE THE NUMBER OF DATA DISKS IN YOUR ARRAY.  DO NOT USE IF YOU INTEND TO RECONSTRUCT THE CONTENTS OF A FAILED DRIVE ONTO A REPLACEMENT, AS PRESSING THIS BUTTON IMMEDIATELY INVALIDATES PARITY. IF YOU INVALIDATE PARITY, YOU WILL NOT BE ABLE TO USE PARITY TO RECONSTRUCT AN OLD DISK's CONTENTS.

 

I would respectfully disagree with any wording using 'Delete', because it is NOT deleting anything.  There are no changes made to the parity disk or any other disk.  Technically, it may also be inaccurate to say it "invalidates parity", although we know what is meant.  Using "delete" would also make it more confusing when this button is used as an important early step in the Trust My Array procedure.

 

While not intuitive, "Set Initial Configuration" more accurately reflects what really happens.  I do agree that we need a better wording, but it should be one that is accurate, then fully explained for the newest user.  Alternatives could be "Set new array" or "Set new array assignments", etc.  What really happens is, the previous array configuration (if any) is cleared, and a new array is established based on the current drive assignments from the Devices tab.  All disks are marked as new (blue status balls), and if a parity drive has been configured, then a parity build is scheduled when the array is next started.  When the user then starts the array, all data disks are examined and marked as valid disks (green status balls) and the parity build proceeds.

 

The Trust My Array procedure works by using a trick, that first establishes a new array (using this "Restore" or "Set new array" button), but then indicates to it that the parity drive is already built (so skip building it), then starts a parity check to verify.

 

An all-capitalized warning (like the suggestions above) is a good idea to add to the button, but I'm not sure of the wording.

Rename the RESTORE button - SET INITIAL CONFIGURATION. 

Added to the top of the list, can't believe I forgot that one.  It isn't really an add-on, I suppose, but in some ways it is more important that the rest.  However, to my mind 'Set Initial Configuration' sounds too complex as well.  As an inexperienced unRAIDer, I'm not sure I would understand what that means.  I would propose instead renaming it to something simple like:

'Delete Parity Data'

Then in the description the reason why one may want to do this could be outlined.

 

Rename the RESTORE button - SET INITIAL CONFIGURATION. 

Yes!!!!!!!

Add to the description: DO NOT USE IF YOU INTEND TO RECONSTRUCT THE CONTENTS OF A FAILED DRIVE ONTO A REPLACEMENT, AS PRESSING THIS BUTTON IMMEDIATELY INVALIDATES PARITY. IF YOU INVALIDATE PARITY, YOU WILL NOT BE ABLE TO USE PARITY TO RECONSTRUCT AN OLD DISK's CONTENTS.

I agree with your description, but again, I don't agree with the new proposed button name.  I would name it 'Delete Parity Data' and add in a line to your description:

ONLY PRESS THIS BUTTON IF YOU WANT TO DECREASE THE NUMBER OF DATA DISKS IN YOUR ARRAY.  DO NOT USE IF YOU INTEND TO RECONSTRUCT THE CONTENTS OF A FAILED DRIVE ONTO A REPLACEMENT, AS PRESSING THIS BUTTON IMMEDIATELY INVALIDATES PARITY. IF YOU INVALIDATE PARITY, YOU WILL NOT BE ABLE TO USE PARITY TO RECONSTRUCT AN OLD DISK's CONTENTS.

 

I would respectfully disagree with any wording using 'Delete', because it is NOT deleting anything.  There are no changes made to the parity disk or any other disk.  Technically, it may also be inaccurate to say it "invalidates parity", although we know what is meant.  Using "delete" would also make it more confusing when this button is used as an important early step in the Trust My Array procedure.

 

While not intuitive, "Set Initial Configuration" more accurately reflects what really happens.  I do agree that we need a better wording, but it should be one that is accurate, then fully explained for the newest user.  Alternatives could be "Set new array" or "Set new array assignments", etc.  What really happens is, the previous array configuration (if any) is cleared, and a new array is established based on the current drive assignments from the Devices tab.  All disks are marked as new (blue status balls), and if a parity drive has been configured, then a parity build is scheduled when the array is next started.  When the user then starts the array, all data disks are examined and marked as valid disks (green status balls) and the parity build proceeds.

 

The Trust My Array procedure works by using a trick, that first establishes a new array (using this "Restore" or "Set new array" button), but then indicates to it that the parity drive is already built (so skip building it), then starts a parity check to verify.

 

An all-capitalized warning (like the suggestions above) is a good idea to add to the button, but I'm not sure of the wording.

Respectfully, I'd go with the "Delete" wording.  You are really moving the system.dat file to system.old, so in effect you ARE deleting the old configuration and all records of the previous parity calculation. 

 

It is strongly worded enough to make a new user think twice.  It is accurate (or close to being accurate)  The act of Starting the array will then create a new super.dat file with a new configuration.  It is actually how the new .config is stored, based on the then assigned and working disks.

 

As far as it being implemented... good luck.  Tom is apparently very thick-headed and we've been requesting it be changed for several years.  He even said once he is open to suggestions for re-wording, but apparently never liked any suggestions so far. (or never found time to make the change)

 

Joe L.

I understand that 'Delete Parity Data' is not very accurate.  However, that is a minor concern for me.  I would much rather the button used some simple scary language like 'delete' so that inexperienced users will think twice before clicking it flippantly.  I think it is better that the button be labeled in an inaccurate way as long as that inaccurate way promotes good behavior.

 

As for the 'Trust My Array' procedure, I would make the following change in wording:

 

- Click the 'Delete Parity Data' button, after first checking the "I'm sure I want to do this" box.  This step makes unRAID forget its current parity data and disk configuration, and schedules a parity build for when the array is next started.  We will tell unRAID to trust the parity data in later steps.

 

Or something like that.

 

Joe. L's suggestion of 'Delete Existing Parity Data and Disk Configuration' is probably the best of both worlds - scary language, but more accurate.

Rename the RESTORE button - SET INITIAL CONFIGURATION.  

 

Guess what?

kill `pidof emhttp`
sed -i 's/Restore/Destroy/g' /usr/local/sbin/emhttp
/usr/local/sbin/emhttp &

I just tried it!  Now I have a shiny new "Destroy" button.    

(The description also changed accordingly  )

 

 

Pics please.

 

Also, instead of 'Destroy' I would name it 'Initiate Meltdown'.

Also, instead of 'Destroy' I would name it 'Initiate Meltdown'.

That was my first thought, but then I realized that a string of different length will cause a segfault in the emhttp binary.

 

We could add that patch to any package we distribute!   

 

Rename the RESTORE button - SET INITIAL CONFIGURATION.  

 

Guess what?

kill `pidof emhttp`
sed -i 's/Restore/Destroy/g' /usr/local/sbin/emhttp
/usr/local/sbin/emhttp &

I just tried it!  Now I have a shiny new "Destroy" button.    

(The description also changed accordingly  )

 

That's gutsy.  I'd never think to stream edit a binary.  (I'd use "dd")

 

Joe L.

hehe, I just changed my button via mc, come back here and find these posts

Guess what?

kill `pidof emhttp`
sed -i 's/Restore/Destroy/g' /usr/local/sbin/emhttp
/usr/local/sbin/emhttp &

I just tried it!  Now I have a shiny new "Destroy" button.   

(The description also changed accordingly  )

 

That's gutsy.  I'd never think to stream edit a binary.

LOL Joe!  I can see how such heresy must have shocked you! 

Just be thankful I didn't do that on bzroot directly, could have given you a heart attack.   

 

Gotta post a pic... !!!! 

Gotta post a pic... !!!! 

 

sed -i 's/Restore/Destroy/g' /usr/local/sbin/emhttp

 

Is now in the beginning of my go file

Why it should be renamed to 'Crush, Kill, Destroy!' with a little description of what it really does, just for kicks, I've love to see an actual pic of that

Why it should be renamed to 'Crush, Kill, Destroy!' with a little description of what it really does, just for kicks, I've love to see an actual pic of that

Such pic won't be real.  It can't be done for real without recompiling emhttp, and that's not open source.

So it can be done for real only by Limetech.

 

Maybe it could be included as a Feature Request in v5 for unRAID :-). So you can only rename by one word, from Format to another word?

Maybe it could be included as a Feature Request in v5 for unRAID :-). So you can only rename by one word, from Format to another word?

The proper way to change text is if unRAID had support for different languages.

Then all the strings would be in separate text-only files, easy for customizations.

There's a feature request for you.

 

Maybe it could be included as a Feature Request in v5 for unRAID :-). So you can only rename by one word, from Format to another word?

And only if the replacement word is the same length as the original.

Ok, time to get creative with a replacement word to replace 'Restore' with then .

While at it why not replace unformatted with something less?

While at it why not replace unformatted with something less?

unformatted simply means not-mounted

 

unformatted = 11 characters

not mounted = 11 characters

 

Joe L.

While at it why not replace unformatted with something less?

unformatted simply means not-mounted

Not really! Well, it means that in theory, but in practice 4.5.3 does treat them as unformatted,

as it will try to format them if you press that unfortunate button.

 

---

We don't want to rename the format button, we want to get rid of it.

It shouldn't be such single button that applies to all disks at the same time.

 

While at it why not replace unformatted with something less?

unformatted simply means not-mounted

Not really! Well, it means that in theory, but in practice 4.5.3 does treat them as unformatted,

as it will try to format them if you press that unfortunate button.

 

So, we don't want to rename the format button, we want to get rid of it.

It shouldn't be such single button that applies to all disks at the same time.

 

 

Yes, on second thought it's better to get rid of it.  The way I deal with it is I format new drives in unMenu.  Then if a drive is labled unformatted in unRAID I know it's bogus.

Maybe it's possible to replace HTML in the same way you replaced the Restore button text.

While at it why not replace unformatted with something less?

unformatted simply means not-mounted

Not really! Well, it means that in theory, but in practice 4.5.3 does treat them as unformatted, as it will try to format them if you press that unfortunate button.

 

So, we don't want to rename the format button, we want to get rid of it.

It shouldn't be such single button that applies to all disks at the same time.

 

unRAID attempts to mount the first partition on a disk as a reiserfs.  If it cannot, for ANY reason, it considers it un-formatted.

 

It might have been replaying journal transactions, it might have an NTFS file system, it might have a corrupted reiserfs file-system that did not mount.  It might be it did not allocate enough time for the mount to complete before determining the mount failed.  It could even be that it is not formatted.  

 

UnRAID should track the disks it has formatted and added to the array.  It would only take one more line per disk in the disk.cfg file.

DeviceFormatted=SERIAL/MODEL

 

It could use the vol_id command to test for a file system.  There's lots of ways I can think of, and probably lots more I do not know about.

It could write a signature to the unused blocks at the beginning of a reiser file-system it has created.  That, if present could prevent it from showing as un-formatted, but instead un-mounted.