RPi Kernel Panic - minneskort ej läsligt
Min Raspberry Pi 3 kraschade igår kväll, jag vet inte riktigt vad som hände men den slutade iaf svara. För en stund sedan kopplade jag in den till TV:n och fick då se att den drabbats av Kernel Panic. Jag tog då ut kortet och satte det i en annan linux-maskin för att se om det gick att rädda det mha e2fsck. Den rasslade på en bra stund och reparerade/städade en hel del inodes men när e2fsck blivit klar syns inte längre minneskortet i lsblk och varken mount eller fdisk fungerar.
Är det bara att kasta minneskortet och köpa ett nytt eller finns det något man kan göra för att få liv i det? Jag skiter egentligen i datan, det var bara en labb-maskin men jag skulle gärna vilja få liv i den igen (helst utan att köpa nytt minneskort).
Så här ser syslog ut efter att jag dragit ut minneskortsläsaren och satt i den igen (/dev/sdj/ är minneskortet jag försöker få liv i):
May 25 13:30:57 Proliant kernel: [1528894.234313] usb 1-3: new high-speed USB device number 4 using ehci-pci
May 25 13:30:57 Proliant kernel: [1528894.371823] usb 1-3: New USB device found, idVendor=11b0, idProduct=6148
May 25 13:30:57 Proliant kernel: [1528894.371836] usb 1-3: New USB device strings: Mfr=3, Product=4, SerialNumber=5
May 25 13:30:57 Proliant kernel: [1528894.371844] usb 1-3: Product: FCR-HS219/1 Mobile Reader
May 25 13:30:57 Proliant kernel: [1528894.371851] usb 1-3: Manufacturer: Kingston
May 25 13:30:57 Proliant kernel: [1528894.371856] usb 1-3: SerialNumber: 000005147
May 25 13:30:57 Proliant kernel: [1528894.374117] usb-storage 1-3:1.0: USB Mass Storage device detected
May 25 13:30:57 Proliant kernel: [1528894.374601] scsi host8: usb-storage 1-3:1.0
May 25 13:30:57 Proliant mtp-probe: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:12.2/usb1/1-3"
May 25 13:30:57 Proliant mtp-probe: bus: 1, device: 4 was not an MTP device
May 25 13:30:58 Proliant kernel: [1528895.375860] scsi 8:0:0:0: Direct-Access Kingston FCR-HS219/1 9715 PQ: 0 ANSI: 0
May 25 13:30:58 Proliant kernel: [1528895.705953] scsi 8:0:0:1: Direct-Access Kingston FCR-HS219/1 9715 PQ: 0 ANSI: 0
May 25 13:30:58 Proliant kernel: [1528895.707190] scsi 8:0:0:2: Direct-Access Kingston FCR-HS219/1 9715 PQ: 0 ANSI: 0
May 25 13:30:58 Proliant kernel: [1528895.708439] scsi 8:0:0:3: Direct-Access Kingston FCR-HS219/1 9715 PQ: 0 ANSI: 0
May 25 13:30:58 Proliant kernel: [1528895.709041] sd 8:0:0:0: Attached scsi generic sg5 type 0
May 25 13:30:58 Proliant kernel: [1528895.709334] sd 8:0:0:1: Attached scsi generic sg6 type 0
May 25 13:30:58 Proliant kernel: [1528895.709887] sd 8:0:0:2: Attached scsi generic sg7 type 0
May 25 13:30:58 Proliant kernel: [1528895.710357] sd 8:0:0:3: Attached scsi generic sg8 type 0
May 25 13:30:58 Proliant kernel: [1528895.722130] sd 8:0:0:1: [sdh] Attached SCSI removable disk
May 25 13:30:58 Proliant kernel: [1528895.722755] sd 8:0:0:2: [sdi] Attached SCSI removable disk
May 25 13:30:58 Proliant kernel: [1528895.725010] sd 8:0:0:0: [sdf] Attached SCSI removable disk
May 25 13:30:58 Proliant kernel: [1528895.728925] sd 8:0:0:3: [sdj] 30318592 512-byte logical blocks: (15.5 GB/14.4 GiB)
May 25 13:30:58 Proliant kernel: [1528895.730868] sd 8:0:0:3: [sdj] Write Protect is off
May 25 13:30:58 Proliant kernel: [1528895.730876] sd 8:0:0:3: [sdj] Mode Sense: 03 00 00 00
May 25 13:30:58 Proliant kernel: [1528895.732879] sd 8:0:0:3: [sdj] No Caching mode page found
May 25 13:30:58 Proliant kernel: [1528895.732885] sd 8:0:0:3: [sdj] Assuming drive cache: write through
May 25 13:30:58 Proliant kernel: [1528895.748511] sdj: sdj1 sdj2
May 25 13:30:58 Proliant kernel: [1528895.756987] sd 8:0:0:3: [sdj] Attached SCSI removable disk
May 25 13:31:49 Proliant kernel: [1528945.905189] EXT4-fs (sdj2): warning: mounting unchecked fs, running e2fsck is recommended
May 25 13:31:51 Proliant kernel: [1528948.118442] scsi_io_completion: 118 callbacks suppressed
May 25 13:31:51 Proliant kernel: [1528948.118471] sd 8:0:0:3: [sdj] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 25 13:31:51 Proliant kernel: [1528948.118481] sd 8:0:0:3: [sdj] Sense Key : Not Ready [current]
May 25 13:31:51 Proliant kernel: [1528948.118495] sd 8:0:0:3: [sdj] Add. Sense: Medium not present
May 25 13:31:51 Proliant kernel: [1528948.118500] sd 8:0:0:3: [sdj] CDB:
May 25 13:31:51 Proliant kernel: [1528948.118505] Write(10): 2a 00 00 02 00 00 00 00 08 00
May 25 13:31:51 Proliant kernel: [1528948.118523] blk_update_request: 118 callbacks suppressed
May 25 13:31:51 Proliant kernel: [1528948.118529] blk_update_request: I/O error, dev sdj, sector 131072
May 25 13:31:51 Proliant kernel: [1528948.118539] buffer_io_error: 625 callbacks suppressed
May 25 13:31:51 Proliant kernel: [1528948.118546] Buffer I/O error on dev sdj2, logical block 0, lost sync page write
May 25 13:31:51 Proliant kernel: [1528948.119429] EXT4-fs (sdj2): mounted filesystem with ordered data mode. Opts: (null)
May 25 13:31:51 Proliant kernel: [1528948.123382] sd 8:0:0:3: [sdj] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 25 13:31:51 Proliant kernel: [1528948.123397] sd 8:0:0:3: [sdj] Sense Key : Not Ready [current]
May 25 13:31:51 Proliant kernel: [1528948.123406] sd 8:0:0:3: [sdj] Add. Sense: Medium not present
May 25 13:31:51 Proliant kernel: [1528948.123410] sd 8:0:0:3: [sdj] CDB:
May 25 13:31:51 Proliant kernel: [1528948.123415] Read(10): 28 00 00 03 04 f0 00 00 08 00
May 25 13:31:51 Proliant kernel: [1528948.123433] blk_update_request: I/O error, dev sdj, sector 197872
May 25 13:31:51 Proliant kernel: [1528948.123475] EXT4-fs error (device sdj2): ext4_find_entry:1289: inode #2: comm gvfsd-trash: reading directory lblock 0
May 25 13:31:51 Proliant kernel: [1528948.123483] EXT4-fs (sdj2): previous I/O error to superblock detected
May 25 13:31:51 Proliant kernel: [1528948.124846] sd 8:0:0:3: [sdj] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 25 13:31:51 Proliant kernel: [1528948.124855] sd 8:0:0:3: [sdj] Sense Key : Not Ready [current]
May 25 13:31:51 Proliant kernel: [1528948.124861] sd 8:0:0:3: [sdj] Add. Sense: Medium not present
May 25 13:31:51 Proliant kernel: [1528948.124863] sd 8:0:0:3: [sdj] CDB:
May 25 13:31:51 Proliant kernel: [1528948.124865] Write(10): 2a 00 00 02 00 00 00 00 08 00
May 25 13:31:51 Proliant kernel: [1528948.124875] blk_update_request: I/O error, dev sdj, sector 131072
May 25 13:31:51 Proliant kernel: [1528948.124880] Buffer I/O error on dev sdj2, logical block 0, lost sync page write
May 25 13:31:51 Proliant kernel: [1528948.126347] sd 8:0:0:3: [sdj] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 25 13:31:51 Proliant kernel: [1528948.126356] sd 8:0:0:3: [sdj] Sense Key : Not Ready [current]
May 25 13:31:51 Proliant kernel: [1528948.126361] sd 8:0:0:3: [sdj] Add. Sense: Medium not present
May 25 13:31:51 Proliant kernel: [1528948.126363] sd 8:0:0:3: [sdj] CDB:
May 25 13:31:51 Proliant kernel: [1528948.126366] Read(10): 28 00 00 03 04 f0 00 00 08 00
May 25 13:31:51 Proliant kernel: [1528948.126375] blk_update_request: I/O error, dev sdj, sector 197872
May 25 13:31:51 Proliant kernel: [1528948.126402] EXT4-fs error (device sdj2): ext4_find_entry:1289: inode #2: comm gvfsd-trash: reading directory lblock 0
May 25 13:31:51 Proliant kernel: [1528948.126406] EXT4-fs (sdj2): previous I/O error to superblock detected
May 25 13:31:51 Proliant kernel: [1528948.127838] sd 8:0:0:3: [sdj] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 25 13:31:51 Proliant kernel: [1528948.127846] sd 8:0:0:3: [sdj] Sense Key : Not Ready [current]
May 25 13:31:51 Proliant kernel: [1528948.127851] sd 8:0:0:3: [sdj] Add. Sense: Medium not present
May 25 13:31:51 Proliant kernel: [1528948.127854] sd 8:0:0:3: [sdj] CDB:
May 25 13:31:51 Proliant kernel: [1528948.127856] Write(10): 2a 00 00 02 00 00 00 00 08 00
May 25 13:31:51 Proliant kernel: [1528948.127865] blk_update_request: I/O error, dev sdj, sector 131072
May 25 13:31:51 Proliant kernel: [1528948.127871] Buffer I/O error on dev sdj2, logical block 0, lost sync page write
May 25 13:31:51 Proliant kernel: [1528948.138301] sd 8:0:0:3: [sdj] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 25 13:31:51 Proliant kernel: [1528948.138312] sd 8:0:0:3: [sdj] Sense Key : Not Ready [current]
May 25 13:31:51 Proliant kernel: [1528948.138318] sd 8:0:0:3: [sdj] Add. Sense: Medium not present
May 25 13:31:51 Proliant kernel: [1528948.138321] sd 8:0:0:3: [sdj] CDB:
May 25 13:31:51 Proliant kernel: [1528948.138325] Read(10): 28 00 00 03 04 f0 00 00 08 00
May 25 13:31:51 Proliant kernel: [1528948.138337] blk_update_request: I/O error, dev sdj, sector 197872
May 25 13:31:51 Proliant kernel: [1528948.138369] EXT4-fs error (device sdj2): ext4_find_entry:1289: inode #2: comm pool: reading directory lblock 0
May 25 13:31:51 Proliant kernel: [1528948.138374] EXT4-fs (sdj2): previous I/O error to superblock detected
May 25 13:31:51 Proliant kernel: [1528948.141463] sd 8:0:0:3: [sdj] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 25 13:31:51 Proliant kernel: [1528948.141473] sd 8:0:0:3: [sdj] Sense Key : Not Ready [current]
May 25 13:31:51 Proliant kernel: [1528948.141480] sd 8:0:0:3: [sdj] Add. Sense: Medium not present
May 25 13:31:51 Proliant kernel: [1528948.141483] sd 8:0:0:3: [sdj] CDB:
May 25 13:31:51 Proliant kernel: [1528948.141486] Write(10): 2a 00 00 02 00 00 00 00 08 00
May 25 13:31:51 Proliant kernel: [1528948.141497] blk_update_request: I/O error, dev sdj, sector 131072
May 25 13:31:51 Proliant kernel: [1528948.141503] Buffer I/O error on dev sdj2, logical block 0, lost sync page write
May 25 13:31:51 Proliant kernel: [1528948.141684] EXT4-fs error (device sdj2): ext4_find_entry:1289: inode #2: comm pool: reading directory lblock 0
May 25 13:31:51 Proliant kernel: [1528948.141689] EXT4-fs (sdj2): previous I/O error to superblock detected
May 25 13:31:51 Proliant kernel: [1528948.142093] EXT4-fs warning (device sdj2): __ext4_read_dirblock:884: error -5 reading directory block (ino 2, block 0)
May 25 13:31:51 Proliant kernel: [1528948.142210] EXT4-fs warning (device sdj2): __ext4_read_dirblock:884: error -5 reading directory block (ino 2, block 0)
May 25 13:31:51 Proliant kernel: [1528948.142253] EXT4-fs warning (device sdj2): __ext4_read_dirblock:884: error -5 reading directory block (ino 2, block 0)
May 25 13:31:51 Proliant kernel: [1528948.142292] EXT4-fs warning (device sdj2): __ext4_read_dirblock:884: error -5 reading directory block (ino 2, block 0)
May 25 13:31:51 Proliant kernel: [1528948.142329] EXT4-fs warning (device sdj2): __ext4_read_dirblock:884: error -5 reading directory block (ino 2, block 0)
May 25 13:31:51 Proliant kernel: [1528948.142365] EXT4-fs warning (device sdj2): __ext4_read_dirblock:884: error -5 reading directory block (ino 2, block 0)
May 25 13:31:51 Proliant kernel: [1528948.142401] EXT4-fs warning (device sdj2): __ext4_read_dirblock:884: error -5 reading directory block (ino 2, block 0)
May 25 13:31:51 Proliant kernel: [1528948.143054] EXT4-fs warning (device sdj2): __ext4_read_dirblock:884: error -5 reading directory block (ino 2, block 0)
May 25 13:31:51 Proliant kernel: [1528948.143098] EXT4-fs warning (device sdj2): __ext4_read_dirblock:884: error -5 reading directory block (ino 2, block 0)
May 25 13:31:51 Proliant kernel: [1528948.143134] EXT4-fs warning (device sdj2): __ext4_read_dirblock:884: error -5 reading directory block (ino 2, block 0)
May 25 13:32:00 Proliant kernel: [1528957.702176] EXT4-fs warning: 12 callbacks suppressed
May 25 13:32:00 Proliant kernel: [1528957.702191] EXT4-fs warning (device sdj2): __ext4_read_dirblock:884: error -5 reading directory block (ino 2, block 0)
May 25 13:32:32 Proliant kernel: [1528989.031140] EXT4-fs warning (device sdj2): __ext4_read_dirblock:884: error -5 reading directory block (ino 2, block 0)
May 25 13:32:32 Proliant kernel: [1528989.031698] EXT4-fs warning (device sdj2): __ext4_read_dirblock:884: error -5 reading directory block (ino 2, block 0)
May 25 13:32:33 Proliant kernel: [1528990.719260] EXT4-fs warning (device sdj2): __ext4_read_dirblock:884: error -5 reading directory block (ino 2, block 0)
May 25 13:32:33 Proliant kernel: [1528990.719743] EXT4-fs warning (device sdj2): __ext4_read_dirblock:884: error -5 reading directory block (ino 2, block 0)
May 25 13:35:01 Proliant CRON[28352]: (root) CMD (if [ -x /etc/munin/plugins/apt_all ]; then munin-run apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then munin-run apt update 7200 12 >/dev/null; fi)
May 25 13:36:52 Proliant kernel: [1529248.799315] EXT4-fs (sdj2): error count since last fsck: 33
May 25 13:36:52 Proliant kernel: [1529248.799343] EXT4-fs (sdj2): initial error at time 1464111862: htree_dirblock_to_tree:1000: inode 1731: block 8768
May 25 13:36:52 Proliant kernel: [1529248.799353] EXT4-fs (sdj2): last error at time 1464175911: ext4_find_entry:1289: inode 2
Finns det något att göra förutom att åka till Webhallen?
Det finns bara två sorters hårddiskar: de som har gått sönder och de som skall gå sönder.