understanding security run output.

[PenalunWil]

I received this security run output last night. Am I correct in assuming that this is a USB drive failure, and I should be looking to replace it?...


Wilsfreenas.local kernel log messages:
> ugen0.3: <vendor 0x0000> at usbus0 (disconnected)
> uhub4: at uhub2, port 3, addr 3 (disconnected)
> ugen0.4: <vendor 0x0557> at usbus0 (disconnected)
> ukbd0: at uhub4, port 1, addr 4 (disconnected)
> ums0: at uhub4, port 1, addr 4 (disconnected)
> usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_SHORT_XFER
> ugen0.3: <vendor 0x0000> at usbus0
> uhub4: <vendor 0x0000 product 0x0001, class 9/0, rev 2.00/0.00, addr 3> on usbus0
> uhub4: 4 ports with 3 removable, self powered
> ugen0.4: <vendor 0x0557> at usbus0
> ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 4> on usbus0
> kbd0 at ukbd0
> ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 4> on usbus0
> ums0: 3 buttons and [XYZ] coordinates ID=0
> ugen0.4: <vendor 0x0557> at usbus0 (disconnected)
> ukbd0: at uhub4, port 1, addr 4 (disconnected)
> ums0: at uhub4, port 1, addr 4 (disconnected)
> ugen0.4: <vendor 0x0557> at usbus0
> ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 4> on usbus0
> kbd0 at ukbd0
> ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 4> on usbus0
> ums0: 3 buttons and [Z] coordinates ID=0

-- End of security output --

I have two USB boot drives one being a mirror of the main one as a back up as recommended in manual 5.3.1

thanks in advance.... Wil

 

[PenalunWil]

In addition to the above this is the first security run output after the latest update from FreeNAS.

I've just started to teach myself FreeBSD so my interpretation skills are not good.

I'm also keeping an eye on this post by gbooker ... https://forums.freenas.org/index.php?threads/supermicro-x10srl-f-o-faulty.39400/ which may or may not be of any significance.

 

[Robert Trevellyan]

Am I correct in assuming that this is a USB drive failure

What is the status of your boot pool?

 

[PenalunWil]

I re-booted my NAS box yesterday and then read your post Rob... this is the status report...

[root@Wilsfreenas ~]# zpool status -v freenas-boot
pool: freenas-boot
state: ONLINE
scan: scrub repaired 0 in 0h2m with 0 errors on Sat Nov 14 03:47:16 2015
config:

NAME STATE READ WRITE CKSUM
freenas-boot ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
gptid/800a6868-fe3a-11e4-b9d3-001e4fa58637 ONLINE 0 0 0
da7p2 ONLINE 0 0 0

errors: No known data errors

So now I'm confused as hell...

The two usb boot drives are only six months old and are Sandisk which were expemsive.

 

[PenalunWil]

I have also received this new security run out put today...

Wilsfreenas.local kernel log messages:
> CPU: Intel(R) Pentium(R) CPU G3220 @ 3.00GHz (2993.14-MHz K8-class CPU)
> Timecounter "TSC-low" frequency 1496567722 Hz quality 1000
> vboxdrv: fAsync=0 offMin=0x2c8 offMax=0xb1c

-- End of security output --

 

[Robert Trevellyan]

The security run output is related VirtualBox, so not relevant here.

It also looks like your boot pool is healthy, so the USB error you saw probably relates to another device. From my searches, one candidate is a UPS, if you have one.

By the way, it appears that you created a single-drive boot pool and then added the mirror from the command-line. If so, consider backing up your configuration and then doing a clean install to both devices at the same time, then restoring your configuration.

 

[PenalunWil]

I don't have an UPS at the moment. I know I should and I was wondering if the problem was due to a power out we had about two weeks ago.

Anyways Rob... many many thanks for your help. I'll read up on your last paragraph and implement it asap and get back if this problem returns.

 

[Robert Trevellyan]

I don't have an UPS at the moment.

Then there's a mystery to be solved.

I don't think reconfiguring the boot pool is urgent, just best practice.

 

[PenalunWil]

Then there's a mystery to be solved.

I don't think reconfiguring the boot pool is urgent, just best practice.

That's why I'm confused as hell .... :)

I did read in the link I pasted above that joeschmuck states "I'd like to tell you that USB other than for a few things is not well supported under FreeNAS " and I wondered if that was the reason behind my initial security run output. Also gbooker states "I contacted Supermicro to ask if my board was faulty and the response was to immediately blame FreeNAS." now that is very off putting for all FreeNAS noobs who are looking for hardware as this contradicts what a lot of member say is possibly the best make of mobo you can get for FreeNAS.

So I guess I'll just have to keep an eye on things and maybe a consider getting a 16GB SATA DOM as my boot drive.

 

[Bidule0hm]

USB is really a pain in the a**. Today I had a power cut and for whatever reason the server couldn't communicate with the UPS (NB: I never had a problem before) so it ended by a hard shutdown as far as I can tell (wasn't here and the logs are unclear on what happened) and when I tried to restart the UPS service, unplug/replug the USB cable of the UPS, rebooted, etc... upsmond wouldn't want to start. Then I just edited the UPS service config, restarted the service and no problem after that, WTF?! --> TL;DR use serial com if you can, serial port is just plain reliable.

And don't get me started on USB drives used as a boot drive... I tested it and now I recommend a DOM, SSD, HDD, ... instead, any day ;)

 

[Robert Trevellyan]

that is very off putting for all FreeNAS noobs

I guess I'll just have to keep an eye on things

Yes, well ...

To begin with, a lot of new mobos come with USB3, which FreeNAS 9.x doesn't support properly, so you have to be careful which ports you use.

Further, the use of external USB drives (e.g. for backup) has always been discouraged because ZFS can't get direct access to the drives.

But, until recently, USB2 has been the standard approach for boot devices. Maybe that will change.

 

[Bidule0hm]

Maybe that will change.

It should, really. :P