Is there way to force rescan disks so that they show up in FreeNAS WebUI

[Jimm Chen]

As I found out in my previous post, hard disks hot inserted into DELL PERC H730 RAID card does not show up in FreeNAS(9.3-20150604) WebUI -> Storage -> View Disk. The same symptom exists when I hot remove a disk. But the system does know the newly inserted/removed events because WebUI Replace Disk section can show me the newly inserted disk.

So I'd need at least a workaround, for example, forcing FreeNAS WebUI to reload the disk information, restarting a system component etc. Can I?

 

[cyberjock]

AFAIK the "jbod" mode of the card is not jbod at all, so you shouldn't even be using that card.

If this is correct, that explains why 'view disk' doesn't list the disk. The controller is a RAID controller and the expectation is that the RAID controller manages the disk, so you'd have to use whatever tools may exist from the CLI or reboot and go into the controller itself.

But you should be way more than a little freaked out about that controller. That's going to eventually lead to a bad day and probably a corrupted and inaccessible zpool.

If you post a debug file (System -> Advanced -> Save Debug) I can tell you if my suspicions are confirmed.

 

[Jimm Chen]

Thank you for your hint. Please help check my log files:

debug-freenas_r730-20150727-before.tgz: The log before I do disk hot insert.
debug-freenas_r730-20150727-after.tgz: The log after I have inserted an 5TB SATA disk.

Two sets of logs so that you can easily see diff to see what happens after disk insertion .

 

[Ericloewe]

AFAIK the "jbod" mode of the card is not jbod at all, so you shouldn't even be using that card.

Some people have reported that the JBOD mode works well, SAS3 caveats aside. It's definitely something that merits some investigation once a suitable guinea pig shows up.

The above is not an endorsement of the Perc H730, any Perc card or any SAS3 controller.

In this case, though, the mfi driver is being used. Which sounds odd, since mpr was supposedly a unified IT/IR/RAID driver. SMART data is inaccessible, which can be (and almost always is) disastrous.

 

[cyberjock]

What @Ericloewe said.

But, you are virtualizing FreeNAS. That's probably my number one rule to not break. Virtualizing is already documented throughout the forum as a dangerous game and is "at your own risk". I personally do not endorse, or troubleshoot problems with virtualized FreeNAS installations because it adds complexity that is just not worth my time.

Your RAID controller is totally unacceptable though and will probably be the demise of your zpool someday.

But if you stopped virtualizing FreeNAS, got a proper RAID controller, and did things like we recommend you'd probably find the behavioral issues are corrected.