On 2017-12-03, at 1:41 PM, Carlos O'Donell wrote: > On Sun, Dec 3, 2017 at 10:37 AM, Carlos O'Donell > <car...@systemhalted.org> wrote: >> On Sun, Dec 3, 2017 at 10:31 AM, Carlos O'Donell >> <car...@systemhalted.org> wrote: >>> Lastly, do we have a new official package repo or is >>> backup.parisc-linux.org sid/* still the most recent? >> >> OK, found debian-ports, and started installing an dist-upgrade from >> there to unstable. > > > [ 1359.376000] sd 3:0:2:0: [sdb] Unhandled sense code > [ 1359.376000] sd 3:0:2:0: [sdb] > [ 1359.376000] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE > [ 1359.380000] sd 3:0:2:0: [sdb] > [ 1359.380000] Sense Key : Hardware Error [current] > [ 1359.388000] Info fld=0x32b1b00 > [ 1359.388000] sd 3:0:2:0: [sdb] > [ 1359.388000] Add. Sense: Mechanical positioning error > [ 1359.396000] sd 3:0:2:0: [sdb] CDB: > [ 1359.396000] Write(10): 2a 00 03 2b 1b 00 00 00 b0 00 > [ 1359.404000] end_request: critical target error, dev sdb, sector 53156608 > [ 1359.404000] EXT4-fs warning (device sdb4): ext4_end_bio:317: I/O > error -181 writing to inode 655989 (offset 0 size 90112 starting block > 6644598) > [ 1359.420000] Buffer I/O error on device sdb4, logical block 296800 > [ 1359.420000] Buffer I/O error on device sdb4, logical block 296801 > [ 1359.428000] Buffer I/O error on device sdb4, logical block 296802 > [ 1359.432000] Buffer I/O error on device sdb4, logical block 296803 > [ 1359.432000] Buffer I/O error on device sdb4, logical block 296804 > [ 1359.440000] Buffer I/O error on device sdb4, logical block 296805 > [ 1359.440000] Buffer I/O error on device sdb4, logical block 296806 > [ 1359.448000] Buffer I/O error on device sdb4, logical block 296807 > [ 1359.456000] Buffer I/O error on device sdb4, logical block 296808 > [ 1359.456000] Buffer I/O error on device sdb4, logical block 296809 > > Looks like sdb might fail too. > > [ 1468.808000] Add. Sense: Unrecovered read error - auto reallocate failed > [ 1468.816000] sd 3:0:2:0: [sdb] CDB: > [ 1468.816000] Read(10): 28 00 03 07 00 58 00 00 08 00 > [ 1468.824000] end_request: critical medium error, dev sdb, sector 50790489 > [ 1468.824000] EXT4-fs error (device sdb4): > ext4_wait_block_bitmap:494: comm http: Cannot read block bitmap - > block_group = 10, block_bitmap = 1035 > [ 1468.848000] Aborting journal on device sdb4-8. > [ 1468.856000] EXT4-fs (sdb4): Remounting filesystem read-only > > Does this mean the hardware is likely dying?
Yes. You might be able to recover it by running "dd if=/dev/sdb of=/dev/null conv=noerror" on it. This will work if the drive's bad block replacement is able to replace the bad blocks. Dave -- John David Anglin dave.ang...@bell.net