Hi,

Using usb live bt5 for a while, keep getting the io errors on every shutdown. Don't know how to capture the errors while shutting down to paste it here. Anyway, the error messages are all related to bad io on filesystem. The bad file blocks got accumulated and causing various errors on next reboot. Had tried reinstall the usb, searching the webs, using different way to shutdown -P, poweroff...etc. The problem re occur.
My temporary solution is to do fsck -f on the casper-rw every so often to maintain it in a working state. Anyone else experience this?

root@bt:~# fsck -f '/media/PENDRIVE/casper-rw'
fsck from util-linux-ng 2.17.2
e2fsck 1.41.11 (14-Mar-2010)
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 15 has zero dtime. Fix<y>? yes

Deleted inode 16 has zero dtime. Fix<y>? yes

Deleted inode 17 has zero dtime. Fix<y>? yes

Deleted inode 806 has zero dtime. Fix<y>? yes

Deleted inode 807 has zero dtime. Fix<y>? yes

Deleted inode 808 has zero dtime. Fix<y>? yes

Deleted inode 809 has zero dtime. Fix<y>? yes

Deleted inode 810 has zero dtime. Fix<y>? yes

yyyyyPass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Inode 346121 ref count is 28, should be 29. Fix<y>? yes

Pass 5: Checking group summary information
Block bitmap differences: -(10240--10249) -14336 -(24569--24574) -(24582--24621) -(24628--24631) -(24633--24694) -(24702--24715) -32594 -(32602--32629) -(32631--32642) -32648 -(32652--32715) -(32720--32725) -32727
Fix<y>? yes

Free blocks count wrong for group #0 (151, counted=401).
Fix<y>? yes

Free blocks count wrong (248875, counted=249125).
Fix<y>? yes

Inode bitmap differences: -(15--17) -(806--810)
Fix<y>? yes

Free inodes count wrong for group #0 (30647, counted=30655).
Fix<y>? yes

Free inodes count wrong (429420, counted=429428).
Fix<y>? yes


casper-rw: ***** FILE SYSTEM WAS MODIFIED *****
casper-rw: 10956/440384 files (1.0% non-contiguous), 190939/440064 blocks
yroot@bt:~#


David