New answers tagged

0

The verification is made on every read, because the firmware reads the sector and its CRC/ECC and if it does not fit to the sector it will try to re-read (repair) it. The Wikipedia article Error detection and correction contains only one sentence: Modern hard drives use CRC codes to detect and Reed–Solomon codes to correct minor errors in sector reads, and ...


1

Put another way: Those signals of failure that can be responsibly dealt with pre-replacement are already dealt with by the firmware inside the drive; specifically designed and optimized for that disk design. Over time that became the division of responsibilities, anything run on the CPU nowadays pretty much only needs a binary good/no good status, anything ...


3

If a hard disk starts to show bad sectors in its SMART data, the only responsible action in business environment is to replace the hard disk.


-1

There's also the Intel Open CAS.


0

Thank you for your time. In step 2 I used resizepart but I got this: Error: The backup GPT table is not at the end of the disk, as it should be. This might mean that another operating system believes the disk is smaller. Fix, by moving the backup to the end (and removing the old backup)? Fix/Ignore/Cancel? Should I Fix it? This is the complete output ~ #...


2

Step 1: Try rescanning the storage devices to tell the kernel that the size has changed. I am not sure if this has to be done for all the four components of the multipath, but it shouldn't hurt. You rescan storage devices by writing anything into their rescan file: echo > /sys/class/block/sdl/device/rescan echo > /sys/class/block/sdm/device/rescan echo ...


2

HDD size in actual "physical" terms of platter/heads is stored in a internal ROM but it is not user-accessible. Modern HDDs (and SSDs) expose an abstraction called LBA (logical block addressing), which basically tell the OS how many user-addressable sectors the disk has. dd simply reads until EOF (end-of-file), which can either be the end of disk ...


0

If lsblk command is working fine in your system then you can use the below command to get UUID of the disk [root@ansible-tower ~]# lsblk -f


2

Don't use dd as a tool for measuring performance. The command line arguments given to dd in your example allow the host OS to cache the writes in RAM. So the results here are likely skewed by the amount of RAM available for caching in the host OS vs the guest OS. fio is a much more relevant tool for benchmarking.


-1

The only thing that really stands out with your configuration is using the old virtio-blk driver, which is getting little maintenance for the past several years. Consider using virtio-scsi instead.


1

I'd recommend DBAN (https://dban.org/). It's free. You can load it to a flash drive and boot from that (https://www.lifewire.com/how-to-erase-a-hard-drive-using-dban-2619148), or burn it to a cd if your BIOS are too old. It has a few different options from a quick erase to a 35 pass overwrite. After that I'd recommend something like what Greg said, ...


0

Caused by NFS server (long-term reported bug) in container/VPS (not matter if is in container or VPS). When you mount NFS to physical host from container or VPS on the same physical host and your server get some stress, NFS server can hang (and this will be extended to other processes). In this case it was caused by memory "stress". The server had ...


-1

I can't add a comment to messages that mention the dd command, but as the man page say don't use the bs parameter with obs and / or ibs. bs will override them.


6

Just do not try to manually disable (^) the feature, then. You already are trying to create a volume exceeding what is possible without it. Adding ability for the file system to be larger than 16TiB (at 4k blocks) is the one and so far (almost) only point of the option. I suspect you are confusing the 64 bit option for something else. From man 5 ext4: 64bit ...


0

If there is no specific reason to have the drive NTFS formated (and i honestly can't think of one) you should use a native Linux filesystem like ext4 or btrfs if /dev/sdb is only used for the uploaded files you can just mount /dev/sdb to "/var/www/uploads", then build the absolute Path like this: $uploadDir = $_SERVER['DOCUMENT_ROOT'] . "/...


Top 50 recent answers are included