Repository: dnschneid/crouton

Issue #288: Suspend/resume breaks chroot when running off external SDC card
Created: 2013-07-28T11:17:41Z
On my Chromebook Pixel it looks like a suspend/resume cycle leaves the chroot in an odd state.
04:14 alex@localhost/x86_64 [] >echo "before suspend"
before suspend
04:14 alex@localhost/x86_64 [] >echo "after suspend"
after suspend
-su: history: /home/alex/.bash_history: cannot create: Input/output error
11:15 alex@localhost/x86_64 [~] >
Looking at the dmesg it looks like there are ext4 errors on the SDC card which forces a re-mount breaking the chroot (or possibly the SDC is just unmounted as part of the suspend cycle).
ss     Generic  STORAGE DEVICE   0207 PQ: 0 ANSI: 0
[15015.434666] sd 12:0:0:0: [sdf] 125827072 512-byte logical blocks: (64.4 GB/59.9 GiB)
[15015.435935] sd 12:0:0:0: [sdf] Write Protect is off
[15015.435946] sd 12:0:0:0: [sdf] Mode Sense: 0b 00 00 08
[15015.437146] sd 12:0:0:0: [sdf] No Caching mode page present
[15015.437156] sd 12:0:0:0: [sdf] Assuming drive cache: write through
[15015.441164] sd 12:0:0:0: [sdf] No Caching mode page present
[15015.441174] sd 12:0:0:0: [sdf] Assuming drive cache: write through
[15015.448779]  sdf: sdf1
[15015.452132] sd 12:0:0:0: [sdf] No Caching mode page present
[15015.452142] sd 12:0:0:0: [sdf] Assuming drive cache: write through
[15015.452151] sd 12:0:0:0: [sdf] Attached SCSI removable disk
[15016.731447] EXT4-fs (sdf1): recovery complete
[15016.736860] EXT4-fs (sdf1): mounted filesystem with ordered data mode. Opts:
[15024.898066] wlan0: no IPv6 routers present
[15029.857907] EXT4-fs error (device sde1): ext4_find_entry:935: inode #3020490: comm bash: reading directory lblock 0
[15029.857941] EXT4-fs error (device sde1): ext4_read_inode_bitmap:171: comm bash: Cannot read inode bitmap - block_group = 368, inode_bitma
p = 12058640
[15029.857954] EXT4-fs error (device sde1) in ext4_new_inode:895: IO failure
[15029.857993] EXT4-fs error (device sde1): ext4_find_entry:935: inode #2884078: comm bash: reading directory lblock 0
[15029.858071] EXT4-fs error (device sde1): ext4_find_entry:935: inode #2883586: comm bash: reading directory lblock 0
[15029.858090] EXT4-fs error (device sde1): ext4_find_entry:935: inode #2883586: comm bash: reading directory lblock 0
[15035.044833] Aborting journal on device sde1-8.
[15035.044845] Buffer I/O error on device sde1, logical block 7372800
[15035.044851] lost page write due to I/O error on sde1
[15035.044857] JBD2: Error -5 detected when updating journal superblock for sde1-8.
[15092.013341] EXT4-fs error (device sde1): ext4_find_entry:935: inode #3020490: comm bash: reading directory lblock 0
[15092.013363] EXT4-fs error (device sde1): ext4_find_entry:935: inode #2884078: comm bash: reading directory lblock 0
[15092.013395] EXT4-fs error (device sde1): ext4_find_entry:935: inode #2883587: comm bash: reading directory lblock 0
[15092.013410] EXT4-fs error (device sde1): ext4_find_entry:935: inode #2884078: comm bash: reading directory lblock 0
[15092.014147] EXT4-fs error (device sde1): ext4_journal_start_sb:328: Detected aborted journal
[15092.014160] EXT4-fs (sde1): Remounting filesystem read-only
[15094.359077] EXT4-fs error (device sde1): ext4_find_entry:935: inode #3020490: comm bash: reading directory lblock 0

Duplicate issue #1480: SD Card doesn't mount after sleep/waking up under KDE
Created: 2015-03-06T15:39:54Z
Hi,
I've got a Problem with  mounting my SD Card.
FIrst: I've got a Toshiba Chromebook 2 and a SD Card which I formatted to ext4. I've set up KDE (trusty) via Crouton.
When I close the lid of the chromebook under Chrome OS and open it a little bit later again, the SD Card is mounted again.
But when I am working under KDE (I've also tried Unity before, it doesn't matter), and close the lid, the SD card can't become mounted after waking up the Chromebook again. In KDE I get an Error, when I try to mount it and in Chrome OS the SD card just disappeared. I can only mount the SD card again if if put it out (I don't do that anymore, I don't want to damage the card) or reboot the whole Chromebook. :(
Can you help me fixing this?
Regards
Melina

Closing comment (2015-03-06T18:46:00Z): this appears to be a dup of #288