Firstly, I am very new to nas4free, and am just getting my head around some of the terminology and methods (i'm primarily an Arch linux user, not a freebsd user) so forgive me if this is in the wrong place, or has been answered elsewhere (couldn't find it)
I setup nas4free, v9.1.0.1 embedded on a 2GB Kingston Datatraveller, its usb2 and in a usb2 slot
everything seems to work fine...but my logs show quite a few of these entries
May 27 18:04:02 elephantine kernel: (da0:umass-sim0:0:0:0): Retrying command (per sense data)
May 27 18:04:02 elephantine kernel: (da0:umass-sim0:0:0:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0
May 27 18:04:02 elephantine kernel: (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error
May 27 18:04:02 elephantine kernel: (da0:umass-sim0:0:0:0): SCSI status: Check Condition
when I google it, I only see a reference to freebsd that this is a quirk in the Kingston DataTravellers. But is it a serious quirk?
Is this something I should be worried about? Should I swap this out for a different usb stick? Since I am still in the building and setup phase, it wouldn't be a serious effort to replace.
Just curious if anyone has any imput on this
And for the devel team. WOW, I am so far really, really impressed by what I am seeing so far with nas4free, keep up the good work.
This is the old XigmaNAS forum in read only mode,
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
question about log entries related to usb flash
-
corvisrex
- NewUser
- Posts: 3
- Joined: 27 May 2013 22:24
- Status: Offline
-
kkd
- Forum Moderator
- Posts: 306
- Joined: 08 May 2013 21:47
- Location: Budapest, Hungary
- Contact:
- Status: Offline
Re: question about log entries related to usb flash
if i were u i replace it.
XigmaNAS x64-embedded | INTEL Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz | 9216MiB RAM | X x YTB WD Red ZFS mirror compressed
-
kkd
- Forum Moderator
- Posts: 306
- Joined: 08 May 2013 21:47
- Location: Budapest, Hungary
- Contact:
- Status: Offline
Re: question about log entries related to usb flash
same saiz it doest like the synronize cache commands. and another 2gb usb is cheap.
XigmaNAS x64-embedded | INTEL Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz | 9216MiB RAM | X x YTB WD Red ZFS mirror compressed
-
corvisrex
- NewUser
- Posts: 3
- Joined: 27 May 2013 22:24
- Status: Offline
Re: question about log entries related to usb flash
Thanks for the reply. What I figured, even if not a serious issue, be to swap it out just to be safe. Not too much trouble I have more than a few new flash drives sitting around, just still getting used to nas4free and embedded systems in general.
-
corvisrex
- NewUser
- Posts: 3
- Joined: 27 May 2013 22:24
- Status: Offline
Re: question.. update
For other peoples future reference...
the Kingston DataTraveller I was using was listed in the logs as having USB revision 2.00/1.00 with quirks = 0x0100
I switched to a usb stick listed as revision 2.00/2.00 which showed quirks = 0x4100
This new one works great, without the errors.
rev 2.00/1.00 usually denotes more cheaply made sticks (or so I understand), but it probably had something to do with the umass quirk 0x0100, I tried another stick with the same quirk and it gave the same errors. so quirk=0x0100 gave me errors, quirk 0x4100=no errors, at least for me.
the Kingston DataTraveller I was using was listed in the logs as having USB revision 2.00/1.00 with quirks = 0x0100
I switched to a usb stick listed as revision 2.00/2.00 which showed quirks = 0x4100
This new one works great, without the errors.
rev 2.00/1.00 usually denotes more cheaply made sticks (or so I understand), but it probably had something to do with the umass quirk 0x0100, I tried another stick with the same quirk and it gave the same errors. so quirk=0x0100 gave me errors, quirk 0x4100=no errors, at least for me.