- fstab
Only obvious thing I can see wrong is that you're using
ntfs rather than
ntfs-3g. The latter is a user-space filesystem (which has been around for many years and is VERY stable) which can read and write NTFS reliably. The
ntfs filesystem driver is a kernel module in the Linux kernel that is much less mature and (AFAIK) does not provide write support, nor can it handle volumes that have a dirty journal (again, AFAIK).
When you have issues like this, the best way to debug it is to try and mount it manually. As root (or add
sudo in front of it):
If you get an error post it here. If not..... hmm.
The other problem that may exist is that the device may not be stable. Sometimes the BIOS boot order and plugging in / unplugging devices (SATA disks, USB disks, etc) can cause the block devices to have different names. One boot it may be
/dev/sda, the next boot it may be
/dev/sdd. You can get the
UUID of the specific partition and use that in
/etc/fstab instead of the
/dev/sda3 device node identifier. A fairly good write-up on how to determine UUIDs and use them in
fstab is at the Ubuntu wiki, but note that some commands they advise you to run may not work with Debian. Instead, just follow the instructions under "Finding UUIDs" and manually plug the UUID into
/etc/fstab by using the syntax
UUID=BlahBlahIAmAUUID instead of
 - Grub entry name
/boot/grub/grub.cfg is for
GRUB2. If the file exists, you can go ahead and edit it and replace the name appropriately. You can also see if a setting in
/etc/default/ directory lets you customize the default name.
If /boot/grub/grub.cfg doesn't exist, then /boot/grub/menu.lst should -- that's the GRUB Legacy menu file. It's reasonably similar to GRUB2's, in the sense that changing the boot order priority is just a matter of copying and pasting the various sections in the document into the desired order, or changing the
default command to reflect the zero-based index of the desired default boot menu item. And of course you can change the name to whatever you want.
If the package tools detect that you have modified a GRUB menu item, generally they won't overwrite your changes automatically, so you don't have to worry about that. But even in the event that your changes are overwritten by a package upgrade, the changes you want to make are only "cosmetic", so it's not a disaster...