Freenas 8.3 Beta1 not detecting faulty/disconnected disks

[mephisto]

Hi there,

I was testing the new version of freenas on a custom box I recently put together ( HP ML350G5 with a LSI2008 in IT mode) and I noticed while testing disaster recovery, if I disconnect the disks freenas doesn't acknowledge the removal on the web interface and doesn't kick in the hot spares. I removed a few other disks and the same thing happened. On the console, I can clearly see the messages about eh disks being disconnected.

Is this some sort of bug?

Thanks

 

[cyberjock]

I've seen the same thing on my Highpoint controllers(all of them) and I thought it was just my controllers. Perhaps this warrants more investigation. Maybe a developer can comment on whether this is an expected condition or how we might be able to prevent this. I'd REALLY like to have a drive fail and know it via the UI.

 

[mephisto]

I've seen the same thing on my Highpoint controllers(all of them) and I thought it was just my controllers. Perhaps this warrants more investigation. Maybe a developer can comment on whether this is an expected condition or how we might be able to prevent this. I'd REALLY like to have a drive fail and know it via the UI.

which version are you using?

 

[cyberjock]

Duplicate.. see below.

 

[cyberjock]

I have a 2220, 2320, 3560 and 4320. The 2220 and 2320 were configred as "Legacy Disks". JBOD is not supported. The 3560 and 4320 were configured in Non-RAID mode.

All were using 8.2-RELEASE x64 and the 8.3-nightly and beta1 x64.

I just found this....

https://support.freenas.org/ticket/493

 

[mephisto]

I have a 2220, 2320, 3560 and 4320. The 2220 and 2320 were configred as "Legacy Disks". JBOD is not supported. The 3560 and 4320 were configured in Non-RAID mode.

All were using 8.2-RELEASE x64 and the 8.3-nightly and beta1 x64.

I just found this....

https://support.freenas.org/ticket/493

In my case, were all SAS drives, HP 10k 73GB, 8 of them. Controller LSI SAS2008

 

[cyberjock]

The fact that we see the same behavior is what interests me. It shows that the issue is not necessarily limited to the hardware.

 

[mephisto]

I'm going to test it now on a Dell 2950 with a PERC 5/I, just flashing the card to IT firmware now then I'll do the same tests I did on the HP ML350.

 

[mephisto]

I was testing taking more disks out and screwing up the raidz array, I can't access it or do anything but freenas still show as healthy, funny :)

 

[cyberjock]

LOL That's funny.

 

[mephisto]

Well I tested the PERC 5/i with each disk presented as raid0, tested taking the disk out and the console again reported everything and the virtual disk was deleted. On the web GUI, nothing, array still healthy, no alarm or anything.

Very much annoying that the first principle of freenas was to have redundancy, I can't even use the very basic features.

 

[cyberjock]

Hmm. Interesting. I wonder if the issue is with the hardware or software. It could be that the RAID controller is not reporting that the disk is disconnected to the appropriate mechanism that gives you the GUI warnings.I'm interested to know more because I have never seen the GUI work properly. Of course, I've always used RAID controllers(some in JBOD mode).

I wouldn't be surprised if FreeNAS configurations that use RAID controllers that use a single disk RAID0 don't work correctly, but I'd expect that for JBOD it would work fine.

I hope the developers take a look at this thread and can comment on it.

 

[mephisto]

Well, actually this happens on 8.2 as well



4 drives disconnected, nothing .... Where is your data pal?

 

[cyberjock]

Hmm. I really wish a developer could comment on this. Perhaps this is a known issue, perhaps not.

I know I've only used FreeNAS with Highpoint RAID controllers and I thought that the problem was somehow related to RAID or Highpoint. I've tried using Non-RAID mode or "Legacy Disks" as appropriate. I've done "test" failures of every setup I've built by pulling a drive out of the bay while the system is operating. I've never had the GUI respond with the yellow warning light after pulling a drive out. /shrug

This definitely warrants more testing, and hopefully a developer can comment on what the "expected" response is from FreeNAS. It could be that what we would expect as a response is not what the developers expected.

Where's a developer comment? :D

 

[mephisto]

I'll test tomorrow on VMware, if it doesn't work... well then I'll head back to solaris as before with nappit

 

[ProtoSD]

Hmm. I really wish a developer could comment on this. Perhaps this is a known issue, perhaps not.

I know I've only used FreeNAS with Highpoint RAID controllers and I thought that the problem was somehow related to RAID or Highpoint. I've tried using Non-RAID mode or "Legacy Disks" as appropriate. I've done "test" failures of every setup I've built by pulling a drive out of the bay while the system is operating. I've never had the GUI respond with the yellow warning light after pulling a drive out. /shrug

This definitely warrants more testing, and hopefully a developer can comment on what the "expected" response is from FreeNAS. It could be that what we would expect as a response is not what the developers expected.

Where's a developer comment? :D

Not a developer, but this is a known issue... search ;)

zfsd is supposed to be the fix, but supposedly won't be integrated until FreeNAS 9.... :(

 

[cyberjock]

I've done alot of searching. Now that I know to search for zfsd I'll definitely do some reading! Can't wait!

 

[mephisto]

Not a developer, but this is a known issue... search ;)

zfsd is supposed to be the fix, but supposedly won't be integrated until FreeNAS 9.... :(

Does this happen in any hardware configuration then?

 

[mephisto]

Hum, I read a bit too, now I got the reason.

In my opinio that is the last bit remaining for freenas catchup with any other solution out there.

Shame I can't have the same web interface on solaris

 

[cyberjock]

It wouldn't stop me! All I have to do is keep an eye on the server for now. The update will come and I can cope for now. I wouldn't abandon such a great software package because of this issue. It'll come. What I'd really hate is to go to solaris and be stuck there for the next several years while FreeNAS might have this fixed in a year or less.