Custom mount point in fstab

Hello,
I am setting up a nas. I have configured a partition scheme that seems suitable for me. I have a problem though, I can not seem to mount a partiton to a custom mount point.
The system is up to date, I just installed it last night. Here is my fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
UUID=4e373785-4fc9-4b97-aadc-adcbc523bbac /boot ext2 defaults 0 1
UUID=50c83b59-b938-4945-9578-39ab7c40d93b / ext4 defaults 0 1
UUID=8e87d854-a344-4a3c-950f-9831c0811ea2 /data ext4 defaults 0 1
UUID=972cce0c-3c35-4d8a-a0d6-719794bc2766 /tm ext4 defaults 0 1
UUID=d6f940d8-ce03-45c3-bfa9-b7dd83cebbb9 /var reiserfs defaults 0 1
UUID=f01dc9e8-a182-4b89-8043-f6f73690ad6c swap swap defaults 0 0
I want /tm for time machine and /data for samba sharing. If I change /data to /home and /tm to /tmp, everything mounts fine. Is there some reason why I shouldn't be able to mount a partition to a custom mount point? I did this two weeks ago on another box that I set up as a test...
Also, if I run fdisk -l, it tells me that some of my partitions do not start on physical sector boundaries. Is that casue for alarm? I created the partitions with cfdisk and nothing seemed odd when I was doing it...??
[root@nas ~]# fdisk -l
Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 * 63 192779 96358+ 83 Linux
Partition 1 does not start on physical sector boundary.
/dev/sda2 192780 1465149167 732478194 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sda5 192843 5076539 2441848+ 83 Linux
Partition 5 does not start on physical sector boundary.
/dev/sda6 5076603 6056504 489951 82 Linux swap / Solaris
Partition 6 does not start on physical sector boundary.
/dev/sda7 6056568 15824024 4883728+ 83 Linux
/dev/sda8 15824088 1090042379 537109146 83 Linux
/dev/sda9 1090042443 1465149167 187553362+ 83 Linux
Partition 9 does not start on physical sector boundary.
Any insight?

bnb2235 wrote:
Also, if I run fdisk -l, it tells me that some of my partitions do not start on physical sector boundaries. Is that casue for alarm? I created the partitions with cfdisk and nothing seemed odd when I was doing it...??
[root@nas ~]# fdisk -l
Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 * 63 192779 96358+ 83 Linux
Partition 1 does not start on physical sector boundary.
/dev/sda2 192780 1465149167 732478194 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sda5 192843 5076539 2441848+ 83 Linux
Partition 5 does not start on physical sector boundary.
/dev/sda6 5076603 6056504 489951 82 Linux swap / Solaris
Partition 6 does not start on physical sector boundary.
/dev/sda7 6056568 15824024 4883728+ 83 Linux
/dev/sda8 15824088 1090042379 537109146 83 Linux
/dev/sda9 1090042443 1465149167 187553362+ 83 Linux
Partition 9 does not start on physical sector boundary.
AFAIK, if you don't align them it will cause performance issues. Check this site: http://johannes-bauer.com/linux/wdc/?menuid=3

Similar Messages

  • Mount points in fstab

    I'm sure this isn't limited to Mavericks, but that is what I'm currently working with.
    I want to mount a hard disk (volume) on a directory of my choosing. AFAIK this can be done in fstab and anything thus specified is ignored by OSX's other rmounting processes, so it should work.
    The problem I'm having is that the mount point has a space in its name and this CANNOT be changed as something else relies on that exact name. Of course by default, a space in the mount point in fstab will cause problems as it will be seen as a separator, so I quoted the entire path string. Double or single quotes both still cause problems. I tried a back slash in front of the space, but that's no better.
    I have since read in mumerous places that there is this problem, but it can be avoided and the solution I have seen is to instead use the octal \040. Aha I thought, this looks promising, but no, there is still a problem with the mount point name.
    Anyone any thoughts on this, why \040 doesn't work and/or any other solutions?

    Read the guides from Oracle and Linux. I've downloaded a couple of guides (it's not easy to find them). Start with Installation and Admin guides. They will refer to other guides where you can read more about OFA. Read the Linux guides/man pages about mount, fstab, fdisk and partitioning. BTW, I only made 2 partitions for Oracle. One for the system, and one for the data (I think it's enough, because on my system there will be only one database).

  • OS X Lion volume custom mount point identified as Binary Document

    Hi!
    I have a large partition for photos and i mounted it in home folder with /etc/fstab (using vifs):
    UUID=372A78A3-E57A-31AF-AF41-4732DB625394 /Users/vanburg/Photo hfs rw,auto
    It works great in Finder, but when i try to open it in Bridge it opens it on Finder instead.
    There's two additions to default folder icon (in bridge): small arrow (as for alias) and a "locked" icon. "Unlock item" doesn't work.
    This problem only occures when i mount volume in custom folder, in /Volumes all works as expected, but it's not what i want.
    Plz, help me solve this problem. May be it needs to add some flags with chflags, or play with ACL?
    I'm new in os x, but worked for years in unix shell, just point me where to digg.
    Thanks!
    OS X Lion 10.7.4, Bridge CS6

    Omke Oudeman wrote:
    I think you might be better of asking this in a dedicated Apple forum.
    It's definitely adobe bridge problem. Every app i'm using, reads/writes on such tricky mounted volumes without problems. Only Bridge, using it's custom internal file system view technology, have this weird behaviour.
    In folders panel brdige doesn't show Photos folder, while others apps do as usual.
    Omke Oudeman wrote:
    If the partition you created does not show the normal folder structure then it is likely it won't read the files also.
    Yes, obviously
    Omke Oudeman wrote:
    And is there a particular reason why you want your pictures in a separate partition instead of a main folder on your HD or on an other internal or external HD?
    There's a buch of reasons to do that.
    Anyway, thanks for answer, but this is more advanced technical bridge problem. Maybe i should issue a bugreport?

  • [SOLVED] How to automatically mount USB drives with custom mount point

    edit:
    Original title was : 'Unable to mount USB disk via /etc/rc.local', but got changed since the /etc/rc.local problem isn't relevant for me anymore.
    Hello,
    Since I am new to this forum, I'll start off with this :
    Thanks to archlinux, its founder and all its contributors, cause this is the operating system (flavour) that annoys me the least.
    The root problem :
    I want to automount USB storage devices to other places than /media/ and without the need for programs that depend on gnome and the like. As I tried some stuff with hald and such, I didn't really get to a nice and easy to configure solution. Any hints in that direction are always welcome.
    For now, automount of known USB storages devices during boot, will do.
    So the things I tried and didnt work :
    1.
    Provide the disk info to /etc/fstab (via the disks UUID and 'auto' filesystem)
    Add 'mount /mountpoint' to /etc/rc.local
    Result : the mount command in rc.local says '... specify filesystem'
    However, after boot, running /etc/rc.local mounts the USB disks correctly.
    2.
    Provide the disk info to /etc/fstab (via the disks UUID and the correct filesystem)
    Add 'mount /mountpoint' to /etc/rc.local
    Result : pc doesn't get through boot process and gives me the 'ctrl-d to reboot or root passwd for maintenance'
    3.
    Provide no disk info in /etc/fstab
    Add the full mount line to /etc/rc.local (mount -t fs /dev/disks/by-uuid/MyUUID /MyMountpoint )
    Result : don't remember the output of the mount execution, but well, it didn't mount
    However, after boot, running /etc/rc.local mounts the USB disks correctly.
    Is there something that isn't loaded at the time of rc.local execution that I need for mounting of USB devices ? Or why else is this failing ?
    Regards,
    BasiK
    Last edited by BasiK (2009-08-28 07:22:50)

    Thanks for the hint hunterthomson, but the pc I will be using it on, is an own-built HTPC/home file server, so there is no way I want to use a graphical file manager to get the usb disks mounted.
    I tried to figure out a little about udev rules, and I got to do what I wanted to do, so thx for pointing me in that direction Mr.Elendig.
    Btw, I am indeed also using auto-sleep/park disks, but this udev way works perfectly.
    I added two rules files to /etc/udev/rules.d/ :
    The first for a known usb disk (with its volume uuid), with a named mountpoint under my media dir /symbiosis/ :
    [basik@plox ~]$ cat /etc/udev/rules.d/80-usb-utopia.rules
    ACTION=="add", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_UUID}=="a59332c2-07ba-4c52-afb5-20e361bdf71a",SYMLINK+="usb-%n", GROUP="storage", NAME="%k"
    ACTION=="add", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_UUID}=="a59332c2-07ba-4c52-afb5-20e361bdf71a",RUN+="/bin/mkdir -p /symbiosis/utopia"
    ACTION=="add", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_UUID}=="a59332c2-07ba-4c52-afb5-20e361bdf71a", RUN+="/bin/mount -t auto -o rw,noauto,sync,dirsync,noexec,nodev,noatime /dev/%k /symbiosis/utopia", OPTIONS="last_rule"
    ACTION=="remove", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_UUID}=="a59332c2-07ba-4c52-afb5-20e361bdf71a", RUN+="/bin/umount -l /symbiosis/utopia", OPTIONS="last_rule"
    The second for unknown usb disks, to mount under the same dir. This is simply taken from the archwiki http://wiki.archlinux.org/index.php/Ude … .26_Tricks
    Make sure these rules are executed after the ones for specific usb disks.
    [basik@plox ~]$ cat /etc/udev/rules.d/usb-disks.rules
    KERNEL=="sd[a-z]", NAME="%k", SYMLINK+="usb%m", GROUP="storage", OPTIONS="last_rule"
    ACTION=="add", KERNEL=="sd[a-z][0-9]", SYMLINK+="usb%n", GROUP="storage", NAME="%k"
    ACTION=="add", KERNEL=="sd[a-z][0-9]", RUN+="/bin/mkdir -p /symbiosis/usb%n"
    ACTION=="add", KERNEL=="sd[a-z][0-9]", RUN+="/bin/mount -t auto -o rw,noauto,sync,dirsync,noexec,nodev,noatime /dev/%k /symbiosis/usb%n", OPTIONS="last_rule"
    ACTION=="remove", KERNEL=="sd[a-z][0-9]", RUN+="/bin/umount -l /symbiosis/usb%n"
    ACTION=="remove", KERNEL=="sd[a-z][0-9]", RUN+="/bin/rmdir /symbiosis/usb%n", OPTIONS="last_rule"
    These may not be the nicest looking udev rules, but it works for what I wanted to do with it.

  • [Solved] External Hard Drive mount point in fstab crashes launch

    Hi there,
    I have an external hard drive that I'd like to automount when I plug it in. Sometimes it seems to work, but other times I have to manually mount it. In order to make this a little easier, I copied the mounting info into my fstab file so that I could just run:
    mount /dir/to/mount
    However, now I can't actually boot up my machine unless the external drive is plugged in. I get some error from systemctrl saying one of the drives couldn't be loaded. 
    An obvious work around would be to write a one line script that mounts the drive for me, however, I'd like to learn how to do this correctly. I think the rules have changed a bit with systemd, as I didn't have this problem a few years ago. 
    Thanks for the help!
    Last edited by B-80 (2015-05-17 08:14:08)

    B-80 wrote:
    Head_on_a_Stick wrote:
    Add "nofail" to the options section.
    EDIT: ...in /etc/fstab
    Thanks for the answer, that fixed it.
    You're welcome but I think Mr.Elendig's post gives the actual solution (my proposal is just a workaround -- using fstab for a filesystem that is not permanently attached is sub-optimal)

  • Unable to open and save across mount point

    Why do these forums appear so neglected?
    Here's is my on-going question/problem:
    General input/output error while accessing /home/MyDir/mountedDir/SomeDire/TheFileName
    I experience a "feature" wherein I cannot open and save documents across an NFS mount point from a Linux client.
    This is an error rcv'd on Linux, GNOME 2.8.*, 2.6.10-gentoo-r6
    The mount is accomplished via an entry in the fstab as shown:
    server-hostname:/export/mydir /home/mydir/mountdir nfs tcp,user,rw,rsize=32768 0 0
    server-hostname is a Solaris OS.

    Sounds like you are missing some of the required plugins - possibly an updater failed, or someone moved/deleted the wrong directory.
    Yes, you'll need to reinstall to restore the missing plugins.

  • How to determine the mount point for directory /tmp ?

    Folks,
    Hello. I am installing Oracle 11gR2 RAC using 2 Virtual Machines (rac1 and rac2 whose OS are Oracle Linux 5.6) in VMPlayer and according to the tutorial
    http://appsdbaworkshop.blogspot.com/2011/10/11gr2-rac-on-linux-56-using-vmware.html
    I am installing Grid infrastructure. I am on step 7 of 10 (verify Grid installation enviroment) and get this error:
    "Free Space: Rac2: /tmp"
    Cause: Could not determine mount point for location specified.
    Action: Ensure location specified is available.
    Expected value: n/a
    Actual value: n/a
    I have checked the free space using the command:
    [root@Rac2 /]# df -k /tmp
    Output:
    Filesystem     1k-blocks     used     Available     Use%     Mounted on
    /dev/sda1     30470144     7826952     21070432     28%     /
    As you see above, the free space is enough, but could not determine mount point for /tmp.
    Do any folk understand how to determine the mount point for directory /tmp ?
    Thanks.

    I have just checked "/home/oracle/.bash_profile". But in my computer, there is no "oracle" under /home directory.Is this your first time Linux and Oracle installation? I had a brief look at your referenced link. The reason why you do not find a "oracle" user is because the instructions use "ora11g" instead, which, btw, is not standard. The directories of your installation and your installation source can be somewhat different from known standards and you will have to adjust it to your system.
    My best guess is that you have either missed something in the instructions or you need to ask the author of the blog what is wrong. The chance to find someone here who has experience with these custom instructions is probably unlikely.
    I suggest you try to locate the cluster verification tool, which should be in the bin directory of your grid installation. Alternatively you might want to check the RAC, ASM & Clusterware Installation forum: RAC, ASM & Clusterware Installation

  • [SOLVED] Mount Points In Arch Linux

    When I performed my initial testing install of Arch Linux today, and I was setting up mount points after I finished partitioning with Cfdisk, I was surprised to see that one of the precanned mount points in the Installer was /etc. On OpenBSD, we were warned against having /etc on its own partition, probably because so much important stuff lives there (like the fstab). I was also surprised to see /var wasn't in the precanned list.
    Anyway, my question is, can you really have /etc on it's own partition? And does the exclusion of /var indicate a problem with it being on its own partition?
    Last edited by NerveJessen (2010-04-02 12:50:38)

    NerveJessen wrote:
    It almost sounds like /var was accidently replaced by /etc.
    EDIT: I'll look into the bug reporting procedures.
    http://bugs.archlinux.org/
    There is the FLySpray link, and there is a button at the top right of your screen as well.
    Post back within this thread with your bug report, so other users may vote for the task once it has been assigned to a developer.
    Welcome to Arch!

  • Using "nested" Mount Points within Mount Points to add additional LUNs to a server

    I realize that this might or might not be common and I haven't read or seen anything about this. So here goes...
    No clustering. Just a strightup adding LUNs to a server mount point.
    I have no issues adding a lun to a mount point (folder on the C-Drive) called MountPoint1. I can build a folder within MountPoint1 and add another LUN to a mountpoint within the first called NestedMountPoint1. I can build another folder within NestedMountPoint1
    and add another LUN to a mountpoint within the second called NestedMountPoint2.
    c:\MountPoiint1 (500GB)
       |-NestedMountPoint1 (300GB)
          |-NestedMountPoint2 (300GB)
    First, do people do this? (Is it a normal practice?) (Recommended?)
    Second, If it is a normal practice, Is there a limit on how many you can nest?
    I can see doing this to add storage to a drive. BUT...

    Hi,
    A mount point is just a logical way to present drives to a system without using drive letters.  You can nest mount points, but it is recommended to use the root (host) volume exclusively for mount points. The root volume is the volume that is hosting
    the mount points. This greatly reduces the time that it takes to restore access to the mounted volumes if you have to run a chkdsk. This also reduces the time that it takes to restore from backup on the host volume.
    For more detailed information, please refer to the articles below:
    How to configure volume mount points on a Microsoft Cluster Server
    http://support.microsoft.com/kb/280297
    Understanding NTFS volume mount points
    https://library.netapp.com/ecmdocs/ECMP1217281/html/GUID-C6537E25-1E71-40F8-A1AF-F0DEED4C865D.html
    Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
    Regards,
    Mandy
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Mount point /proc/bus/usb does not exist

    Does anybody know why this mount point would not be there? There is indeed a directory at that location...

    hi,
    kleptophobiac wrote:Does anybody know why this mount point would not be there? There is indeed a directory at that location...
    sarah31 wrote:perhaps it is the syntax in your fstab?
    Nope, it's a miracle, concerning the scsi kernel only, AFAIK. Some devs have
    rebuilt with some module variations but no clue so far where it does come
    from.
    It goes like that:
    usbcore loads usbfs (when it shouldn't), at a time when proc is not mounted.
    usbfs tries to create the dir and throws that error. Later on boot process
    hotplug corrects that. So it's a kind of annoyance, but it does feel
    uncomfortable as long as no one where it does come from :-/
    -neri

  • Firewire mount points

    Ladies and Gentlemen:
    Ii have a difficult question to answer:
    I have 2 daisy-chained Firewire LaCie Drives
    1. Time Machine
    2. for the User directory
    The 2. drive is sometimes mounted on "/Volumes/Users" or "/Volumes Users 1" which causes problems accessing the "Users" directory and initiates a fallback to the harddrive.
    I do not know why this happens. And I do not know how to prevent it.
    Does anyone knows the reason for this behavior (obviously the "User 1" is created because a "User" mount point already exists…)
    When the "Time Machine" is switched of the mount point stays the same. But when it is on it changes…
    My temporarily solution now is to connect the "Time MAchine" with a FW400 cable. But thats not the desired final solution…
    Any solutions available?
    Thank you very much.
    Kind regards
    Dieter Zakel MD MA

    Well, I went ahead and created the file fstab in /etc. Using df after a reboot showed that the volume was mounted at the pspecified place. So, the fstab file work. I used the LABEL= construct so as not to have to rely on the order the firewire devices were plugged in.
    However, the volumes stall all show up on the desktop. I conclude that the volume list is not generated from the /Volumes directory. So ... still not solved.

  • Fixed mount points for USB disks via HAL

    I've been trying to figure this out on my own but I've been able to achieve my goal.
    I want to setup my system so that it auto-mounts a specific hard drive and makes its contents available at a specific file system location.
    I'd love to do that by identifying my hard drives by UUID or ID and assigning each one a different mount point.
    I've tried the approach described in the ArchWiki:
    File: /etc/hal/fdi/policy/20-$device_name.fdi
    <?xml version="1.0" encoding="UTF-8"?>
    <deviceinfo version="0.2">
    <device>
    <match key="volume.uuid" string="$device_uuid">
    <merge key="volume.label" type="string">$device_name</merge>
    </match>
    </device>
    </deviceinfo>
    http://wiki.archlinux.org/index.php/HAL#About_volumes_mount_points
    and this one:
    <device>
    <match key="info.udi" string="/org/freedesktop/Hal/devices/volume_uuid_E265_5E6A">
    <merge key="volume.policy.desired_mount_point" type="string">ipod</merge>
    <merge key="volume.policy.mount_option.iocharset=iso8859-15" type="bool">true</merge>
    <merge key="volume.policy.mount_option.sync" type="bool">true</merge>
    </match>
    </device>
    http://www.mythic-beasts.com/~mark/random/hal/
    I restart HAL each time I change the configuration of the 20-$device_name.fdi or preferences.fdi (the second code example). Nothing at all can be found in /var/log/messages. It just silently refuses to mount the devices.
    It works okay without these configurations and HAL auto-mount all these hard drives but only if I do not mess with the configs in /etc/hal/fdi/policy.
    Can someone please explain what could be wrong here?

    Dehir wrote:Im actually having similar difficulties. Have created etc/hal/fdi/policy/20-$device_name.fdi names for each device. But when im trying mount them from pcmanfm they get mounted every single time by random order, which is not that i want. Id prefer hal mounting over fstab but still want them to be mounted with specific names.
    Yeah, that's the whole point - I want to have it done automatically with only one condition - fixed mount point names.

  • Udev mount point

    Hi,
    I'm brand new to Arch from Gentoo so please take it easy. I'm trying to set a fixed mount point for my external hard drive (with my music on it) using udev. (as it doesn't make sense to put an external drive in fstab)
    I've copied across my old rule from my gentoo install on the same machine:
    /etc/udev/rules.d/10-local.rules
    SUBSYSTEMS=="usb", ATTRS{serial}=="2HBEQTN2 ", KERNEL=="sd?", SYMLINK+="external", GROUP="storage"
    SUBSYSTEMS=="usb", ATTRS{serial}=="2HBEQTN2 ", KERNEL=="sd?1", SYMLINK+="external", GROUP="storage"
    But for some reason it doesn't seem to have any effect on my new Arch system (I have rebooted so shouldn't be an issue with restarting udev).
    Since udev makes me want to cry does anyone have any ideas?

    Here's my output of $udevadm info -a -p $(udevadm info -q path -n /dev/sdb)
    Udevadm info starts with the device specified by the devpath and then
    walks up the chain of parent devices. It prints for every device
    found, all possible attributes in the udev rules key format.
    A rule to match, can be composed by the attributes of the device
    and the attributes from one single parent device.
    looking at device '/devices/pci0000:00/0000:00:02.1/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0/block/sdb':
    KERNEL=="sdb"
    SUBSYSTEM=="block"
    DRIVER==""
    ATTR{range}=="16"
    ATTR{ext_range}=="256"
    ATTR{removable}=="0"
    ATTR{ro}=="0"
    ATTR{size}=="976773168"
    ATTR{alignment_offset}=="0"
    ATTR{discard_alignment}=="0"
    ATTR{capability}=="52"
    ATTR{stat}==" 153 91 1362 25060 8 0 8 23 0 25030 25083"
    ATTR{inflight}==" 0 0"
    looking at parent device '/devices/pci0000:00/0000:00:02.1/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0':
    KERNELS=="6:0:0:0"
    SUBSYSTEMS=="scsi"
    DRIVERS=="sd"
    ATTRS{device_blocked}=="0"
    ATTRS{type}=="0"
    ATTRS{scsi_level}=="3"
    ATTRS{vendor}=="Maxtor "
    ATTRS{model}=="Basics Desktop "
    ATTRS{rev}=="0122"
    ATTRS{state}=="running"
    ATTRS{timeout}=="30"
    ATTRS{iocounterbits}=="32"
    ATTRS{iorequest_cnt}=="0xcd"
    ATTRS{iodone_cnt}=="0xcc"
    ATTRS{ioerr_cnt}=="0x1a"
    ATTRS{modalias}=="scsi:t-0x00"
    ATTRS{evt_media_change}=="0"
    ATTRS{queue_depth}=="1"
    ATTRS{queue_type}=="none"
    ATTRS{max_sectors}=="240"
    looking at parent device '/devices/pci0000:00/0000:00:02.1/usb1/1-1/1-1:1.0/host6/target6:0:0':
    KERNELS=="target6:0:0"
    SUBSYSTEMS=="scsi"
    DRIVERS==""
    looking at parent device '/devices/pci0000:00/0000:00:02.1/usb1/1-1/1-1:1.0/host6':
    KERNELS=="host6"
    SUBSYSTEMS=="scsi"
    DRIVERS==""
    looking at parent device '/devices/pci0000:00/0000:00:02.1/usb1/1-1/1-1:1.0':
    KERNELS=="1-1:1.0"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb-storage"
    ATTRS{bInterfaceNumber}=="00"
    ATTRS{bAlternateSetting}==" 0"
    ATTRS{bNumEndpoints}=="02"
    ATTRS{bInterfaceClass}=="08"
    ATTRS{bInterfaceSubClass}=="06"
    ATTRS{bInterfaceProtocol}=="50"
    ATTRS{modalias}=="usb:v0D49p7410d0122dc00dsc00dp00ic08isc06ip50"
    ATTRS{supports_autosuspend}=="0"
    looking at parent device '/devices/pci0000:00/0000:00:02.1/usb1/1-1':
    KERNELS=="1-1"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{configuration}==""
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bmAttributes}=="c0"
    ATTRS{bMaxPower}==" 2mA"
    ATTRS{urbnum}=="707"
    ATTRS{idVendor}=="0d49"
    ATTRS{idProduct}=="7410"
    ATTRS{bcdDevice}=="0122"
    ATTRS{bDeviceClass}=="00"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bDeviceProtocol}=="00"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{speed}=="480"
    ATTRS{busnum}=="1"
    ATTRS{devnum}=="2"
    ATTRS{devpath}=="1"
    ATTRS{version}==" 2.00"
    ATTRS{maxchild}=="0"
    ATTRS{quirks}=="0x0"
    ATTRS{authorized}=="1"
    ATTRS{manufacturer}=="Maxtor "
    ATTRS{product}=="Basics Desktop "
    ATTRS{serial}=="2HBEQTN2 "
    looking at parent device '/devices/pci0000:00/0000:00:02.1/usb1':
    KERNELS=="usb1"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{configuration}==""
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bmAttributes}=="e0"
    ATTRS{bMaxPower}==" 0mA"
    ATTRS{urbnum}=="46"
    ATTRS{idVendor}=="1d6b"
    ATTRS{idProduct}=="0002"
    ATTRS{bcdDevice}=="0206"
    ATTRS{bDeviceClass}=="09"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bDeviceProtocol}=="00"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{speed}=="480"
    ATTRS{busnum}=="1"
    ATTRS{devnum}=="1"
    ATTRS{devpath}=="0"
    ATTRS{version}==" 2.00"
    ATTRS{maxchild}=="10"
    ATTRS{quirks}=="0x0"
    ATTRS{authorized}=="1"
    ATTRS{manufacturer}=="Linux 2.6.33-ARCH ehci_hcd"
    ATTRS{product}=="EHCI Host Controller"
    ATTRS{serial}=="0000:00:02.1"
    ATTRS{authorized_default}=="1"
    looking at parent device '/devices/pci0000:00/0000:00:02.1':
    KERNELS=="0000:00:02.1"
    SUBSYSTEMS=="pci"
    DRIVERS=="ehci_hcd"
    ATTRS{vendor}=="0x10de"
    ATTRS{device}=="0x005b"
    ATTRS{subsystem_vendor}=="0x1043"
    ATTRS{subsystem_device}=="0x815a"
    ATTRS{class}=="0x0c0320"
    ATTRS{irq}=="23"
    ATTRS{local_cpus}=="ffff"
    ATTRS{local_cpulist}=="0-15"
    ATTRS{modalias}=="pci:v000010DEd0000005Bsv00001043sd0000815Abc0Csc03i20"
    ATTRS{dma_mask_bits}=="32"
    ATTRS{consistent_dma_mask_bits}=="31"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}==""
    ATTRS{companion}==""
    looking at parent device '/devices/pci0000:00':
    KERNELS=="pci0000:00"
    SUBSYSTEMS==""
    DRIVERS==""

  • Does Solaris supports non-ASCII mount point?

    Hi,
    Does Solaris 10 supports non-ASCII mount point?
    Kind regards,
    Daniel

    # fstab generated by gen_fstab
    #<file system>   <dir>         <type>      <options>    <dump> <pass>
    none            /dev/pts      devpts      defaults        0     0
    none            /dev/shm      tmpfs       defaults        0     0
    UUID=496E-7B5E /media/STORAGE vfat    defaults,user,users,rw,exec,uid=777,gid=777   0       0
    /dev/sr0     /mnt/sr0_cd  auto     user,noauto,exec,unhide 0     0
    # This would do for a floppy
    #/dev/fd0        /mnt/floppy    vfat,ext2 rw,user,noauto    0     0
    #    +   mkdir /mnt/floppy
    # E.g. for USB storage:
    #/dev/sdb1        /mnt/usb      auto      rw,user,noauto   0     0
    #    +   mkdir /mnt/usb

  • Not mounting HDD from fstab

    Hi!
    Until last week my external HDD was mounted automatically during the boot but now it's not.
    I haven't modified anything related to the fstab.
    This is what the fstab file contains:
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    devpts /dev/pts devpts defaults 0 0
    shm /dev/shm tmpfs nodev,nosuid 0 0
    #/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
    #/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
    #/dev/fd0 /media/fl auto user,noauto 0 0
    /dev/sda5 / ext4 defaults 0 1
    /dev/sda6 swap swap defaults 0 0
    /dev/sda7 /home ext4 defaults,user_xattr 0 2
    /dev/sdc1 /media/HDD ntfs-3g defaults 0 0
    # mount point for Acer A500
    mtpfs /media/a500 fuse user,noauto,allow_other 0 0
    tmpfs /tmp tmpfs defaults,nosuid 0 0
    /dev/sc1 is the partition I want to mount during the boot:
    Disk /dev/sda: 500.1 GB, 500107862016 bytes, 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: 0x00080fa8
    Device Boot Start End Blocks Id System
    /dev/sda1 63 976768064 488384001 5 Extended
    /dev/sda5 126 52436159 26218017 83 Linux
    /dev/sda6 52436223 54540674 1052226 82 Linux swap / Solaris
    /dev/sda7 54540738 976768064 461113663+ 83 Linux
    Disk /dev/sdc: 1000.2 GB, 1000170586112 bytes, 1953458176 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: 0x00073856
    Device Boot Start End Blocks Id System
    /dev/sdc1 2048 1953458175 976728064 7 HPFS/NTFS/exFAT
    Any idea of what could be happening?

    Lone_Wolf wrote:
    sounds like sometimes the drive is not ready yet when the system tries to mount it.
    Also you're fstab is not listing anything with dev/sdb .
    please post the output of
    #fdisk -l
    so we can see what drives are present on your system.
    Is sdc an external or internal harddrive ?
    if an external drive how is it connected ( usb, eSata, firewire, bluetooth, network ) ?
    I've posted that output before:
    Disk /dev/sda: 500.1 GB, 500107862016 bytes, 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: 0x00080fa8
    Device Boot Start End Blocks Id System
    /dev/sda1 63 976768064 488384001 5 Extended
    /dev/sda5 126 52436159 26218017 83 Linux
    /dev/sda6 52436223 54540674 1052226 82 Linux swap / Solaris
    /dev/sda7 54540738 976768064 461113663+ 83 Linux
    Disk /dev/sdc: 1000.2 GB, 1000170586112 bytes, 1953458176 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: 0x00073856
    Device Boot Start End Blocks Id System
    /dev/sdc1 2048 1953458175 976728064 7 HPFS/NTFS/exFAT
    Oh sorry! It's true, I forgot that info.
    It's an external HDD. Exactly a WD My Book Essential of 1TB connected by USB

Maybe you are looking for