Brand new, precleared drive: "Unmountable: No file system"


rmp5s

Recommended Posts

I have a brand new 8TB drive that I put in and precleared.  

 

410288556_Screenshot2019-01-16at6_44_45AM.thumb.png.87e2c94b2e023e89d113510050b5db05.png

 

I want to make it my cache disk, but it's telling me, "Unmountable:  No file system".

 

1404109610_Screenshot2019-01-16at6_46_31AM.thumb.png.c4df5b89c2fb73653eb6393b3c21411f.png

 

...so I think to myself, "cool.  I just need to format it" but the "format" button is greyed out.

 

What am I missing here...???

Edited by rmp5s
Link to comment
10 hours ago, johnnie.black said:

That's weird, try rebooting, if still the same post diags, maybe something visible there.

That did the trick.  Thanks!

 

9 hours ago, jonp said:

There should be a checkbox that's near the button that you have to click in order for the button to become clickable.

Sent from my Pixel 3 XL using Tapatalk
 

Nope.  There is not checkbox, as can be seen in the screenshot above.  It was just a glitch.  Solved by a reboot.

Link to comment
26 minutes ago, rmp5s said:

That did the trick.  Thanks!

 

Nope.  There is not checkbox, as can be seen in the screenshot above.  It was just a glitch.  Solved by a reboot.

That screenshot is showing the Format button for an Unassigned Device. Totally different thing than formatting a drive assigned to a cache slot. Not what you needed to do but to format an Unassigned Device you must enable "destructive mode" in Settings for Unassigned Devices.

 

What you needed to do was get Unraid to format the disk AFTER you assign it to a cache slot. The checkbox to enable format in that case is in Main - Array Operations.

Link to comment
On 1/16/2019 at 6:14 PM, trurl said:

That screenshot is showing the Format button for an Unassigned Device. Totally different thing than formatting a drive assigned to a cache slot. Not what you needed to do but to format an Unassigned Device you must enable "destructive mode" in Settings for Unassigned Devices.

 

What you needed to do was get Unraid to format the disk AFTER you assign it to a cache slot. The checkbox to enable format in that case is in Main - Array Operations.

Yea, I just noticed that the dashboard says "parity disk not present" even though I have the new 8TB assigned as a cache drive.

 

Guess that's why?  

 

Not seeing a format checkbox, though.

 

Array stopped:

 

369977189_Screenshot2019-01-17at8_51_57PM.thumb.png.1b7d0212477b6e78613c3fbaeec6bebd.png

 

Array running:

 

1407285705_Screenshot2019-01-17at8_53_16PM.thumb.png.2edceb4ae1f47d6d89fd7ccbeec88047.png

 

Am I missing something?

Link to comment
18 minutes ago, rmp5s said:

I just noticed that the dashboard says "parity disk not present" even though I have the new 8TB assigned as a cache drive.

Parity and cache have nothing to do with each other. The whole point of cache is it is not part of the parity array.

 

Also, 8TB is an unusually large disk to assign as cache. Do you perhaps really intend to assign that disk as parity?

Link to comment
10 hours ago, Squid said:

Post a screen shot of the Array Devices and Cache section of the Main tab

 

604656686_Screenshot2019-01-18at7_14_24AM.thumb.png.94e27a11e69c9cefd6dc43e80c18c94c.png

 

9 hours ago, trurl said:

Parity and cache have nothing to do with each other. The whole point of cache is it is not part of the parity array.

 

Also, 8TB is an unusually large disk to assign as cache. Do you perhaps really intend to assign that disk as parity?

 

Oh...I thought the two were the same.  Just looking for some fault tolerance and I thought the parity drive had to be as big as your biggest array drive.  Mine (for now) will be 8TB.

Link to comment
6 minutes ago, rmp5s said:

 

604656686_Screenshot2019-01-18at7_14_24AM.thumb.png.94e27a11e69c9cefd6dc43e80c18c94c.png

 

 

Oh...I thought the two were the same.  Just looking for some fault tolerance and I thought the parity drive had to be as big as your biggest array drive.  Mine (for now) will be 8TB.

No - they are completely different.    The parity is about protecting the array disks and you are correct in it needing to be at least as large as the largest data disk,

 

Cache disk is about providing higher performance storage for running apps/VMs and for the initial write of new files.  If you DO want a cache disk then it is typical (although not required) to use a SSD as this gives the highest performance.   A cache disk has no minimum or maximum size requirement - you determine what meets your basic usage pattern.   If the cache disk is a single drive then it has no redundancy (many are happy with this).   A cache can also be run as a 'pool' of multiple drives which gives redundancy if that is important for the files that you place on there.   However be aware if running a pool with more than one drive that this requires the cache to be formatted as BTRFS and that has proved more fragile and prone to corruption that XFS.

 

Not sure what you have put on the cache disk so far.    If you want to repurpose the current cache disk for use as a parity disk, then you make sure that the VM and docker services are stopped; set any shares that might be using the cache disk to Use Cache=Yes (if this sounds counter-intuitive turn on the GUI help to see what the actual affect of this setting is) and then run mover to get any files currently on the cache disk moved back to the array.    After doing that you can stop the array; unassign the cache disk; re-assign the drive as parity1; start the array to start building parity  (it will probably take most of a day with a 8TB drive.).   At this point you can re-enable the docker and/or VM services if you use them.  You could then later add a smaller drive as cache (assuming you want one).

Link to comment
1 hour ago, rmp5s said:

Oh...I thought the two were the same 

If you stop the array you should see the proper place to assign your parity disk, just above disk1. It is clearly labeled Parity, whereas Cache is also clearly labeled and a completely different section on the Main page.

 

Did you follow any sort of guide when setting up your server?

Link to comment
4 hours ago, itimpi said:

No - they are completely different.    The parity is about protecting the array disks and you are correct in it needing to be at least as large as the largest data disk,

 

Cache disk is about providing higher performance storage for running apps/VMs and for the initial write of new files.  If you DO want a cache disk then it is typical (although not required) to use a SSD as this gives the highest performance.   A cache disk has no minimum or maximum size requirement - you determine what meets your basic usage pattern.   If the cache disk is a single drive then it has no redundancy (many are happy with this).   A cache can also be run as a 'pool' of multiple drives which gives redundancy if that is important for the files that you place on there.   However be aware if running a pool with more than one drive that this requires the cache to be formatted as BTRFS and that has proved more fragile and prone to corruption that XFS.

 

Not sure what you have put on the cache disk so far.    If you want to repurpose the current cache disk for use as a parity disk, then you make sure that the VM and docker services are stopped; set any shares that might be using the cache disk to Use Cache=Yes (if this sounds counter-intuitive turn on the GUI help to see what the actual affect of this setting is) and then run mover to get any files currently on the cache disk moved back to the array.    After doing that you can stop the array; unassign the cache disk; re-assign the drive as parity1; start the array to start building parity  (it will probably take most of a day with a 8TB drive.).   At this point you can re-enable the docker and/or VM services if you use them.  You could then later add a smaller drive as cache (assuming you want one).

 

D'oh!!

Thanks, man.

 

There was nothing on the drive yet so I just kicked it out of the cache spot, deleted the partition, rebooted and added it as parity.  Parity is building now.

 

Thanks, EVERYONE!!  You guys rock!!

Link to comment
  • 11 months later...
5 minutes ago, Squid said:

Just so there's no misunderstanding, these are all new drives that you just precleared and are supposed to be empty?  You still have to format them.  There's a check box when you start the array

 

If not, then post your diagnostics

 

Ahh Got it. Formatting commencing.... See you tomorrow lmao.

Link to comment

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...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.