Hot answers tagged

25

There's an interesting intersection of server design, disk technology and economics here: Also see: Why are Large Form Factor (LFF) disks still fairly prevelant? The move toward dense rackmount and small form-factor servers. E.g. you don't see many tower offerings anymore from the major manufacturers, whereas the denser product lines enjoy more frequent ...


5

There are at least a few things that could cause problems with SOME drive types: Drives that are not meant to deal with the vibration load of a chassis having many drives (unlikely problem with any drive specified as RAID/NAS-capable) Firmware that does not allow TLER, or needs time-consuming manual reconfiguration of the drive to enable it (ditto) Drives ...


4

HUGE issue: (May be a teeny bit off-topic - but I'ts imporant!) When you are dealing with SSDs - (as is often the case, or may be either the case or temptation) - a lot of SSDs have a nasty problem where they cannot always recover from spontaneous power outages! This is a tiny problem with HDDs. HDDs usually have enough capacitance to power their logic ...


4

Try command | stdbuf -o5M cut -b- For 5MiB output buffering. See man stdbuf for a list of options. Note this doesn't work with tee which overrides the the buffer modes.


2

You would use the cheap HP SATA SSDs for boot. They're not fast. But they work just fine for the purpose. (It's clearly an Intel SATA drive) SATA is fine in this case because there's no need for dual-port SAS disks in an internal server backplane (no failover or multipath needs).


2

That's just the tray. If you still have the bad drive, take it out of the tray and put the new drive in the same tray (assuming that the drive itself is bad and not the tray, of course).


2

"COMPARE AND WRITE" opcode usually means that your writing queue is continuously growing because of low disk write performance. The reason for such behavior may be a very highly loaded OS (Synology DSM) or faulty disk drive assuming that network connection from your ESX host to NAS is OK. First of all check CPU/RAM usage on your Synology box. Also check the ...


1

Onboard Sata/AHCI is hotplug capable but this is disabled in OmniOS per default: To enable add the following line to /etc/system set sata:sata_auto_online=1


1

You can try running: sudo apt-get autoremove This command removes packages that were installed by other packages and are no longer needed. I assume you have unused kernel images making boot partition full. And if you can't run the above command then you will need to clean /boot partition manually. First you can use the following command to find out ...


1

It's possible to set on the kernel command line with e.g. elevator=deadline. I don't know for sure, but I consider it very unlikely that the default changed between 573.3.1 and 573.8.1 of Red Hat's 2.6.32 kernel. You can inspect your kernel command line by reading /proc/cmdline.


1

You need to extend the extended partition (4) first. Then you can extend/replace the logical ones.


1

+1 on VM reboots when adding disks to running hosts... Added 22 disks to 22 hosts about half rebooted or entered a stuck state and had to be forcibly rebooted. uname -a 3.10.0-123.13.2.el7.x86_64 #1 SMP Thu Dec 18 14:09:13 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux waagent --version WALinuxAgent-2.0.14 running on centos Openlogic CentOS 7.1 Wanted to add an ...



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