On 09/10/2016 02:26 PM, Nicolas George wrote:
Le quintidi 25 fructidor, an CCXXIV, Tony Baldwin a écrit :
The output of dmesg will tell you more.
perhaps some of this will be useful?
# fdisk -l
It is a little. But much less than the source of information I mentioned in
my first mail and that you utterly ignored.
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 journal
and tried to e2fsk /dev/sdb2 and 3, in both cases I got something like this:
ext2fs_check_if_mount: Input/output error while determining whether
/dev/sdb3 is mounted.
e2fsck: Device or resource busy while trying to open /dev/sdb3
Filesystem mounted or opened exclusively by another program?
AFAIK nothing is doing anything on those partitions since I haven't even
been able to mount them.
Thanks,
Tony
/dev/sdb2 * 4098048 824020991 819922944 391G 7 HPFS/NTFS/exFAT
/dev/sdb3 824020992 2930272255 2106251264 1004.3G 7 HPFS/NTFS/exFAT
And when I try to fsck (perhaps I'm doing it wrong?) nothing happens but
this:
# sudo fsck /dev/sdb2
fsck from util-linux 2.25.2
root@deathstar:/media# sudo fsck -y /dev/sdb2
fsck from util-linux 2.25.2
root@deathstar:/media# man fsck
root@deathstar:/media# man fsck
root@deathstar:/media# sudo fsck -y /dev/sdb3
fsck from util-linux 2.25.2
I very much doubt that Linux's fsck will be able to deal with microsoft's
filesystems efficiently.
I can't help but think if I could remove the bad inodes in /media at the
mount points I'd be back in business.
I very much believe you are completely wrong on that.
--
http://www.baldwinlinguas.com
translations, localization,
multilingual web development
EN, ES, FR, PT
