You are not logged in.

#1 2016-11-05 18:54:31

LeftyAce
Member
Registered: 2012-08-18
Posts: 159

[SOLVED] Can't mount volume, but fsck says it's fine....

Hi all,

I'm having a heck of a time trying to google this problem because I get no error messages.

I have an external harddrive (USB) with two partitions: ntfs and ext4. The ext4 partition is for my backups. I ran a backup using rdiff-backup, and then asked it to list changed files. I cancelled that operation while it was running (maybe a mistake?), and the drive suddenly was no longer mounted.

Now when plug the drive into the computer, the NTFS partition automounts, but the EXT4 partition does not. If I try to mount it manually, the command returns no errors, but the drive is not mounted. Here is what I see in dmesg when I connect it:

# dmesg
[ 3714.468101] usb 4-1.2: new high-speed USB device number 5 using ehci-pci
[ 3714.567267] usb-storage 4-1.2:1.0: USB Mass Storage device detected
[ 3714.570859] scsi host6: usb-storage 4-1.2:1.0
[ 3715.592467] scsi 6:0:0:0: Direct-Access     WDC WD10 EZEX-00BN5A0          PQ: 0 ANSI: 5
[ 3715.593173] sd 6:0:0:0: Attached scsi generic sg1 type 0
[ 3715.593772] sd 6:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[ 3715.595997] sd 6:0:0:0: [sdc] Write Protect is off
[ 3715.596003] sd 6:0:0:0: [sdc] Mode Sense: 28 00 00 00
[ 3715.597007] sd 6:0:0:0: [sdc] No Caching mode page found
[ 3715.597015] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[ 3715.663218]  sdc: sdc1 sdc2
[ 3715.666895] sd 6:0:0:0: [sdc] Attached SCSI disk
[ 3716.072579] ntfs: volume version 3.1.
[ 3716.072587] ntfs: (device sdc2): load_system_files(): Volume is dirty.  Mounting read-only.  Run chkdsk and mount in Windows.
[ 3716.185710] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null)

After that happens, this is what lsblk says (sdc2 is the NTFS partition):

# lsblk
NAME            MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sdc               8:32   0 931.5G  0 disk  
├─sdc2            8:34   0  97.7G  0 part  /media/2F368CDB41444458
└─sdc1            8:33   0 833.9G  0 part  

Here is what happens when I try to mount /dev/sdc1:

# mount -v /mnt/backup
mount: /dev/sdc1 mounted on /mnt/backup.
# umount -v /mnt/backup
umount: /mnt/backup: not mounted

I ran fsck and it found no errors:

[root@laptop]# fsck -r /dev/sdc1
fsck from util-linux 2.28.2
e2fsck 1.43.3 (04-Sep-2016)
/dev/sdc1: clean, 883937/54648832 files, 106629781/218590464 blocks
/dev/sdc1: status 0, rss 3176, real 0.264626, user 0.239999, sys 0.003333

[root@laptop]# fsck -a /dev/sdc1
fsck from util-linux 2.28.2
/dev/sdc1: clean, 883937/54648832 files, 106629781/218590464 blocks

[root@laptop]# fsck -p /dev/sdc1
fsck from util-linux 2.28.2
/dev/sdc1: clean, 883937/54648832 files, 106629781/218590464 blocks

Any ideas where my partition went? Thanks in advance!

Last edited by LeftyAce (2016-11-12 20:32:21)

Offline

#2 2016-11-05 19:53:26

olive
Member
From: Belgium
Registered: 2008-06-22
Posts: 1,490

Re: [SOLVED] Can't mount volume, but fsck says it's fine....

Are you sure that /mnt/backup is not your mounted partition after "mount -v /mnt/backup"? What does mountpoint /mnt/backup gives? Are you sure there are datas on your partition?

Note that for automount to work, the entry should not be in fstab. If you unplug and replug the drive, be sure to check dmesg to see the device node of your disk. You can also do a "fsck -f /dev/sdc1" (be sure to not fsck a mounted filesystem).

Last edited by olive (2016-11-05 19:54:09)

Offline

#3 2016-11-05 19:56:52

mich41
Member
Registered: 2012-06-22
Posts: 796

Re: [SOLVED] Can't mount volume, but fsck says it's fine....

Is return code from the first run of mount zero? Does /proc/mounts indicate that the volume is mounted?

edit: similar case (?)

Last edited by mich41 (2016-11-05 20:00:30)

Offline

#4 2016-11-12 20:31:31

LeftyAce
Member
Registered: 2012-08-18
Posts: 159

Re: [SOLVED] Can't mount volume, but fsck says it's fine....

Thanks for the replies, and my apologies for the delay getting back to this. A reboot mysteriously fixed it (which means I can't try some of the diagnosis ideas you had).

I actually don't want that drive to automount. On my previous install I was able to avoid that by setting the "noauto" flag in /etc/fstab. That's why it's listed there. On my new install with udisks2 running I haven't had success setting certain drives not to be automounted. I'll start a separate thread once I get a chance to dig into that.

Offline

Board footer

Powered by FluxBB