Tag Info

Hot answers tagged

3

There should be tools available to query your RAID controller and determine the SMART status of the drives in the array. Not knowing the particular device you've got, I don't have any suggestions as to what to use. Once you know what to use (and how to use it), you'll need to automate the monitoring, so it will proactively notify you when there is a ...


3

This is the problem with raidz1 (and also RAID5). If the data on the disk changes but no drive fault occurs to let ZFS or the RAID controller know which drive caused the error, then it can't know which drive is correct. With raidz2 (and higher) or RAID6, you get a quorum of drives that can decide which drive to ignore for reconstruction. Your only solution ...


3

Gparted works well, even for windows so don't worry about it ! by the way i didn't found something as powerfull as Gparted for windows. Use Gparted live to boot on the iso, the graphic interface will help you to extand your partition.


3

Depending on your case, partition layout and mount points your indexes can vary: but here is example of reporting free disk space on partitions two mounted partitions: df | grep mnt /dev/xvdz1 5160576 10236 4888196 1% /mnt /dev/xvdz2 36123264 49032 34239276 1% /mnt/test getting indexes for them from snmpwalk: snmpwalk -On -v 2c ...


2

These disks are not compatible with each other. If your existing disks are 8.9cm (3.5"), then any new disks you buy should also be 8.9cm.


2

To have the disks appear under /dev/sd*, the solution was to restart the Fibre Channel HBA driver, as stated in this answer. In my case, it was lpfc : stop lpfc driver: $ modprobe -r lpfc start lpfc driver: $ modprobe lpfc Then, my device appeared under /dev/sdb. After that, as stated by GregL, I needed to partition the device, and then format it with ...


1

You have answered the question yourself. If you have a UPS you can leave them on, if you don't then they should be off or else you risk data loss. On most servers in the datacenter they will generally be using OEM firmware that uses the cache in a read only mode. (The equivalent of off) Writes will be cached by the RAID card with battery backed memory.


1

nowadays, git-annex has its own solutions for this problem. you can use: git annex info --fast * ...to get actual disk usage (and more) from the files directly from git-annex. it can also operate on remote repositories, which is very useful: git annex info --fast --not --in here . ... would give you the amount of data that is not in the current ...


1

Michael’s answer shows that there doesn’t seem to be a way to distinguish instance disks from EBS volumes inside an AWS instance. In fact, the kernel info for instance and EBS disks, which you can compare with diff -r /sys/block/xvd{f,g}, is identical except for write stats and device name. And the disks don’t respond to smartctl. However, I have noticed ...


1

With a Basic volume/partition on a Basic disk the free space has to be adjacent to the volume/partition you want to extend. You'll need to either delete X: in order to extend C:, or you'll need to use a tool like GParted>


1

If you don't have a hardware RAID controller and are using software RAID, sure... It makes sense to check the S.M.A.R.T. status and monitor the RAID status of your array in that situation.


1

Try using the master password to secure-erase the disk. Performing a secure erase will reset the user password. You can find lists of default master passwords by vendor through google searches. For example, this web site may be useful: https://ipv5.wordpress.com/2008/04/14/list-of-hard-disk-ata-master-passwords/


1

It seems that the two first disk are 3.5' HDD, while the second two are 2.5' SFF HDD. So, the point is if your server supports 2.5' small form factor HDD.



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