Hello, I'm having ext3 error messages in my f7 system. The message is: Jun 10 09:48:16 localhost kernel: EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 8355310 I'm only seeing it after connection of an external hd drive box. This box is connected to the pc via usb and internally has an IDE disk. It is a black cyclone MDT-SI3572. See <a href="http://www.midte.com/en_productinfo.asp?BigSortID=54&SmallSortID=90&ProductID=149">http://www.midte.com/en_productinfo.asp?BigSortID=54&SmallSortID=90&ProductID=149 </a> It seems it has the JM20337 Chipset... When I perform I/O operations on external box I get this error and I suspect that the ide disk on it has some problems too... /dev/sda3 is the / filesystem of the internal sata2 drive of my pc /dev/sdf is how the external hdd-box is seen by the system. What is the meaning of the ext3 error? Is fsck reccomended to be run? Some further information below: When I connect the usb cable and power on the box I get: Jun 10 08:30:29 localhost kernel: usb 7-5: new high speed USB device using ehci_hcd and address 2 Jun 10 08:30:29 localhost kernel: usb 7-5: configuration #1 chosen from 1 choice Jun 10 08:30:29 localhost kernel: scsi5 : SCSI emulation for USB Mass Storage devices Jun 10 08:30:34 localhost kernel: scsi 5:0:0:0: Direct-Access SAMSUNG J1AW931372 0-07 PQ: 0 ANSI: 2 CCS Jun 10 08:30:34 localhost kernel: SCSI device sdf: 66055248 512-byte hdwr sectors (33820 MB) Jun 10 08:30:34 localhost kernel: sdf: Write Protect is off Jun 10 08:30:34 localhost kernel: sdf: assuming drive cache: write through Jun 10 08:30:34 localhost kernel: SCSI device sdf: 66055248 512-byte hdwr sectors (33820 MB) Jun 10 08:30:34 localhost kernel: sdf: Write Protect is off Jun 10 08:30:34 localhost kernel: sdf: assuming drive cache: write through Jun 10 08:30:34 localhost kernel: sdf: sdf1 sdf2 Jun 10 08:30:34 localhost kernel: sd 5:0:0:0: Attached scsi disk sdf Jun 10 08:30:34 localhost kernel: sd 5:0:0:0: Attached scsi generic sg6 type 0 Jun 10 08:30:35 localhost hald: mounted /dev/sdf1 on behalf of uid 500 Jun 10 08:30:35 localhost kernel: kjournald starting. Commit interval 5 seconds Jun 10 08:30:35 localhost kernel: EXT3 FS on sdf2, internal journal Jun 10 08:30:35 localhost kernel: EXT3-fs: mounted filesystem with ordered data mode. Jun 10 08:30:35 localhost hald: mounted /dev/sdf2 on behalf of uid 500 I get some sense key errors on hdd-box I don't understand the meaning of... Jun 10 08:32:47 localhost kernel: sdf: Current: sense key: No Sense Jun 10 08:32:47 localhost kernel: Additional sense: No additional sense information Jun 10 08:32:47 localhost kernel: sdf: Current: sense key: No Sense Jun 10 08:32:47 localhost kernel: Additional sense: No additional sense information Jun 10 08:33:09 localhost kernel: sdf: Current: sense key: No Sense Jun 10 08:33:09 localhost kernel: Additional sense: No additional sense information Jun 10 08:33:09 localhost kernel: sdf: Current: sense key: No Sense Jun 10 08:33:09 localhost kernel: Additional sense: No additional sense information Jun 10 08:33:31 localhost kernel: sdf: Current: sense key: No Sense Jun 10 08:33:31 localhost kernel: Additional sense: No additional sense information Jun 10 08:33:31 localhost kernel: sdf: Current: sense key: No Sense Jun 10 08:33:31 localhost kernel: Additional sense: No additional sense information I can umount the two filesystems on sdf Jun 10 08:33:54 localhost hald: unmounted /dev/sdf2 from '/media/disk' on behalf of uid 500 Jun 10 08:34:00 localhost hald: unmounted /dev/sdf1 from '/media/NEW VOLUME' on behalf of uid 500 If I umount the file systems and then I power off the box I get: Jun 10 08:34:07 localhost kernel: usb 7-5: USB disconnect, address 2 BTW, is it ok to power off the box after the fs are umounted but the pc is still powered on? Or do I have to power off the pc and then the box? thanks for any suggestions. Gianluca