Hot answers tagged

18

There is a vendor independent SAT (SCSI/ATA transfer) standard, but AFAIK this is not widely supported on (cheaper) bridges. There are several vendor specific ATA pass-through commands that you can select with smartctl with the -d option: -d TYPE, --device=TYPE Specify device type to one of: ata, scsi, sat[,N][+TYPE], usbcypress[,X], ...


16

You can use rm to remove the folder on your external hard drive. The full Terminal command looks like this rm -r /Volumes/$drivename/$folder Replace $drivename with the name of your external hard drive. Replace $folder with the name of your folder. If you don't know the name of your external hard drive you can look it up with ls /Volumes


14

That's the problem with multi-user systems, especially if you have more than one of them. ;) There's no really nice way to do what you want. Approaches coming to mind would be having the same UID for your account on every machine you're using your external drive (actually not feasible, since most probably not all of the machines are under your control) ...


10

This is Debian Bug #631504 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631504). As is also mentioned there, the entry in fstab for /media/usb0 should not be there. It prevents Gnome from mounting the USB drive automatically and with the right permissions. This line (or lines, I had two of them, one for /media/usb0 and one for /media/usb1) should be ...


8

After cycling around /sys for a while, I found this solution: # echo /sys/class/enclosure/*/*/device/block/sdaa /sys/class/enclosure/2:0:35:0/Slot 15/device/block/sdaa # echo 1 > '/sys/class/enclosure/2:0:35:0/Slot 15/locate' Or: # echo 1 > /sys/class/enclosure/*/*/device/block/sdaa/../../enclosure*/locate To blink all detected devices: ...


8

fdisk -l can just list the filesystems it has the permission to read on. See my test with strace: user@host:~/test$ strace -e open /sbin/fdisk -l ... open("/proc/partitions", O_RDONLY) = 3 open("/dev/sda", O_RDONLY) = -1 EACCES (Permission denied) open("/dev/sda1", O_RDONLY) = -1 EACCES (Permission denied) open("/dev/sda2", ...


7

@chaos and @Braiam have provided good answers on why you aren't getting the behavior you are looking for from fdisk when running as a non-root user. The simple fact is that allowing regular users to read disks directly would allow bypassing file permissions by simply reading the disk data directly, which could be a major problem and certainly would make file ...


7

There's another similar question and bindfs is suggested there: mkdir /home/$user/sda1 bindfs -u $user -g $group /mnt/sda1 /home/$user/sda1 OSX users suggest noowners mount option described like this: Ignore the ownership field for the entire volume. This causes all objects to appear as owned by user ID 99 and group ID 99. User ID 99 is ...


7

SMART over USB is generally either not possible, or is done with (bridge) vendor-specific commands, so there's no one way to get things done. smartctl knows about a few specific bridge chips. Check the manpage for a list. This is horrible, but the only 100% reliable way to access SMART on a disk is to unplug it from the bridge and stick it on a proper host ...


6

It is 'safe' to remove an external drive when it is unmounted. The reason it might not be safe simply if programs aren't using it is that the Linux kernel does write caching. Meaning that when a program has written to disk, that data might not physically be on the disk, it could still be in memory (unless the program uses fsync or fdatasync). Linux does ...


5

What file system is on your external drive? Are you sure it supports concepts like owner, permissions and symbolic links? FAT32, for example, doesn't support these things, so you won't be able to use utilities like chmod, and Windows "shortcuts" are not the same as UNIX symlinks.


5

You need to comment out the DEVICESCAN line, and put in lines for individual devices. Mine, for example, looks like this: /dev/sda -d removable -n standby,8 -S on -o on -a \ -m root -M exec /usr/share/smartmontools/smartd-runner \ -r 194 -R 5 -R 183 -R 187 -s L/../../6/01 /dev/sdb -d removable -n standby,8 -S on -o on -a \ -m root ...


5

You can configure the power management with hdparm -B $value /dev/sdx Put that e.g. in /etc/init.d/boot.local Quoting the man page: A low value means aggressive power management and a high value means better performance. Possible settings range from values 1 through 127 (which permit spin-down), and values 128 through 254 (which do not permit ...


5

There isn't an appropriate value of -d. The problem is that you're using a SATA↔USB mass storage bridge, and USB mass storage doesn't have a standard way to request ATA/SATA SMART data. So instead the controller has either no way or some vendor-specific way to get the data. smartctl knows a few of these; examples include usbjmicron and usbsubplus. So, if ...


5

If your objective is to find out the device name of the external drive you just connected, the easiest ways is to run dmesg | tail -20 or so right after connecting it: $ dmesg | tail -20 [ 5610.869053] usb 2-1.4: New USB device strings: Mfr=10, Product=11, SerialNumber=5 [ 5610.869058] usb 2-1.4: Product: Iomega Select HDD [ 5610.869062] usb 2-1.4: ...


5

There is a special option in rsync: --remove-source-files This tells rsync to remove from the sending side the files (meaning non-directories) that are a part of the transfer and have been successfully duplicated on the receiving side. Note that you should only use this option on source files that ...


4

This is because super user or root has complete permissions to probe all devices while the users doesn't have such privileges by default. Whenever it tries it fails hence not listing the details. Some groups may have such privilege too which you can add yourself.


4

The owner and group of a file are stored as numbers. So the file will be owned by uid=1005, regardless of which user (or none at all) that is on the system its connected to. Changing the user/group to nobody won't fix your problem. Then only the nobody user (or members of the nobody group) would be allowed to access the files. Unfortunately, I don't think ...


4

You need to run shred on the device, not on the mount point. Type mount and get the device name (e.g. /dev/sdb1, likely it will be /dev/sdXY where X is a letter and Y is a number), then unmount it (run umount /your/device) and run shred /your/device.


4

USB drives have a chipset that converts USB mass-storage-device commands to IDE or SATA commands, which the drive then receives. Cheap chipsets (which are the majority, I imagine) don't pass on commands correctly to the drive that aren't directly related to reading or writing data from the drive. You are kind of at the mercy of that hardware with USB ...


4

You need to mount the drive first. mount /dev/sda1 /mnt then make your directory cd /mnt mkdir some-directory This may help but I haven't watched it. Side note: You may need to format the drive or partition it with something Linux can read and write. NTFS support in Linux is pretty mature, but for quite some time you could only mount it read only ...


4

Most probably the filesystem of your external hard drive does not manage or accept change of permissions. If the filesystem were ext3, ext4, UFS, ZFS or any kind of Unix filesystem you will not have any kind of problems but I guess you are mounting an NTFS or even FAT32 disk. You can check it out with the 'mount' command.


4

If you specify a block size (512 bytes) of less than the block size of the disk (often 4096 bytes, but nowadays maybe more), the block will be partially written, so that the contents of the rest of the block must be preserved before writing. This is because disk blocks cannot be written to with only 512 bytes, but you have to write a full block at once ...


3

Most likely it has to do with this commit: Open a directory with Anjuta where they changed: [File Loader] -SupportedMimeTypes=application/x-anjuta-old +SupportedMimeTypes=application/x-anjuta-old,inode/directory so when installing anjuta, update-desktop-database is run (during post-install); that updates /usr/share/applications/mimeinfo.cache and the ...


3

You can do it with find like so (to stay close to your original command) sudo find /mnt/sdb/ -type f -exec shred -v -n 1 {} + You should run it without -exec first so you can verify the list of files. However, if you've already removed files using regular rm, or overwritten files by editing or copying them, those files may still exist in the "free" space ...


3

It looks like you either made a backup with a different user, or that the permissions now assigned to the drive are different. First you should note the result of: mount | grep USB500 (and probably extend your question with that) After that can mount the drive read only by doing: sudo mount -o remount,ro /media/dave/USB500 and get a listing of what is ...


3

I think your next steps depend on how valuable the data on the drive is. If its fairly valuable, your next step should be to stop attempting recovery and instead contact a data recovery firm. Hopefully it's just the electronics on the PCB failing, in which case they ought to be able to do a full recovery relatively inexpensively. If you're not going to do ...


3

You could try an alternate approach, which is to recognize your device at the udev level and use /dev/mybook-partition in /etc/fstab. Put something like the following in /etc/udev/rules.d/dwilliams.rules: KERNEL=="sd*", PROGRAM=="/sbin/blkid %N", RESULT=="C252-9CA3", SYMLINK+="mybook-partition" The section on Auto mounting USB devices in the Arch wiki for ...


3

There are several possible causes and things that you might do. The dmesg excerpt suggests a few things: The kernel tries several times to access the device. It seems that each time it does not finish for some reason. There are notices saying not ready after error recovery which indicate that the drive either failed to undergo filesystem checks (although ...


3

It is quite unusual to format a filesystem on a hard disk without a partition table. It appears that you did in fact, have a partition table before, and the partition started at sector 2048, which is the usual starting location for the first partition on a disk these days. If you run fdisk and use the u command to change its units to sectors, then create a ...



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