/etc/fstab and mounting USB drives
The latest rebuildfstab in my grml installed on hd has these entries:
LABEL=MX320G /mnt/MX320G ntfs noauto,user,dev,suid,exec,ro,umask=000,uid=tom,gid=tom 0 0 # /dev/sda1
/dev/usb-sda1 /mnt/usb-sda1 auto user,noauto,nodev,noatime,nosuid,noexec,rw,uid=tom,gid=tom 0 0
Those are the same drive.
mount /mnt/MX320G
doesn't work; it complains about no LABEL=MX320G device.
mount /mnt/usb-sda1
does work, but I don't like the "rw" on my ntfs file system.
Here's another pair from /etc/fstab that mount a vfat fs:
LABEL=MX200G /mnt/MX200G vfat noauto,user,dev,suid,exec,umask=000,uid=tom,gid=tom 0 0 # /dev/sdb1
/dev/usb-sdb1 /mnt/usb-sdb1 auto user,noauto,nodev,noatime,nosuid,noexec,rw,uid=tom,gid=tom 0 0
Both
mount /mnt/MX200G
and
mount /mnt/usb-sdb1
work.
-- Tom White
* Tom White tom@bulldogcountry.com [20061103 14:53]:
The latest rebuildfstab in my grml installed on hd has these entries:
LABEL=MX320G /mnt/MX320G ntfs noauto,user,dev,suid,exec,ro,umask=000,uid=tom,gid=tom 0 0 # /dev/sda1
/dev/usb-sda1 /mnt/usb-sda1 auto user,noauto,nodev,noatime,nosuid,noexec,rw,uid=tom,gid=tom 0 0
Those are the same drive.
mount /mnt/MX320G
doesn't work; it complains about no LABEL=MX320G device.
Please show output of:
# vol_id /dev/usb-sda1
when your device is available as /dev/usb-sda1. (Seems to be a problem with ntfs.)
mount /mnt/usb-sda1
does work, but I don't like the "rw" on my ntfs file system.
Basically I wanted to avoid another fstype-check in rebuildfstab. "auto" works pretty well, everything the kernel is aware of works OOTB. The rw becomes ro as soon as the kernel isn't sure whether rw really works. Check the syslog when mounting the device, is it *really* rw?
Here's another pair from /etc/fstab that mount a vfat fs:
LABEL=MX200G /mnt/MX200G vfat noauto,user,dev,suid,exec,umask=000,uid=tom,gid=tom 0 0 # /dev/sdb1
/dev/usb-sdb1 /mnt/usb-sdb1 auto user,noauto,nodev,noatime,nosuid,noexec,rw,uid=tom,gid=tom 0 0
Both
mount /mnt/MX200G
and
mount /mnt/usb-sdb1
work.
Thanks, seems that vfat works but ntfs causes headaches once more. :(
regards, -mika-
Hi, I had to use a different computer to setup the HD. Unfortunately the screen resolution is now different (setup was done with 1024*768, now the resolution on the target is 800*600).
This impacts the framebuffer and it's handling, in console mode not showing all lines, which is annoying.
how can I easily reconfigure on the target machine the LILO setup, so that even with framebuffer the display is ok?
regards peb
* Peter Eberl peb@eberl.com [20061103 22:11]:
I had to use a different computer to setup the HD. Unfortunately the screen resolution is now different (setup was done with 1024*768, now the resolution on the target is 800*600).
This impacts the framebuffer and it's handling, in console mode not showing all lines, which is annoying.
how can I easily reconfigure on the target machine the LILO setup, so that even with framebuffer the display is ok?
Just adjust the vga=... line(s) in /etc/lilo.conf and rerun lilo. For 1024x768 take 'vga=0x0317'.
regards, -mika-
On Fri, 3 Nov 2006, Michael Prokop wrote:
Please show output of:
# vol_id /dev/usb-sda1
# vol_id /dev/usb-sda1 ID_FS_USAGE=filesystem ID_FS_TYPE=ntfs ID_FS_VERSION=3.1 ID_FS_UUID=CEE64717E646FEE9 ID_FS_LABEL=MX320G ID_FS_LABEL_SAFE=MX320G
Basically I wanted to avoid another fstype-check in rebuildfstab. "auto" works pretty well, everything the kernel is aware of works OOTB. The rw becomes ro as soon as the kernel isn't sure whether rw really works. Check the syslog when mounting the device, is it *really* rw?
syslog doesn't have much to say:
Nov 3 16:56:02 grml kernel: NTFS volume version 3.1.
But
# mount ... /dev/usb-sda1 on /mnt/usb-sda1 type ntfs (rw,nosuid,nodev,noexec,noatime,uid=1000,gid=1000,fmask=0177,dmask=077,nls=iso8859-1,errors=continue,mft_zone_multiplier=1)
Thanks,
-- Tom White
On Fri, 3 Nov 2006, Michael Prokop wrote:
- Tom White tom@bulldogcountry.com [20061103 14:53]:
The latest rebuildfstab in my grml installed on hd has these entries:
LABEL=MX320G /mnt/MX320G ntfs noauto,user,dev,suid,exec,ro,umask=000,uid=tom,gid=tom 0 0 # /dev/sda1
/dev/usb-sda1 /mnt/usb-sda1 auto user,noauto,nodev,noatime,nosuid,noexec,rw,uid=tom,gid=tom 0 0
Those are the same drive.
mount /mnt/MX320G
doesn't work; it complains about no LABEL=MX320G device.
Please show output of:
# vol_id /dev/usb-sda1
when your device is available as /dev/usb-sda1. (Seems to be a problem with ntfs.)
mount /mnt/usb-sda1
does work, but I don't like the "rw" on my ntfs file system.
Basically I wanted to avoid another fstype-check in rebuildfstab. "auto" works pretty well, everything the kernel is aware of works OOTB. The rw becomes ro as soon as the kernel isn't sure whether rw really works. Check the syslog when mounting the device, is it *really* rw?
Here's another pair from /etc/fstab that mount a vfat fs:
LABEL=MX200G /mnt/MX200G vfat noauto,user,dev,suid,exec,umask=000,uid=tom,gid=tom 0 0 # /dev/sdb1
/dev/usb-sdb1 /mnt/usb-sdb1 auto user,noauto,nodev,noatime,nosuid,noexec,rw,uid=tom,gid=tom 0 0
Both
mount /mnt/MX200G
and
mount /mnt/usb-sdb1
work.
Thanks, seems that vfat works but ntfs causes headaches once more. :(
regards,
-mika-
http://grml.org/ # Linux for texttool-users and sysadmins http://wiki.grml.org/ # share your knowledge http://grml.supersized.org/ # the grml development weblog #grml @ irc.freenode.org # meet us on irc
* Tom White tom@bulldogcountry.com [20061104 00:15]:
On Fri, 3 Nov 2006, Michael Prokop wrote:
Please show output of:
# vol_id /dev/usb-sda1
# vol_id /dev/usb-sda1 ID_FS_USAGE=filesystem ID_FS_TYPE=ntfs ID_FS_VERSION=3.1 ID_FS_UUID=CEE64717E646FEE9 ID_FS_LABEL=MX320G ID_FS_LABEL_SAFE=MX320G
Ok, finally debugged it: mounting NTFS via label does not work (neither mount.ntfs-3g nor mount.ntfs-fuse seem to support it).
grml-scanpartitions version 0.3-10 is aware of this fact and adds entries like:
/dev/hda5 /mnt/hda5 ntfs ... 0 0 # ntfs does not support mount by label
to /etc/fstab.
regards, -mika-
Teilnehmer (3)
-
Michael Prokop -
Peter Eberl -
Tom White