February 20, 201511 yr I have my unraid server automatically sleeping when all the disks are idle. I quite often have a USB drive connected and mounted, but the mount is no longer functioning after resuming the system. The mount is still listed in the output of the mount command, but it can been seen from the device list that the USB drive is listed as a different device to the one originally mounted. To re-mount I have to umount and then mount again using the new device name. After a further sleep/resume, the same happens except its gone back to the original device name. e.g. /dev/sdh1 is mounted, after sleep/resume the device is /dev/sdi instead, and the original mount no longer works. If I umount /dev/sdh1 and mount /dev/sdi1, after a further sleep/resume, it goes back to /dev/sdh. Is there a way to stop this happening without umounting this drive before sleeping?
February 20, 201511 yr Community Expert You should never make assumptions about the /dev/sd? Type device name for a USB drive. You should instead use the drive Id or drive label when mounting such a device.
February 21, 201511 yr Author Fair enough, but it still won't solve the problem of losing the mount during sleep/resume will it?
February 21, 201511 yr Community Expert Fair enough, but it still won't solve the problem of losing the mount during sleep/resume will it? It should as the mount will follow the id/label instead of the /dev/sd? device name. This is a classic issue with USB drives where one cannot rely on the /dev/sd? name when mounting drives. The answer is to always mount with something that stays constant. However if after S3 sleep the USB sub-system is not coming back properly then that is a different issue. However your earlier post indicated that the drive was being seen - it was just that its /dev/sd? value changed so that the previous mount was invalid.
Archived
This topic is now archived and is closed to further replies.