Google for the following strings to find, watch and control live video- web- CC- cams. And … learn how to secure your network ;-)
Short tutorial on how to connect, format, mount, detach and reconnect external USB disks.
The used disk is WD20EARS connected to a USB port via Sharkoon Quickport Pro cradle.
Basically, you need only two commands:
- rmformat – to determine the device name/path
- zpool – to do the rest (create ZFS, mount, attach and detach)
The bottom line – Sweex PU202 (eSATA PCI express card) based on Sil3515 chipset is not supported by nv_125.
Both cfgadm and prtdiag see that there is something in the slot:
Ap_Id Type Receptacle Occupant Condition
pcie1 pci-pci/hp connected configured ok
. . .
ID Status Type Description
— ——— —————- —————————-
2 in use PCI Express PCIE2
“format -e” does not see the disk connected to that card.
- QNAP TS-439 Pro NAS with 4 x WD20EADS in RAID-5
- eSATA/USB Sharkoon QuickPort Pro SATA cradle
- 1.7TB data on RAID-5
Guess, how long will it take to back up 1.7TB of mostly big files to a directly connected eSATA disk using standard GUI commands?
Continue reading “QNAP NAS, eSATA , Solaris and backing up”
I thought that nothing could be easier on Solaris than to mount a directory from a QNAP NAS (running Linux). Ha! Nope… Here’s some gotchas.
Some CPU’s and system boards allow you to change operating voltage and frequency, resulting in a corresponding change in performance, and power consumed.
Adam Savage and Jamie Hyneman used their MythBuster’s approach to demonstrate the difference between CPU and GPU at Nvision 08.
What to choose for a home server? The most important difference is not the accelerometers or MTBF but whether the disks will be used in RAID’s.
An excerpt from Western-Digital FAQ:
When an error is found on a desktop edition hard drive, the drive will enter into a deep recovery cycle to attempt to repair the error, recover the data from the problematic area, and then reallocate a dedicated area to replace the problematic area. This process can take up to 2 minutes depending on the severity of the issue. Most RAID controllers allow a very short amount of time for a hard drive to recover from an error. If a hard drive takes too long to complete this process, the drive will be dropped from the RAID array. Most RAID controllers allow from 7 to 15 seconds for error recovery before dropping a hard drive from an array. Western Digital does not recommend installing desktop edition hard drives in an enterprise environment (on a RAID controller).
Western Digital RAID edition hard drives have a feature called TLER (Time Limited Error Recovery) which stops the hard drive from entering into a deep recovery cycle. The hard drive will only spend 7 seconds to attempt to recover. This means that the hard drive will not be dropped from a RAID array.
If you install a RAID edition hard drive in a desktop computer, the computer system may report more errors than a normal desktop hard drive (due to the TLER feature). Western Digital does not recommend installing RAID edition hard drives into a desktop computer environment.