Tag Info

Hot answers tagged

15

SCSI and ATA are entirely different standards. They are currently both developed under the aegis of the INCITS standards organization but by different groups. SCSI is under technical committee T10, while ATA is under T13.1 ATA was designed with hard disk drives in mind, only. SCSI is a broader standard, capable of controlling mass storage devices, tape ...


4

If you do not have backups, your data wasn't important. It's gone. There is no undo. Especially not with encryption involved. something that produces output > /dev/somedisk overwrites data on the device. Whatever is overwritten can not be restored, so your only chance would be if you noticed and cancelled it right away. Then probably only the first few ...


4

I don't know what you are trying to achieve so I can only describe what your command is actually doing. dd if=/dev/zero You are reading from a special device which returns an infinite number of zero (or NUL) bytes. of=/EMPTY You are creating a new file using the above (infinite) input. bs=1M You read and write the infinite data stream in megabyte ...


3

why it's vda Because it's a virtual disk. A cloud server can be run on a hypervisor. The role of a hypervisor is to control the capacity of operating systems so it is allocated where needed. With cloud hosting there are multiple cloud servers which are available to each particular client. This allows computing resource to be dedicated to a ...


2

Disable the drive cache and try re-formatting again. The system is getting ahead of the hardware.


2

Getting statistics about ongoing dd process You can use the kill command with the appropriate signal to make dd output statistics to standard error. From the GNU dd man page: Sending a USR1 signal to a running 'dd' process makes it print I/O statistics to standard error and then resume copying. $ dd if=/dev/zero of=/dev/null& pid=$! $ kill ...


2

It's not really possible. You simply can not prevent someone powering on/off a computer, or indeed them doing whatever they want with it once they have hands on access. I've done something similar, for a server. It uses full disk encryption and produces its key based on hardware data such as CPU type, Mac Address, amount of memory installed, etc. If someone ...


2

Use sudo. (But power off should not be prevented or people will pull the plug instead.) Some config files can be tightened to the point where they cannot be viewed; however others (critically DNS configuration) do not work if not world-readable. For each file you have to read the manual to find out. If full disk encryption + TPM-provided boot password ...


2

Can the disk (ATA) be setup so that a failing read doesn't take too long, so that it can be dropped, and the reading process and the disk wouldn't be blocked, and the next read could be attempted? No. My understanding of this is that it's a logical problem resulting from a design choice (not unique to linux) that favours performance and stability for ...


1

If you have the ftp user's home directory pointed to a mountpoint on the usb device, and the FTP client is set to write in the default directory, the hard drives will be not be utilized for the file storage. You may find that reads and writes are faster, but it's been my experience USB flash drives have life more limited than your hard drive. Personally, ...


1

Linux shows you device files for partitions when the disk has partitions. If the disk has partitions, there's no point in telling Linux not to show them to you: whatever problem you're having, this could only hide the problem, not solve it. If you change the partition table while the disk is connected, the kernel might not notice and might keep acting on ...


1

smartmon-tools may be useful in detection hard failures by the drive. However, the output is difficult to interpret. On the whole, I tend to agree with @Patrick that it there are more likely causes. But hard-drives do fail. If they are slowly degrading (instead of catastrophic failure like head crashes) the drive controller may use bad sector replacement ...


1

Hard drives usually don't have labels, it's filesystems that do. Here are the main places where a filesystem label is likely to come up: In /etc/fstab. In your bootloader configuration (e.g. /boot/grub/grub.cfg). If your Grub configuration is automatically generated, run update-grub after changing your labels and verify that the result is what you wanted. ...


1

As far as I know, labels aren't that much used in the unix world, so there isn't any danger in changing them. Keep using the UUIDs and you should be fine.


1

No way to recover, as simple as that. As a side note, doing dd is not a perfect way to backup files. For future cases, consider using tools like dar - you want some compression, incremental backup would also allow you to save huge amount of time and disk space in most cases.


1

dd was useful in the old days when people used tapes (when block sizes mattered) and when simpler tools such as cat might not be binary-safe. Nowadays, dd if=/dev/sdb of=/dev/sdc is a just complicated, error-prone, slow way of writing cat /dev/sdb >/dev/sdc. While dd still useful for some relatively rare tasks, it is a lot less useful than the number of ...


1

I have no idea about ZFS but if your intention is to zero out the file system then rather dd I will suggest shred I'm not answering about why dd is in infinite loop but your end-target is solved


1

The cause is hdparm, there is a bug in there that spins down the HDD in 3-5 sec when idle. This has been known in hdparm since 2012 and reported fixed. Now it causes the same problems in Debian Wheezy (for me it was Debian 7.6 and not before that initial upgrade to 7.6). Solution: check what level you power management is on (Advanced power management ...



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