It could be that ntfs-3g has been damaged. That can be checked with
the command
rpm -V ntfs-3g
which should return nothing. If it does return something, re-install
ntfs-3g.
Another possibility is that the disk has been corrupted. To check
that possibility, first verify that you have the smartmontools rpm
installed (do `rpm -q smartmontools`) and then do a short offline test of
sdh, the drive which has the NTFS filesystem:
smartctl -t short /dev/sdh
After the test has been given enough time to complete, do
smartctl -a /dev/sdh
The output should end with the result of the short offline test, and
before that result the output should list recent errors detected. The
status of the test should be "Completed without error" and there should be
no errors detected. Even better, but much more time consuming, is
smartctl -t long /dev/sdh
For more information on smartctl, do 'man smartctl'.
If the disk drive is ok, and the NTFS filesystem contains some
uncorrupted version of a Windows operating system, you might be able to
boot your computer into it. In your case, when you installed SL6 perhaps
you also retained the ability to boot into Windows, and there are already
the appropriate lines in /etc/grub.conf. If they aren't already in
grub.conf, adding to its end the following lines may allow you to boot
into whatever operating system is in /dev/sdh1:
title Testing Booting into my NTFS filesystem
rootnoverify (hd7,0)
chainloader +1
The "7" in hd7 is there because 7+1=8 and the "h" of /dev/sdh1 is the 8th
letter of the alphabet. The "0" in hd7,0 is there because 0+1=1, as in
sdh1. After /etc/grub.conf has the required entries for booting into
/dev/sda1, reboot and select from your grub choices the operating system
corresponding to the NTFS filesystem. If booting into /dev/sdh1 fails,
either my instructions are wrong, the NTFS filesystem wasn't one into
which one may boot, or the filesystem was corrupted. If it works, then
the filesystem is probably ok, though if you know enough about the
operating system into which you've booted, you could try one of its disk
checking or repair programs.
Steven Yellin
On Thu, 15 Dec 2011, ting xu wrote:
> Ghis, here is what I got:
>
> #umount /dev/sdh1
> umount: /dev/sdh1: not mounted
> # umount -a
> umount: /home: device is busy.
> (In some cases useful info about processes that use the device
> is found by lsof(8) or fuser(1))
> umount: /dev/shm: device is busy.
> (In some cases useful info about processes that use the device
> is found by lsof(8) or fuser(1))
> umount: /: device is busy.
> (In some cases useful info about processes that use the device
> is found by lsof(8) or fuser(1))
> #mount -a
> #make /mnt/backup
> #fdisk -l
> [Here I omitted some information about Disk /dev/mapper/xxxx, etc. ]
>
> Disk /dev/sdh: 2000.4 GB, 2000398933504 bytes
> 1heads, 63 sectors/track, 62016335 cylinders
> Units = cylinders of 63 * 512 = 32256 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0xa4b57300
>
> Device Boot Start End
> Blocks Id System
> /dev/sdh1 2 62016256 1953512032+
> 7 HPFS/NTFS
>
> #mount -t ntfs-3g /dev/sdh1 /mnt/backup
> #ls /mnt/backup
>
> nothing appears...
>
> If I use "ntfs-3g /dev/sdh1 /mnt/backup", still echo "Segmentation fault".
>
> Linda
>
>
>
> On Thu, Dec 15, 2011 at 9:16 PM, Ghislain Vaillant <
> [log in to unmask]> wrote:
>
>> **
>> Hmmm let's do it one more time (could you please give the output you get
>> from each command if any):
>>
>> 1) unmount the sdh drive (in case of)
>> # umount /dev/sdh1
>>
>> Maybe you could rather unmount everything by:
>> # umount -a
>> Later you can remount everything using:
>> # mount -a
>>
>> 2) create a new mount directory
>> # mkdir /mnt/mymountdir
>>
>> 3) list the drives
>> # fdisl -l
>>
>> I get this:
>> Device Boot Start End Blocks Id System
>> /dev/sdb1 1 121601 976760001 7 HPFS/NTFS
>>
>> 4) mount your ntfs drive to the directory
>> # mount -t ntfs-3g /dev/sdb1 /mnt/mymountdir
>>
>> 5) list files
>> # ls /mnt/mymountdir
>>
>> Ghis
>>
>>
>>
>> On 15/12/11 12:45, ting xu wrote:
>>
>> No, nothing appears.
>>
>>
>> On Thu, Dec 15, 2011 at 8:42 PM, Ghislain Vaillant <
>> [log in to unmask]> wrote:
>>
>>> So nothing appears if you "ls /mnt/mounted_disk" ?
>>>
>>>
>>> On 15/12/11 11:59, ting xu wrote:
>>>
>>> Ghis,
>>>
>>> Thank you for your reply. I tried, nothing echo, but when I check with
>>> "df -Th", the disk has not been mounted:(
>>> Do you have any other suggestion?
>>>
>>> Best!
>>>
>>> Linda
>>>
>>>
>>> On Thu, Dec 15, 2011 at 6:57 PM, Ghislain Vaillant <
>>> [log in to unmask]> wrote:
>>>
>>>> What about:
>>>>
>>>> mkdir /mnt/mounted_disk
>>>> mount -t ntfs-3g /dev/sdh /mnt/mounted_disk
>>>>
>>>> This is the basic mounting command for ntfs partitions, more infos on
>>>> mounting options here:
>>>> http://opensuse.swerdna.org/susentfs.html
>>>>
>>>> Ghis
>>>>
>>>>
>>>>
>>>> On 15/12/11 02:19, ting xu wrote:
>>>>
>>>>
>>>> Hi,
>>>>
>>>> I want to mount a NTFS hard disk. I have installed the ntfs-3g, but
>>>> there is a "Segmentation fault" information come out. I don't know how to
>>>> fix it. I am a freshman of Linux. Would anyone tell me how to mount this
>>>> NTFS hard disk? Much appreciate!
>>>> *
>>>> *
>>>> *#rpm -qa ntfs*
>>>> ntfs-3g-2011.4.12-5.el6.x86_64
>>>> #fdisk -l |grep NTFS*
>>>> *Disk /dev/sdc doesn't contain a valid partition table
>>>> Disk /dev/dm-1 doesn't contain a valid partition table
>>>> Disk /dev/dm-2 doesn't contain a valid partition table
>>>> Disk /dev/dm-3 doesn't contain a valid partition table
>>>> Disk /dev/dm-4 doesn't contain a valid partition table
>>>> Disk /dev/dm-5 doesn't contain a valid partition table
>>>> /dev/sdh1 1 60801 488384001 7 HPFS/NTFS
>>>> *
>>>> *#ntfs-3g /dev/sdh1 /mnt*
>>>> *Segmentation fault*
>>>>
>>>>
>>>> Linda
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>
|
