thanks for replying
the contents of /var/log/fsck/checkfs are:
# cat /var/log/fsck/checkfs
Log of fsck -C -R -A -a
Mon Sep 29 10:13:49 2014
fsck from util-linux 2.20.1
fsck.fat 3.0.26 (2014-03-07)
/dev/sda1: 3 files, 33/124424 clusters
/dev/sda7: clean, 14070/29589504 files, 35292691/118326016 blocks
/dev/sda6: clean, 16/97536 files, 22572/390144 blocks
/dev/sda3 is mounted.
e2fsck: Cannot continue, aborting.
/dev/sda4: clean, 11320/183264 files, 260334/732416 blocks
fsck exited with status code 8
Mon Sep 29 10:13:50 2014
The Crunchbang user had an issue with the UUID of one of his partitions changing. My UUIDs seem unchanged, either that or I have been spending too much time on the computer
/dev/sda5: UUID="8cba2281-c6c4-4de7-8ecc-68cf95044da1" TYPE="swap"
/dev/sda1: UUID="0502-D895" TYPE="vfat"
/dev/sda2: UUID="90686687-d42c-46dc-82f6-b483229c8ea7" TYPE="ext4"
/dev/sda3: UUID="e648b45d-6300-4447-90d8-4bb69536a360" TYPE="ext4"
/dev/sda4: UUID="985e0647-bfbf-4043-bade-1f2c16f75970" TYPE="ext4"
/dev/sda6: UUID="07e69fdc-c9ee-49a2-8a8d-9cb463040db7" TYPE="ext4"
/dev/sda7: UUID="6d68a663-fd68-438b-9847-6181f16c0578" TYPE="ext4"
# cat /etc/fstab
# /etc/fstab: static file system information.
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda2 during installation
UUID=90686687-d42c-46dc-82f6-b483229c8ea7 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=0502-D895 /boot/efi vfat defaults 0 1
# /home was on /dev/sda7 during installation
UUID=6d68a663-fd68-438b-9847-6181f16c0578 /home ext4 defaults 0 2
# /tmp was on /dev/sda6 during installation
UUID=07e69fdc-c9ee-49a2-8a8d-9cb463040db7 /tmp ext4 defaults 0 2
# /usr was on /dev/sda3 during installation
UUID=e648b45d-6300-4447-90d8-4bb69536a360 /usr ext4 defaults 0 2
# /var was on /dev/sda4 during installation
UUID=985e0647-bfbf-4043-bade-1f2c16f75970 /var ext4 defaults 0 2
# swap was on /dev/sda5 during installation
UUID=8cba2281-c6c4-4de7-8ecc-68cf95044da1 none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
I am unable to install smartmontools:
# apt-get install smartmontools
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
0 upgraded, 1 newly installed, 0 to remove and 443 not upgraded.
Need to get 0 B/460 kB of archives.
After this operation, 1,650 kB of additional disk space will be used.
(Reading database ... 152903 files and directories currently installed.)
Preparing to unpack .../smartmontools_6.2+svn3841-1.2_amd64.deb ...
Unpacking smartmontools (6.2+svn3841-1.2) ...
dpkg: error processing archive /var/cache/apt/archives/smartmontools_6.2+svn3841-1.2_amd64.deb (--unpack):
unable to clean up mess surrounding `./usr/sbin/smartd' before installing another version: Read-only file system
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)
I think this means that /dev/sda3 i.e., the /usr partition is the one having problems, but running fsck on it from a LiveCD or in maintenance mode shows it as being "clean".
what can i do next?