It resumed on its own. Weird. On Wed, Aug 12, 2015 at 4:23 PM, Timothy Normand Miller <theo...@gmail.com> wrote: > On Wed, Aug 12, 2015 at 2:10 PM, Chris Murphy <li...@colorremedies.com> wrote: > >> >> Anyway it looks like it's hardware related, but I don't know what >> device ata4.00 is, so maybe this helps: >> http://superuser.com/questions/617192/mapping-ata-device-number-to-logical-device-name > > # ata=4; ls -l /sys/block/sd* | grep $(grep $ata > /sys/class/scsi_host/host*/unique_id | awk -F'/' '{print $5}') > lrwxrwxrwx 1 root root 0 Aug 12 16:21 /sys/block/sde -> > ../devices/pci0000:00/0000:00:1f.5/ata4/host3/target3:0:0/3:0:0:0/block/sde > > sde is the newly attached drive, replacing the one that had appeared > to have bad sectors. So it looks like either this new motherboard has > a bad connector, or the cable is bad. I'm going to swap it out for a > different SATA cable. How do I resume the failed operation? And > should I reboot because of the OOPSes? > > -- > Timothy Normand Miller, PhD > Assistant Professor of Computer Science, Binghamton University > http://www.cs.binghamton.edu/~millerti/ > Open Graphics Project
-- Timothy Normand Miller, PhD Assistant Professor of Computer Science, Binghamton University http://www.cs.binghamton.edu/~millerti/ Open Graphics Project -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
