Sabayon Community

by **Richlion** » Fri Apr 22, 2011 16:47

Hello,
I have my system on a 250GB drive and I have a separate Sata 500Gb hard drive that used to have a Windows Vista installation, but still is an NTFS file system. Since last night I cannot mount it, in Dolphin the error message is:

"An error occurred while accessing '465.8' Gib Hard Drive'. the system responded:
org.freedesktop.UDisks.error.Failed: Requested filesystem type is neither well-known nor in /proc/filesystems nor in /etc/filesystems"

When I run fsck.ntfs on the drive:

Code: Select all: Richlion1 tmp # pg 1.log Loading $MFT/Bitmap runlist failed. Trying $MFTMirr. Loading $MFTMirr/Bitmap runlist failed too. Aborting. Unsupported: replay_log() Unsupported: check_volume() Checking 230457 MFT records. Error getting bit value for record 0. Error getting bit value for record 1. Error getting bit value for record 2. Error getting bit value for record 3. Error getting bit value for record 4. Error getting bit value for record 5. Error getting bit value for record 6. Error getting bit value for record 7. Error getting bit value for record 8. Error getting bit value for record 9. Error getting bit value for record 10. Error getting bit value for record 11. Error getting bit value for record 12. Error getting bit value for record 13. Error getting bit value for record 14. Error getting bit value for record 15. Error getting bit value for record 16. Assertion failed for '16:FILE record magic'. should be 0x454c4946, was 0x0. Assertion failed for 'attrs_offset < bytes_in_use'. 0x0 >= 0x0 Error getting bit value for record 17. Assertion failed for '17:FILE record magic'. should be 0x454c4946, was 0x0. Assertion failed for 'attrs_offset < bytes_in_use'. 0x0 >= 0x0 Error getting bit value for record 18. Assertion failed for '18:FILE record magic'. should be 0x454c4946, was 0x0. Assertion failed for 'attrs_offset < bytes_in_use'. 0x0 >= 0x0 Error getting bit value for record 19. Assertion failed for '19:FILE record magic'. should be 0x454c4946, was 0x0. Assertion failed for 'attrs_offset < bytes_in_use'. 0x0 >= 0x0 Error getting bit value for record 20. Assertion failed for '20:FILE record magic'. should be 0x454c4946, was 0x0. Assertion failed for 'attrs_offset < bytes_in_use'. 0x0 >= 0x0 Error getting bit value for record 21. Assertion failed for '21:FILE record magic'. should be 0x454c4946, was 0x0. Assertion failed for 'attrs_offset < bytes_in_use'. 0x0 >= 0x0 Error getting bit value for record 22. Assertion failed for '22:FILE record magic'. should be 0x454c4946, was 0x0. Assertion failed for 'attrs_offset < bytes_in_use'. 0x0 >= 0x0 Error getting bit value for record 23. Assertion failed for '23:FILE record magic'. should be 0x454c4946, was 0x0. Assertion failed for 'attrs_offset < bytes_in_use'. 0x0 >= 0x0 Error getting bit value for record 24. Error getting bit value for record 25. Error getting bit value for record 26. Error getting bit value for record 27. ...... messages continue Error getting bit value for record 230456. Errors found. Unsupported cases found.

I thought my hard drive was dead, but I think it is still healthy:
fdisk -l shows:

Code: Select all: Richlion1 ~ # fdisk -l Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders, total 625142448 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 Disk identifier: 0xeca4b515 Device Boot Start End Blocks Id System /dev/sda1 * 2048 1026047 512000 83 Linux /dev/sda2 1026048 625141759 312057856 8e Linux LVM Disk /dev/sdb: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders, total 976773168 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 Disk identifier: 0x783b93e4 Device Boot Start End Blocks Id System /dev/sdb1 * 2048 976771071 488384512 7 HPFS/NTFS Disk /dev/dm-0: 53.7 GB, 53687091200 bytes 255 heads, 63 sectors/track, 6527 cylinders, total 104857600 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 Disk identifier: 0x00000000 Disk /dev/dm-0 doesn't contain a valid partition table Disk /dev/dm-1: 259.5 GB, 259543531520 bytes 255 heads, 63 sectors/track, 31554 cylinders, total 506920960 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 Disk identifier: 0x00000000 Disk /dev/dm-1 doesn't contain a valid partition table Disk /dev/dm-2: 6308 MB, 6308233216 bytes 255 heads, 63 sectors/track, 766 cylinders, total 12320768 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 Disk identifier: 0x00000000 Disk /dev/dm-2 doesn't contain a valid partition table

I found a hint I could somehow mount/force the drive are read-only:
http://www.linuxquestions.org/questions ... ux-729250/
but I don't know how, can anyone help?

Do I still need to plug this drive into a Windows box and run chkdsk?

Thanks for helping.
Richard

PS . Wish Everyone a Happy Easter :wink:

by **joost** » Fri Apr 22, 2011 16:59

I've bumped into this too.
At first I wasn't sure it was only me who had this.
I'll go see if I can find a solution.

by **Sisko43** » Fri Apr 22, 2011 17:04

Me too. No ntfs access with the same error messages in general since last update.

by **Fitzcarraldo** » Fri Apr 22, 2011 17:10

Would this be the fix?: https://bugs.kde.org/show_bug.cgi?id=270689#c2

by **joost** » Fri Apr 22, 2011 17:12

Some quick facts:

- Checked disk in Windows 7: No problems found
- Mounting it in Gnome: No problem

So this has to be an issue in KDE.

Indeed like the bug above states, edit /etc/filesystems and add ntfs-3g to it.

by **Sisko43** » Fri Apr 22, 2011 17:15

I think it's "udisks". Made a downgrade via portage from version 1.0.2-r1 to 1.0.2. Everything works again..

by **joost** » Fri Apr 22, 2011 17:16

Code: Select all: joost@xbox-360 ~ $ qfile -e /etc/filesystems sys-apps/baselayout-2.0.1 (/etc/filesystems)

Let me investigate that further, perhaps we simply need an updated version.

by **Richlion** » Fri Apr 22, 2011 17:18

Ah, I managed to mount it:

# cd /media
# mkdir dd
# chmod 777 dd
# ntfsmount /dev/sdb1 /media/dd

ALso found a nice PDF instruction:
http://www.linux-magazine.com/w3/issue/74/ntfsprogr.pdf

by **joost** » Fri Apr 22, 2011 17:20

Richlion and Sisko43

edit /etc/filesystems and add ntfs-3g to it

by **Richlion** » Fri Apr 22, 2011 17:24

joost wrote:Richlion and Sisko43

edit /etc/filesystems and add ntfs-3g to it

Thanks, but can you give an example? My /etc/filesystems is empty right now.
Is it something like in /etc/fstab?

/dev/<NTFS-part> /mnt/windows ntfs-3g gid=users,umask=0022 0 0

Sabayon Community

Hard drive recovery on NTFS, help needed [Solved]

Hard drive recovery on NTFS, help needed [Solved]

Re: Hard drive recovery on NTFS, help needed

Re: Hard drive recovery on NTFS, help needed

Re: Hard drive recovery on NTFS, help needed

Re: Hard drive recovery on NTFS, help needed

Re: Hard drive recovery on NTFS, help needed

Re: Hard drive recovery on NTFS, help needed

Re: Hard drive recovery on NTFS, help needed

Re: Hard drive recovery on NTFS, help needed

Re: Hard drive recovery on NTFS, help needed

Who is online