FAQ SearchLogin
Tuxera Home
View unanswered posts | View active topics It is currently Wed Nov 25, 2020 10:04



Post new topic Reply to topic  [ 5 posts ] 
Failed to access volume RPi 2 
Author Message

Joined: Wed Oct 28, 2015 15:06
Posts: 4
Post Failed to access volume RPi 2
I am having problems to mount a HDD in a Raspberry Pi 2 (Raspbian Wheezy).

At boot this failure msg :

Mounting local filesystems...ntfs-3g: Failed to access volume '/dev/sda1': No such file or directory

In console (terminal mode) sudo ntfs-3g /dev/sda1 /media/SAMSUNG ... works perfectly.

I have this fstab :

/dev/sda1 /media/SAMSUNG ntfs-3g defaults,noatime 0 0

Note: I some variants tested I changed /dev/sda1 for the UUID the result is the same "Failed to access ..."

Thanks in advance.

I have 2 reports :
Volume Information
Name of device: /dev/sda1
Device state: 11
Volume Name: SAMSUNG
Volume State: 27
Volume Version: 3.1
Sector Size: 512
Cluster Size: 4096
Index Block Size: 4096
Volume Size in Clusters: 488378008
MFT Information
MFT Record Size: 1024
MFT Zone Multiplier: 0
MFT Data Position: 24
MFT Zone Start: 786432
MFT Zone End: 61833683
MFT Zone Position: 786432
Current Position in First Data Zone: 61833683
Current Position in Second Data Zone: 0
LCN of Data Attribute for FILE_MFT: 786432
FILE_MFTMirr Size: 4
LCN of Data Attribute for File_MFTMirr: 244189004
Size of Attribute Definition Table: 2560
FILE_Bitmap Information
FILE_Bitmap MFT Record Number: 6
State of FILE_Bitmap Inode: 80
Length of Attribute List: 0
Attribute List: (null)
Number of Attached Extent Inodes: 0
FILE_Bitmap Data Attribute Information
Decompressed Runlist: not done yet
Base Inode: 6
Attribute Types: not done yet
Attribute Name Length: 0
Attribute State: 3
Attribute Allocated Size: 61050880
Attribute Data Size: 61047256
Attribute Initialized Size: 61047256
Attribute Compressed Size: 0
Compression Block Size: 0
Compression Block Size Bits: 0
Compression Block Clusters: 0

Dumping Inode 4 (0x4)
Upd. Seq. Array Off.: 48 (0x30)
Upd. Seq. Array Count: 3 (0x3)
Upd. Seq. Number: 92 (0x5c)
LogFile Seq. Number: 0x20013b7
MFT Record Seq. Numb.: 4 (0x4)
Number of Hard Links: 1 (0x1)
Attribute Offset: 56 (0x38)
MFT Record Flags: IN_USE
Bytes Used: 464 (0x1d0) bytes
Bytes Allocated: 1024 (0x400) bytes
Next Attribute Instance: 5 (0x5)
MFT Padding: 00 00
Dumping attribute $STANDARD_INFORMATION (0x10) from mft record 4 (0x4)
Attribute length: 72 (0x48)
Resident: Yes
Name length: 0 (0x0)
Name offset: 24 (0x18)
Attribute flags: 0x0000
Attribute instance: 0 (0x0)
Data size: 48 (0x30)
Data offset: 24 (0x18)
Resident flags: 0x00
ReservedR: 0 (0x0)
File Creation Time: Fri Oct 25 06:39:30 2013 UTC
File Altered Time: Fri Oct 25 06:39:30 2013 UTC
MFT Changed Time: Fri Oct 25 06:39:30 2013 UTC
Last Accessed Time: Fri Oct 25 06:39:30 2013 UTC
File attributes: HIDDEN SYSTEM (0x00000000)
Dumping attribute $FILE_NAME (0x30) from mft record 4 (0x4)
Attribute length: 112 (0x70)
Resident: Yes
Name length: 0 (0x0)
Name offset: 24 (0x18)
Attribute flags: 0x0000
Attribute instance: 2 (0x2)
Data size: 82 (0x52)
Data offset: 24 (0x18)
Resident flags: 0x01
ReservedR: 0 (0x0)
Parent directory: 5 (0x5)
File Creation Time: Fri Oct 25 06:39:30 2013 UTC
File Altered Time: Fri Oct 25 06:39:30 2013 UTC
MFT Changed Time: Fri Oct 25 06:39:30 2013 UTC
Last Accessed Time: Fri Oct 25 06:39:30 2013 UTC
Allocated Size: 36864 (0x9000)
Data Size: 36000 (0x8ca0)
Filename Length: 8 (0x8)
File attributes: HIDDEN SYSTEM (0x00000000)
Namespace: Win32 & DOS
Filename: '$AttrDef'
Dumping attribute $SECURITY_DESCRIPTOR (0x50) from mft record 4 (0x4)
Attribute length: 144 (0x90)
Resident: Yes
Name length: 0 (0x0)
Name offset: 24 (0x18)
Attribute flags: 0x0000
Attribute instance: 3 (0x3)
Data size: 116 (0x74)
Data offset: 24 (0x18)
Resident flags: 0x00
ReservedR: 0 (0x0)
Revision: 1
Control: 0x8004
Owner SID: S-1-5-21-1409082233-602609370-839522115-500
Group SID: S-1-5-32-544
System ACL: missing
Discretionary ACL:
Revision 2
ACE: type:allow flags:0x0 access:0x120089
SID: S-1-5-18
ACE: type:allow flags:0x0 access:0x120089
SID: S-1-5-32-544
Dumping attribute $DATA (0x80) from mft record 4 (0x4)
Attribute length: 72 (0x48)
Resident: No
Name length: 0 (0x0)
Name offset: 0 (0x0)
Attribute flags: 0x0000
Attribute instance: 4 (0x4)
Lowest VCN 0 (0x0)
Highest VCN: 0 (0x0)
Mapping pairs offset: 64 (0x40)
Compression unit: 0 (0x0)
Data size: 2560 (0xa00)
Allocated size: 4096 (0x1000)
Initialized size: 2560 (0xa00)
Runlist: VCN LCN Length
0x0 0xbfffe 0x1
End of inode reached
Total runs: 1 (fragments: 1)


Wed Oct 28, 2015 15:26
Profile
NTFS-3G Lead Developer

Joined: Tue Sep 04, 2007 17:22
Posts: 1286
Post Re: Failed to access volume RPi 2
Hi,

Quote:
Mounting local filesystems...ntfs-3g: Failed to access volume '/dev/sda1': No such file or directory

In console (terminal mode) sudo ntfs-3g /dev/sda1 /media/SAMSUNG ... works perfectly.

If you can mount from console, then ntfs-3g and its dependencies are correctly installed. Also the partition is in a valid state.

Systems using systemd start modules and drivers in parallel. Maybe /dev/sda1 is not yet created when mounting from fstab. Are there other partitions from /dev/sda mounted from fstab ?

You may (at least temporarily) insert the mount command in a startup script (usually in /etc/rc.d/rc.local).

Regards

Jean-Pierre


Wed Oct 28, 2015 22:39
Profile

Joined: Wed Oct 28, 2015 15:06
Posts: 4
Post Re: Failed to access volume RPi 2
jpa wrote:
Hi,

Quote:
Mounting local filesystems...ntfs-3g: Failed to access volume '/dev/sda1': No such file or directory

In console (terminal mode) sudo ntfs-3g /dev/sda1 /media/SAMSUNG ... works perfectly.

If you can mount from console, then ntfs-3g and its dependencies are correctly installed. Also the partition is in a valid state.

Systems using systemd start modules and drivers in parallel. Maybe /dev/sda1 is not yet created when mounting from fstab. Are there other partitions from /dev/sda mounted from fstab ?

You may (at least temporarily) insert the mount command in a startup script (usually in /etc/rc.d/rc.local).

Regards

Jean-Pierre

Hi Jean Pierre

I am new in Linux not Linux especific, in Raspbian (Wheezy)

This is my fstab

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>

proc /proc proc defaults 0 0
/dev/mmcblk0p2 / ext4 defaults,noatime 0 1
/dev/mmcblk0p1 /boot vfat defaults 0 2
/dev/sda1 /media/SAMSUNG ntfs-3g defaults,noatime 0 0

So that my only partition in this HDD is sda1.
I have the boot report. If you saw it Could help to identify if the problem is sda1 not created at ntfs-3g run?

Thanks for your help


Wed Oct 28, 2015 22:53
Profile

Joined: Wed Oct 28, 2015 15:06
Posts: 4
Post Re: Failed to access volume RPi 2
The problem seems to be SO ... and the solution change to Jessie version. I will test and then comment.


Thu Oct 29, 2015 03:05
Profile

Joined: Wed Oct 28, 2015 15:06
Posts: 4
Post Re: Failed to access volume RPi 2
Wheezy mount in parallel so fstab reach ntfs-3g line before device were available ... solution a rootdelay=5 in this file /boot/cmdline.txt


Fri Oct 30, 2015 00:45
Profile
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 5 posts ] 


Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Original forum style by Vjacheslav Trushkin.