I am running 10.1 on a T60p and have an external USB hard drive. After a suspend/resume the original device assigned to the usb disk (/dev/sdb) goes bad and the USB device is given another device name (/dev/sdc). This causes all sorts of problems for mounted filesytems. I see the following in the message log. Here's where it starts to go bad during the resume: Jun 7 08:13:28 koetsu kernel: Restarting tasks...<6>usb 5-1: USB disconnect, address 16 Jun 7 08:13:28 koetsu kernel: sd 6:0:0:0: rejecting I/O to device being removed Jun 7 08:13:28 koetsu kernel: xfs_force_shutdown(sdb3,0x1) called from line 338 of file fs/xfs /xfs_rw.c. Return address = 0xf9a61a27 Jun 7 08:13:28 koetsu kernel: Filesystem "sdb3": I/O Error Detected. Shutting down filesystem : sdb3 Jun 7 08:13:28 koetsu kernel: Please umount the filesystem, and rectify the problem(s) Jun 7 08:13:28 koetsu kernel: xfs_force_shutdown(sdb3,0x1) called from line 338 of file fs/xfs /xfs_rw.c. Return address = 0xf9a61a27 Then a whole slew of: Jun 7 08:13:29 koetsu kernel: 6:0:0:0: rejecting I/O to dead device Jun 7 08:13:29 koetsu kernel: Buffer I/O error on device sdb2, logical block 519 Jun 7 08:13:29 koetsu kernel: lost page write due to I/O error on sdb2 Jun 7 08:13:29 koetsu kernel: 6:0:0:0: rejecting I/O to dead device Jun 7 08:13:29 koetsu kernel: Buffer I/O error on device sdb2, logical block 519 Jun 7 08:13:29 koetsu kernel: lost page write due to I/O error on sdb2 Until: Jun 7 08:13:31 koetsu kernel: 6:0:0:0: rejecting I/O to dead device Jun 7 08:13:31 koetsu kernel: 6:0:0:0: rejecting I/O to dead device Jun 7 08:13:31 koetsu kernel: 6:0:0:0: rejecting I/O to dead device Jun 7 08:13:31 koetsu kernel: EXT3-fs error (device loop2): ext3_find_entry: reading directory #2 offset 0 Jun 7 08:13:31 koetsu kernel: Aborting journal on device loop2. Jun 7 08:13:31 koetsu kernel: 6:0:0:0: rejecting I/O to dead device Jun 7 08:13:31 koetsu kernel: EXT3-fs error (device loop2): ext3_find_entry: reading directory #2 offset 0 Jun 7 08:13:34 koetsu kernel: Vendor: HTS54806 Model: 0M9AT00 Rev: MGBO Jun 7 08:13:34 koetsu kernel: Type: Direct-Access ANSI SCSI revision: 00 Jun 7 08:13:34 koetsu kernel: SCSI device sdc: 117210240 512-byte hdwr sectors (60012 MB) Jun 7 08:13:34 koetsu kernel: sdc: Write Protect is off Jun 7 08:13:34 koetsu kernel: sdc: Mode Sense: 00 14 00 00 Jun 7 08:13:34 koetsu kernel: sdc: assuming drive cache: write through Jun 7 08:13:34 koetsu kernel: SCSI device sdc: 117210240 512-byte hdwr sectors (60012 MB) Jun 7 08:13:34 koetsu kernel: sdc: Write Protect is off Jun 7 08:13:34 koetsu kernel: sdc: Mode Sense: 00 14 00 00 Jun 7 08:13:34 koetsu kernel: sdc: assuming drive cache: write through Jun 7 08:13:34 koetsu kernel: sdc: sdc1 sdc2 sdc3 Jun 7 08:13:34 koetsu kernel: sd 7:0:0:0: Attached scsi disk sdc Jun 7 08:13:34 koetsu kernel: sd 7:0:0:0: Attached scsi generic sg1 type 0 Jun 7 08:13:34 koetsu kernel: usb-storage: device scan complete Now I have access to the disk as /dev/sdc but the kernel mount table is messed up and I have to manually clean everything up and remount the filesystems. It isn't really possible to stop all work on the device, unmount the filesystems, and remove the USB device before suspend. So how do get it to re-use the original device? Cosmo -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com