I was trying to install ruby with :sudo apt-get install ruby1.8output:W: Not using locking for read only lock file /var/lib/dpkg/lockE: Unable to write to /var/cache/apt/E: The package lists or status file could not be parsed or opened.Output of sudo dpkg --configure -adpkg: unable to access dpkg status area: Read-only file system output of mount/dev/sda3 on / type ext4 (rw,errors=remount-ro)tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)proc on /proc type proc (rw,noexec,nosuid,nodev)sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)udev on /dev type tmpfs (rw,mode=0755)tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)/dev/sda1 on /boot type ext4 (rw)/dev/sdb1 on /home type ext4 (rw)mount: warning: /etc/mtab is not writable (e.g. read-only filesystem).       It's possible that information reported by mount(8) is not       up to date. For actual information about system mount points       check the /proc/mounts file.Output ofcat /proc/mountsrootfs / rootfs rw 0 0none /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0none /proc proc rw,nosuid,nodev,noexec,relatime 0 0none /dev devtmpfs rw,relatime,size=1553128k,nr_inodes=216450,mode=755 0 0none /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0/dev/disk/by-uuid/cf4fb4ae-6d12-407b-bf43-3b0daaaaaf74 / ext4 ro,relatime,errors=remount-ro,barrier=1,data=ordered 0 0tmpfs /lib/init/rw tmpfs rw,nosuid,relatime,mode=755 0 0tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0/dev/sda1 /boot ext4 rw,relatime,barrier=1,data=ordered 0 0/dev/sdb1 /home ext4 rw,relatime,barrier=1,data=ordered 0 0output of dmesg (some last part)[1968636.237601] JBD2: Detected IO errors while flushing file data on sdb1-8[1968772.229102] JBD2: Detected IO errors while flushing file data on sdb1-8[1968789.799409] IPv6 addrconf: prefix with wrong length 56[1968990.325125] IPv6 addrconf: prefix with wrong length 56[1969190.801848] IPv6 addrconf: prefix with wrong length 56[1969192.245363] JBD2: Detected IO errors while flushing file data on sdb1-8[1969197.698223] IPv6 addrconf: prefix with wrong length 56[1969223.105506] JBD2: Detected IO errors while flushing file data on sdb1-8[1969349.119764] JBD2: Detected IO errors while flushing file data on sdb1-8[1969398.205686] IPv6 addrconf: prefix with wrong length 56[1969598.713179] IPv6 addrconf: prefix with wrong length 56[1969607.241633] JBD2: Detected IO errors while flushing file data on sdb1-8[1969799.220758] IPv6 addrconf: prefix with wrong length 56[1969825.462909] JBD2: Detected IO errors while flushing file data on sdb1-8[1969831.231049] JBD2: Detected IO errors while flushing file data on sdb1-8[1969999.728348] IPv6 addrconf: prefix with wrong length 56[1970200.247944] IPv6 addrconf: prefix with wrong length 56[1970221.321558] JBD2: Detected IO errors while flushing file data on sdb1-8[1970253.105491] JBD2: Detected IO errors while flushing file data on sdb1-8. /var/log/syslog do not have updated logWhat should I do in order to have my file system read write without loosing all my data ?Is it appropriate to do sudo mount / -o remount,rw ? What other option do I have ?NOTE: System is debian vm running in ESXI server.
Not able to execute system files
filesystems;mount
Your virtual harddisk is broken. That happens a lot. Best to backup your files and ask an admin to restore an older, archived, version of it. You can try a sudo shutdown -rF nowto make your system reboot and force a filesystem check before mounting, but your dmesg output reads like a broken harddisk.