Re: [clug-talk] inodes, fsck and read-only file systems, Oh my!

2015-10-29 Thread Cody Swanson
Read only filesystems are generally the result of the drive timing out on write operations. Usually this means bad blocks on the disk. Smartctl -a /dev/sda or whatever your disk device is will show any errors the drive has logged. Additionally check /var/log/syslog or /var/log/messages (depend

Re: [clug-talk] inodes, fsck and read-only file systems, Oh my!

2015-10-27 Thread Gustin Johnson
What file system is this? Have you run fsck with the -c and -f flags? Can you boot this device with a cd or USB and then check the disk (systemrescuecd is my current favorite rescue distro)? Running "badblocks -svv" (those are two v's as in victor, the "w" will perform a destructive write test)

Re: [clug-talk] inodes, fsck and read-only file systems, Oh my!

2015-10-27 Thread Viorel Tabara
On 10/27/2015 05:29 PM, Noah Tellin wrote: > Lately, I am getting read-only file system issues and other problems > on boot up, when running Mint, [...] I don't seem to get those problems when > running Ubuntu. What filesystem and on what block device? It would help to post an 'lsblk' output from