Subject: mount problems

From: Tony Baldwin <[email-masked]>
Date: Sat, 10 Sep 2016 13:45:28 -0400

Suddenly I can't mount my 2nd hdd, it's been fine, but after a reboot 
today, I get  I/O  errors trying to mount the two partitions on it with 
this script:
#!/bin/bash

if [ $(whoami) != "root" ]; then
	echo "must be root, bitch"
	exit
else
	mount /media/win7
	mount /media/winhome
	echo "mounted, sir."
fi
ls /media/winhome/
ls /media/win7/
exit

Which worked flawlessly not long ago,
although, I have to say recently I've been able to simply mount these 
partitions in pcmanfm
Definitely something weird going on:
[501][tony.deathstar: media]$ ls -la
ls: cannot access winhome: Input/output error
ls: cannot access myown: Permission denied
ls: cannot access win7: Input/output error
total 16
drwxr-xr-x  7 root root 4096 Sep  5 13:55 .
drwxr-xr-x 24 root root 4096 Jul  9  2015 ..
drwxr-xr-x  2 root root 4096 Oct 13  2012 cardreader
d?????????  ? ?    ?       ?            ? myown
drwx------  3 tony root 4096 Sep 10 13:04 tony
d?????????  ? ?    ?       ?            ? win7
d?????????  ? ?    ?       ?            ? winhome
[502][tony.deathstar: media]$ su

How can I remove these corrupted inodes and redo my mounting stuff?
I do recall there is a way to make it so I can delete them, when I had 
troubles with bad inodes on a server due to improper use of logrotate 
allowing my server to become overloaded with empty logs that were bad 
inodes, but I do not recall what that method is.

Thanks,
Tony
-- 
http://tonybaldwin.me
all tony, all the time

---

From: Nicolas George <[email-masked]>
Date: Sat, 10 Sep 2016 19:53:00 +0200

> ls: cannot access win7: Input/output error

If you are lucky, fsck (or the windows equivalent) will fix this.

If you are less lucky, you need to prepare for a trip to the hard drive
dealer.

The output of dmesg will tell you more.

Regards,

-- 
  Nicolas George

---

From: Tony Baldwin <[email-masked]>
Date: Sat, 10 Sep 2016 14:21:58 -0400

> The output of dmesg will tell you more.
perhaps some of this will be useful?
# fdisk -l

Disk /dev/sda: 1.4 TiB, 1500301910016 bytes, 2930277168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x0009ff62

Device     Boot      Start        End    Sectors  Size Id Type
/dev/sda1             2048   58593279   58591232   28G 83 Linux
/dev/sda2         58595326 2930276351 2871681026  1.3T  5 Extended
/dev/sda5       2867777536 2930276351   62498816 29.8G 82 Linux swap / 
Solaris
/dev/sda6         58595328 2867777535 2809182208  1.3T 83 Linux

Partition 3 does not start on physical sector boundary.

Partition table entries are not in disk order.
Disk /dev/sdb: 1.4 TiB, 1500301910016 bytes, 2930277168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0007b3d9

Device     Boot     Start        End    Sectors    Size Id Type
/dev/sdb1            2048    4098047    4096000      2G 83 Linux
/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 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 do have these partitions listed in /etc/fstab:
# new lines, should be auto rw for me tony
#UUID=6B3B505F1763BB9B  /media/winhome  ntfs-3g 
exec,rw,permissions,auto,user,uid=1000,gid=1000 0 0
#UUID=BAE47010E46FCCE7B /media/win7     ntfs-3g 
exec,rw,permissions,auto,user,uid=1000,gid=1000 0 0

-- 
http://tonybaldwin.me
all tony, all the time

---

From: Nicolas George <[email-masked]>
Date: Sat, 10 Sep 2016 20:26:18 +0200

> perhaps some of this will be useful?

It is a little. But much less than the source of information I mentioned in
my first mail and that you utterly ignored.

> 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.

> mount points I'd be back in business.

I very much believe you are completely wrong on that.

---

From: Anthony Baldwin <[email-masked]>
Date: Sat, 10 Sep 2016 14:36:55 -0400

> 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

-- 
http://www.baldwinlinguas.com
translations, localization,
multilingual web development
EN, ES, FR, PT

---

From: Nicolas George <[email-masked]>
Date: Sat, 10 Sep 2016 21:07:29 +0200

Le quintidi 25 fructidor, an CCXXIV, Anthony Baldwin a écrit :
> I saw this: 15.690807] EXT3-fs (sda1): warning: checktime reached, running
> e2fsck is recommended

Looking 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/sdb2

And 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 time to waste writing mails that will not be read. Good luck.

Regards,

-- 
  Nicolas George

---

From: Tony Baldwin <[email-masked]>
Date: Sat, 10 Sep 2016 15:28:17 -0400

> I have no time to waste writing mails that will not be read. Good luck.

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://tonybaldwin.me
all tony, all the time

---

From: Anthony Baldwin <[email-masked]>
Date: Sat, 10 Sep 2016 15:34:17 -0400

>> 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!

---

From: Anthony Baldwin <[email-masked]>
Date: Sat, 10 Sep 2016 19:57:10 -0400

> That system is so slow, stupid and crippled that it's maddening!
I let windows do it's auto-repair thingy, and when I booted back to 
Debian, things looked like maybe they were back to normal. I was able to do:
$ ls -li
total 12
1349304 drwxr-xr-x 2 root root 4096 Sep  5 13:55 myown
1357617 drwxr-xr-x 2 root root 4096 Jul 10  2015 win7
1357619 drwxr-xr-x 2 root root 4096 Jul 10  2015 winhome

Then I tried do mount them again, and got the I/O error,
and they're back to doing this:
$ ls -li
ls: cannot access winhome: Input/output error
ls: cannot access win7: Input/output error
total 4
1349304 drwxr-xr-x 2 root root 4096 Sep  5 13:55 myown
       ? d????????? ? ?    ?       ?            ? win7
       ? d????????? ? ?    ?       ?            ? winhome

I don't get it...

./Tony

---

From: Anthony Baldwin <[email-masked]>
Date: Sun, 11 Sep 2016 06:37:26 -0400

>       ? d????????? ? ?    ?       ?            ? winhome
This can't have anything to do with "the microsoft version of fsck",
because the windows disk (which is actually split into two partitions,
one with the win7 system, and one that's just storage) is running fine
when I boot it (for a crippled OS, anyway), and mounting the storage 
partition fine, too.
PLus, I'm having trouble sshfs mounting a remote server running Debian,
which worked fine days ago, now when I try it I get the same I/O errors, 
and wierd inode issues I'm getting with this local hdd.

---

From: Anthony Baldwin <[email-masked]>
Date: Sun, 11 Sep 2016 08:12:24 -0400

> and wierd inode issues I'm getting with this local hdd.

To confirm.
I booted back to windows and did a chkdsk (I'm assuming this is the 
nearest thing to a Windows approximation of fsck) for both C:// (the 
win7 system and /dev/sdb2) and D:// (storage, /dev/sdb3), and still 
cannot mount either partition on this drive when I come back to my 
Debian system.
The disk itself is fine, the problem is with the debian system somewhere.
Oh, and I have been able to sshfs mount my remote server again, btw

]$ dmesg | grep sdb
[    3.098300] sd 5:0:0:0: [sdb] 2930277168 512-byte logical blocks: 
(1.50 TB/1.36 TiB)
[    3.098341] sd 5:0:0:0: [sdb] Write Protect is off
[    3.098343] sd 5:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    3.098360] sd 5:0:0:0: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
[    3.132979]  sdb: sdb1 sdb2 sdb3
[    3.133999] sd 5:0:0:0: [sdb] Attached SCSI disk

---

From: Eike Lantzsch <[email-masked]>
Date: Sun, 11 Sep 2016 08:59:45 -0400

> [    3.133999] sd 5:0:0:0: [sdb] Attached SCSI disk

sorry should have read:
df -h *and* df -hi

---

From: Tony Baldwin <[email-masked]>
Date: Sun, 11 Sep 2016 11:43:17 -0400

>> [    3.133999] sd 5:0:0:0: [sdb] Attached SCSI disk

neither seems to indicate any problem:
]$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1        28G   16G   11G  61% /
udev             10M     0   10M   0% /dev
tmpfs           3.2G  9.4M  3.2G   1% /run
tmpfs           7.9G   23M  7.9G   1% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           7.9G     0  7.9G   0% /sys/fs/cgroup
/dev/sda6       1.3T  589G  663G  48% /home
tmpfs           1.6G  8.0K  1.6G   1% /run/user/1000
[504][tony.deathstar: /home/tony]$ df -hi
Filesystem     Inodes IUsed IFree IUse% Mounted on
/dev/sda1        1.8M  514K  1.3M   29% /
udev             2.0M   453  2.0M    1% /dev
tmpfs            2.0M   776  2.0M    1% /run
tmpfs            2.0M    33  2.0M    1% /dev/shm
tmpfs            2.0M     5  2.0M    1% /run/lock
tmpfs            2.0M    11  2.0M    1% /sys/fs/cgroup
/dev/sda6         84M  1.2M   83M    2% /home
tmpfs            2.0M    15  2.0M    1% /run/user/1000
I was able to load a Trisquel mini liveCD up and mount that hdd from 
that system, and recover some of the most important stuff by rsyncing it 
back to the hdd my Jessie is on.
Still, I'd like to understand and amend the problem and be able to mount 
this disk like I used to on the Jessie system.
Since both Windows and Trisquel can mount and access is, the problem 
must be somewhere here in Jessie...
But I have work (with a deadline tomorrow) and am running out of both, 
patience and time for this problem today... will come back to it tomorrow

Thanks,
Tony

-- 
http://tonybaldwin.me
all tony, all the time

---

From: Eike Lantzsch <[email-masked]>
Date: Sun, 11 Sep 2016 14:37:05 -0400

On Sonntag, 11. September 2016 11:43:17 PYT Tony Baldwin wrote:
> >>>>>>> And yet again you did not read part of my previous mail, the one
> >>>>>>> about
> >>>>>>> using
> >>>> Debian, things looked like maybe they were back to normal. I was able
> >>>> to
> >>>> do:
> >>>> $ ls -li
> >>>> total 12

Again:
fsck /dev/sda1
fsck /dev/sda6
and keep track of the output
if there are too many errors then you might be better off with
fsck -y /dev/sda1
fsck -y /dev/sda6

if you still run into the same problem -> reinstall your system, it is broken
before you do that test your system drive (sda) with testdisk

-- 
Eike Lantzsch ZP6CGE

---

From: Eike Lantzsch <[email-masked]>
Date: Sun, 11 Sep 2016 08:54:40 -0400

> [    3.133999] sd 5:0:0:0: [sdb] Attached SCSI disk

The problem seems to be your system and not the mounted disks with NTFS or any 
remote shares.
shot into the dark:
might be that your root partition is full or ran out of inodes?
df -hi

also start your system using a live cd, e.g. knoppix
 [boot with "knoppix 2" to use only command line] and "fsck /dev/sdxn" where x 
is the letter of the hard disk where your system resides and n is the number 
of the pertinent partition(s).

is your /usr, /var and /tmp on the same partition than your root?

hope that helps to analize the problem further

Cheers
Eike

-- 
Eike Lantzsch ZP6CGE

---

From: Anthony Baldwin <[email-masked]>
Date: Sun, 11 Sep 2016 09:17:41 -0400

> The problem seems to be your system and not the mounted disks with NTFS or any
That's what I'd been trying to say.

> of the pertinent partition(s).

I had gparted try to check/repair that disk (not mounted anyway, so why 
not?), which failed.
I have posted the output here:
http://tonybaldwin.me/files/gparted_details.htm
> is your /usr, /var and /tmp on the same partition than your root?
Yes, my Debian system is all on one disk and one partition, even /home.

---

From: Eike Lantzsch <[email-masked]>
Date: Sun, 11 Sep 2016 10:18:38 -0400

On Sonntag, 11. September 2016 09:17:41 PYT Anthony Baldwin wrote:
> > The problem seems to be your system and not the mounted disks with NTFS or
> > any remote shares.
> 
> >  [boot with "knoppix 2" to use only command line] and "fsck /dev/sdxn"
> >  where x> 
> > is the letter of the hard disk where your system resides and n is the
> > number of the pertinent partition(s).
> 
That is on /dev/sda[n] if I understand correctly?
Do start a Debian Life CD or Knoppix and fsck /dev/sda[n]
> > hope that helps to analize the problem further

Let me ask again to understand the whole picture better:
On which disk does your Debian system reside? On /dev/sda[n] with filesystem of 
ext4 or on /dev/sdb2 with filesystem NTFS?
Do you have a swap partition? On which disk?

Why is /dev/sdb2 NTFS? Do you use it on both Debian and another computer with 
MS-Windows or do you have Win7 installed on the same box as Debian and if so, 
do you dual boot with grub or with the MS-Windows bootloader?

gparted does not seem to be the right tool to solve this problem. Why would 
you resize a partition that gives you problems on a system that is most 
probably the source of the problem?
Again: look from the outside and boot a Life CD...
You may e.g. use Knoppix 7.4.x. That way you need only to download the CD-
image and save yourself the trouble to download a whole DVD-image.

-- 
Eike Lantzsch ZP6CGE

---

From: Anthony Baldwin <[email-masked]>
Date: Sat, 10 Sep 2016 13:47:05 -0400

> inodes, but I do not recall what that method is.

Can't get the inode nos.
# ls -li
ls: cannot access winhome: Input/output error
ls: cannot access win7: Input/output error
total 12
1349045 drwxr-xr-x 2 root root 4096 Oct 13  2012 cardreader
       1 drwxrwxrwx 1 tony tony 4096 Aug  7 13:34 myown
1357674 drwx------ 3 tony root 4096 Sep 10 13:04 tony
       ? d????????? ? ?    ?       ?            ? win7
       ? d????????? ? ?    ?       ?            ? winhome