Tag Info

Hot answers tagged

47

Don't attempt to "wipe" an SSD with tools designed for spinning magnetic hard drives. You won't actually destroy all the data, and you'll just reduce the lifetime of the SSD. Instead, use an erase tool specifically designed for SSDs, which can use the drive's internal flash erase (discard) to discard all of the blocks, including the ones you can't access. ...


6

Hard drives do have a multitude of error correction methods in place to prevent data corruption. Hard drives are divided into sectors, from which some may become completely unwritable / unreadable or return wrong data through data corruption - let's call the first bad sector corruption and the latter silent data corruption. Bad Sector Corruption The first ...


5

Using /dev/urandom should make everything faster. I wouldn't wipe an SSD like that. SSD's usually have advanced wear leveling in place. Basically, instead of writing over the existing data, the drive writes over unused portions. It'll take a bit of time to properly scramble all the data. By that time, you would have already wore down an SSD, though it's only ...


2

/dev/random generates random data by entropy collected by your system (time delays between keyboard shortcuts, network timing by measuring the packet arrivals with nanosecond precision, etc). If there is not enough entropy, this device blocks output while it collects more entropy. /dev/urandom uses aso the collected entropy, but it uses a pseudorandom ...


2

Interesting question from a customer/end user perspective. My advice is not to use the HP DL380 G5 systems for anything today, if you can avoid it? They are unfavorable for power, performance, support and compatibility reasons. A few examples: RAM is very limited on this model. Any SATA SSD used on a Smart Array P400-era controller (2005-2008) will be ...


1

My account was a trial account. It seems SSDs are only available for full accounts.


1

From reading the diskstats plugin source, munin calculates the disk utilization percentage by looking at the total time spent doing IO over a given monitoring period. If the device is spending all it's time doing IO, then it's at 100% utilization. This is somewhat independent of actual IOPS and read/write speeds, as these will have a very access-pattern ...



Only top voted, non community-wiki answers of a minimum length are eligible