CLSegraves
Explorer
- Joined
- Sep 13, 2013
- Messages
- 84
I'll post this here since it's kind of a noob question. My nas generated the following security run output last night
and I'd appreciate it if someone would take a quick look at it and
1) tell me what's going on
2) tell me if there is anything I need to be concerned about/correct/etc.
Everything seems to be working fine.
Thanks,
Chris
edit: I should mention I momentarily pulled a drive yesterday to check a model number. That put the pool in degraded state, however I reinserted and rebooted to clear the 'error'. Other than that, the nas has not been touched since I reassembled it last week (moved it from a big desktop case to a smaller hot swap nas case).
Code:
NAS01.local kernel log messages: > ada1 at ahcich3 bus 0 scbus3 target 0 lun 0 > ada1: <ST2000DM001-1CH164 CC27> s/n Z340AF2K detached > Waiting (max 60 seconds) for system process `vnlru' to stop...done > Waiting (max 60 seconds) for system process `bufdaemon' to stop...done > > Waiting (max 60 seconds) for system process `syncer' to stop...Syncing disks, vnodes remaining...2 0 0 0 done > All buffers synced. > GEOM_ELI: Device ada1p1.eli destroyed. > GEOM_ELI: Detached ada1p1.eli on last close. > (ada1:ahcich3:0:0:0): Periph destroyed > ada1 at ahcich3 bus 0 scbus3 target 0 lun 0 > ada1: <ST2000DM001-1CH164 CC27> ATA-9 SATA 3.x device > ada1: Serial Number Z340AF2K > ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) > ada1: Command Queueing enabled > ada1: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C) > ada1: quirks=0x1<4K> > ada1: Previously was known as ad10 > Timecounter "TSC-low" frequency 1247193782 Hz quality 1000 > GEOM_ELI: Device ada0p1.eli created. > GEOM_ELI: Device ada1p1.eli created. > vboxdrv: fAsync=0 offMin=0x2e8 offMax=0xc74 -- End of security output --
and I'd appreciate it if someone would take a quick look at it and
1) tell me what's going on
2) tell me if there is anything I need to be concerned about/correct/etc.
Everything seems to be working fine.
Thanks,
Chris
edit: I should mention I momentarily pulled a drive yesterday to check a model number. That put the pool in degraded state, however I reinserted and rebooted to clear the 'error'. Other than that, the nas has not been touched since I reassembled it last week (moved it from a big desktop case to a smaller hot swap nas case).