On 09/10/2016 03:28 PM, Tony Baldwin wrote:
On 09/10/2016 03:07 PM, Nicolas George wrote:Le quintidi 25 fructidor, an CCXXIV, Anthony Baldwin a écrit :I apologize, but, I've never quite figured out what to do with dmesg, or what to look for in its output, etc.. it really just confuses me... I saw this: 15.690807] EXT3-fs (sda1): warning: checktime reached, running e2fsck is recommended [ 15.722318] EXT3-fs (sda1): using internal journalLooking for places that talk about the device causing problems would be a good start. Your problems are on /dev/sdb, so why do you bother with lines about /dev/sda?and tried to e2fsk /dev/sdb2And yet again you did not read part of my previous mail, the one about using Linux's fsck on microsoft's filesystems.
I have no knowlege of what a windows equivalent to fsck would be. I hardly use that system.I only even installed it, because for a brief while I was doing some work for the State (I work freelance from home) that required windows only software (my contacts with the state didn't even know what gnu/linux is), and it had to be run on bare metal, not in a virtual environment.
Thankfully, I am no longer doing that work. That system is so slow, stupid and crippled that it's maddening!
I have no time to waste writing mails that will not be read. Good luck. Regards,from dmesg | grep sdb 3.472220] sdb: sdb1 sdb2 sdb3 [ 3.472955] sd 5:0:0:0: [sdb] Attached SCSI disk [ 118.344330] EXT4-fs (sdb1): recovery complete [ 118.344542] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
-- http://www.baldwinlinguas.com translations, localization, multilingual web development EN, ES, FR, PT