[almightybob7]

Hello,

I have a dual-boot setup of Windows XP, and UbuntuStudio. I have them on separate partitions (obviously) of the same hard drive. I've always been able to read the ntfs partition (sda1, in this case), which is where I kept all of the music and other documents I had before switching to Linux. Things were working fine, and sda1 was able to be mounted without a problem, until now.

I attempted to install GFX Grub, using a tutorial found at UnixTutorials: http://www.unix-tutorials.com/go.php?id=3588 . The installation seems to have worked out fine, as I now have GFX Grub instead of the normal, nongraphical Grub bootloader, but now when I booted, I noticed that the shortcut to sda1 was not on the desktop anymore. I opened up a nautilus window, and instead of the normal sda1, it was shown as "68.4 GB Volume." I tried to open it, but got an error message. Here's what it said.

Cannot mount volume.
Unable to mount volume.

mount: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so

I tried to open up syslog, but I don't know what exactly it is that I'm looking for. I also tried using Gparted, and the disk is recognized as an ntfs partition, but it is still unable to be mounted. I really hope that this doesn't mean that I lost everything on the partition.

Anybody have any ideas what might be going on here? I greatly appreciate any advice or tips.

Thank You

[TRS-80 vet]

Originally Posted by almightybob7

Hello,

I have a dual-boot setup of Windows XP, and UbuntuStudio. I have them on separate partitions (obviously) of the same hard drive. I've always been able to read the ntfs partition (sda1, in this case), which is where I kept all of the music and other documents I had before switching to Linux. Things were working fine, and sda1 was able to be mounted without a problem, until now.

I attempted to install GFX Grub, using a tutorial found at UnixTutorials: http://www.unix-tutorials.com/go.php?id=3588 . The installation seems to have worked out fine, as I now have GFX Grub instead of the normal, nongraphical Grub bootloader, but now when I booted, I noticed that the shortcut to sda1 was not on the desktop anymore. I opened up a nautilus window, and instead of the normal sda1, it was shown as "68.4 GB Volume." I tried to open it, but got an error message. Here's what it said.


I tried to open up syslog, but I don't know what exactly it is that I'm looking for. I also tried using Gparted, and the disk is recognized as an ntfs partition, but it is still unable to be mounted. I really hope that this doesn't mean that I lost everything on the partition.

Anybody have any ideas what might be going on here? I greatly appreciate any advice or tips.

Thank You

Check your package manager to see if ntfs-3g is still properly installed. (I'm assuming that app is how you were accessing the ntfs partition before). I'm not familiar with studio version tho'.

If you can't mount the partition, the files are still there, I imagine. Before to much re-configuration, a backup would be in order however...

[almightybob7]

Thank you for your help, but I'm pretty sure I didn't have ntfs-3g before though, because I could just read the disks as soon as I installed Ubuntu. They were read-only though.

Thanks for that slice of hope though. I had really started to get worried about things.

[TRS-80 vet]

Originally Posted by almightybob7

Thank you for your help, but I'm pretty sure I didn't have ntfs-3g before though, because I could just read the disks as soon as I installed Ubuntu. They were read-only though.

Thanks for that slice of hope though. I had really started to get worried about things.

How were you able before to access the ntfs partition? Knowing that I think is necessary, since you now cannot access ntfs...

You have no icon for the ntfs partition at Places/computer/...

What does mtab and fstab return from CLI?

[almightybob7]

Umm, I don't know. There were just icons on my desktop that shortcutted to my NTFS drives, which I was able to read. I guess then, I must've had something like ntfs-3g, but I was unable to write to the disks.

I'll post up the mtab and fstab information in a bit.

[almightybob7]

Okay, here's my mtab info.

PHP Code:

/dev/sda6 / ext3 rw,errors=remount-ro 0 0
proc /proc proc rw,noexec,nosuid,nodev 0 0
/sys /sys sysfs rw,noexec,nosuid,nodev 0 0
varrun /var/run tmpfs rw,noexec,nosuid,nodev,mode=0755 0 0
varlock /var/lock tmpfs rw,noexec,nosuid,nodev,mode=1777 0 0
udev /dev tmpfs rw,mode=0755 0 0
devshm /dev/shm tmpfs rw 0 0
devpts /dev/pts devpts rw,gid=5,mode=620 0 0
lrm /lib/modules/2.6.22-14-generic/volatile tmpfs rw 0 0
securityfs /sys/kernel/security securityfs rw 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,noexec,nosuid,nodev 0 0
/dev/scd0 /media/cdrom0 udf ro,noexec,nosuid,nodev,user=nate 0 0 


Here's my fstab info.

PHP Code:

# /etc/fstab: static file system information.
#
#  -- This file has been automaticly generated by ntfs-config -- 
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>

proc /proc proc defaults 0 0
# Entry for /dev/sda6 :
UUID=6b40c913-42dd-420b-8ea3-6f474f28e430 / ext3 defaults,errors=remount-ro 0 1
# Entry for /dev/ !! UNKNOW DEVICE !! :
UUID=8480EC0F80EC098E /media/sda1 ntfs umask=222,utf8 0 1
# Entry for /dev/sdb1 :
UUID=D2F4036FF403555F /media/sdb1 ntfs umask=222,utf8 0 1
# Entry for /dev/sda5 :
UUID=6d135151-59ce-419b-b69c-c4fc10ae5267 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
/dev/sda1 /media/windows ntfs-3g umask=222,utf8 0 0
/dev/sdb1 /media/sdb1 ntfs-3g defaults,force 0 0 


I hope this helps.

[TRS-80 vet]

Punch in:

sudo apt-get install ntfs-3g

[almightybob7]

Originally Posted by TRS-80 vet

Punch in:

sudo apt-get install ntfs-3g

yeah, I tried that and it said that ntfs-3g is already at the newest version.

thanks though.

[TRS-80 vet]

Okay, let's identify the partition:

sudo fdisk -l (lower case L)

It was sda 1 before, when you had access. This will confirm the value to edit into fstab.