That bug has been opened on https://launchpad.net/distros/ubuntu/+source/gnome-system-tools/+bug/47730

"Running disks-admin from the Desktop CD causes file systems to be mounted (no other options, such as read-only) are passed. For journalled filesystems, this means that the filesystem is being modified...

 6760 ? S 0:00 gksu disks-admin
 6761 ? Ss 0:00 \_ disks-admin
 6767 pts/0 Ss+ 0:00 \_ perl /usr/share/setup-tool-backends/scripts/disks-conf --report
 6780 pts/0 Z+ 0:00 \_ [sh] <defunct>
 6816 pts/0 S+ 0:00 \_ sh -c LC_ALL=C PATH=$PATH:/sbin:/usr/sbin /bin/mount /dev/sda5 /tmp/disks-conf-sda5 2>&1
 6817 pts/0 D+ 0:00 \_ /bin/mount /dev/sda5 /tmp/disks-conf-sda5

I only noticed this because the 'disks-admin' GUI has frozen, because of the mount, which in turn is failing because of:

[4295698.924000] ata1: command 0xc8 timeout, stat 0xd0 host_stat 0x21
[4295698.924000] ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
[4295698.924000] ata1: status=0xd0 { Busy }
[4295698.924000] sd 0:0:0:0: SCSI error: return code = 0x8000002
[4295698.924000] sda: Current: sense key: Aborted Command
[4295698.924000] Additional sense: Scsi parity error
[4295698.924000] Info fld=0x40
[4295698.924000] end_request: I/O error, dev sda, sector 23069407
[4295698.924000] Buffer I/O error on device sda5, logical block 2"