Stop USB Drive unmounting at User Logoff

When my users logoff, the external USB drive is unmounted. The external drive is used to hold the users home directory. I have placed an entry in fstab as:
+*/dev/disk1s6 /Mount/LaCie hfs noowners 0 2*+
The mount works with +*mount -a*+
I got the system to stop from unmounting the drive at login with the command
+*defaults write /Library/Preferences/SystemConfiguration/autodiskmount AutomountDisksWithoutUserLogin -bool YES*+
which I found in another post.
At this point I have to issue a mount after as user logs off, which is pretty rare at my house, fortunately.
How can I change my systems behavior to leave the /Mount/LaCie drive mounted when the users log on or off?

Teresa Meerschaert wrote:
+*defaults write /Library/Preferences/SystemConfiguration/autodiskmount AutomountDisksWithoutUserLogin -bool YES*+
That command should keep disks mounted no matter who logs in or out. Isn't it working for you? Did you reboot after entering the command?

Similar Messages

  • Mounting USB drive as regular user (with ntfs-3g)

    Hello. First of all, I not asking to do the homework for me, rather is someone can help me understand why I can't get this work.
    I spent the last night trying to figure how mount an USB drive as a regular user, using ntfs-3g. I read the related wiki entries and researched quite a lot in the forums. I came up with this:
    fstab:
    # /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/sda1 / ext3 defaults,noatime 0 1
    /dev/sda2 /home ext3 defaults,noatime 0 2
    /dev/sda3 swap swap defaults 0 0
    /dev/sdb1 /mnt/usb ntfs-3g noauto,uid=0,gid=0,noatime,umask=000, 0 0
    I created a ntfsuser group, added my user to that group and trim permissions to the ntfd-3g executable (link in this post). That allows me mount the partition as root and read/write as regular user. It works, so (i think) not big deal here.
    However if I add user to the mount options the following error shows up:
    Mount is denied because setuid and setgid root ntfs-3g is insecure with the
    external FUSE library. Either remove the setuid/setgid bit from the binary
    or rebuild NTFS-3G with integrated FUSE support and make it setuid root.
    Please see more information at http://ntfs-3g.org/support.html#unprivileged
    What bugs me the most is I don't understand why I can't mount as regular user when the user option is set in the fstab. Shouldn't that allow regular users to mount and unmount? Is not like that I'm mounting and dismounting USB drives every 5', but I would like to get this done because I know it can be done
    Sorry for asking such trivial question, but I sense that I'm missing something really stupid and I just can't figure what it is

    Beware of the double post! (+1)
    Ok, I decided I'd get this to work, although the method and the implications it could have might not seem pretty to some. There are certain conditions for a user to mount any ntfs volume with ntfs-3g, I will name them here:
    1. ntfs-3g with integrated fuse support. You'll get this by:
        1A. Removing ntfs-3g and fuse from your system if you have them installed as separate packages, so do this as root:
    pacman -Rn ntfs-3g
    pacman -Rn fuse
    Now you can install the new package.
        1B. Getting a modified version of the PKGBUILD found in that AUR link previously mentioned by me, here's mine:
    # Maintainer: Gula <gulanito.archlinux.org>
    # Slightly modified by anderfs
    # Don't forget to setuid-root for the ntfs-3g binary after you install this
    pkgname=ntfs-3g-fuse-internal
    pkgver=2010.5.16
    pkgrel=1
    pkgdesc="Stable read and write NTFS driver (whit internal fuse suport)"
    url="http://www.tuxera.com"
    arch=('i686' 'x86_64')
    license=('GPL2')
    depends=('glibc')
    conflicts=('ntfs-3g')
    makedepends=('pkgconfig')
    options=('!libtool')
    source=(http://www.tuxera.com/opensource/ntfs-3g-${pkgver}.tgz
    http://aur.archlinux.org/packages/ntfs-3g-fuse-internal/ntfs-3g-fuse-internal/25-ntfs-config-write-policy.fdi)
    sha1sums=('895da556ad974743841f743c49b734132b2a7cbc'
    '200029f2999a2c284fd30ae25734abf6459c3501')
    build() {
    cd "${srcdir}/ntfs-3g-${pkgver}"
    ac_cv_path_LDCONFIG=/bin/true ./configure --prefix=/usr \
    --with-fuse=internal --disable-static || return 1
    make || return 1
    package() {
    cd "${srcdir}/ntfs-3g-${pkgver}"
    make DESTDIR="${pkgdir}" install || return 1
    ln -s /bin/ntfs-3g "${pkgdir}/sbin/mount.ntfs" || return 1
    install -m755 -d "${pkgdir}/usr/share/hal/fdi/policy/10osvendor"
    install -m644 "${srcdir}/25-ntfs-config-write-policy.fdi" "${pkgdir}/usr/share/hal/fdi/policy/10osvendor/" || return 1
    Save this as PKGBUILD, preferrably in an empty directory so it doesn't clutter things up when you build it.
        1C. Now go to the directory where you saved it and do this as a regular user:
    makepkg PKGBUILD
    After that's done, you'll get a package called ntfs-3g-fuse-internal-2010.5.16-1-i686.pkg.tar.xz, or something similar.
        1D. Install that package as root:
    pacman -U ntfs-3g-fuse-internal-2010.5.16-1-i686.pkg.tar.xz
    If all went well you now have ntfs-3g compiled with integrated fuse support.
    2. The ntfs-3g version must be higher than 1.2506, this is already covered, the package installed from AUR matches this requirement.
    3. The ntfs-3g binary must be set to setuid-root, to accomplish this you shall do the following as root:
    chown root $(which ntfs-3g)
    chmod 4755 $(which ntfs-3g)
    I used 4750 instad of 4755, I guess that last bit can be a matter of personal taste as long as it isn't something obnoxious like "7".
    4. The user must have the right access to the volume. Okay, this is the ugly part, volumes are owned by root and managed by the disk group with permissions brw-rw----, this means you have to add any users you want mounting this volume to the disk group.
        4A. So, do this as root:
    gpasswd -a [user] disk
    Where [user] is obviously the name of whichever user you're adding to the disk group, do this for any user you want mounting this volume.
        Any users currently logged in will have to log out and back in for these change to take effect, this most likely includes you.
        4B. Now that you logged back in, try this:
    groups
    One of the groups listed should be disk, if it's not there you didn't completely log out of all open sessions.
    5. The user must have the right permissions/access to the mount point. For a user to be able to mount something to a mount point, that user needs to have read permission (pretty self-explanatory), write permission (so the user can make any changes to the sub-structure of the mount point), and execute permission (so the user can change-dir to that mount point) to it. Mount points can be anywhere, so this really depends where you're mounting.
    In my case, I'm mounting these volumes on certain directories under /mnt/, for example /mnt/example. If you're mounting stuff there, you might as well take advantage of the fact your "mounting user" is already in the group disk, and do the following as root:
    chgrp disk /mnt/example
    chmod 774 /mnt/example
    Now users in the disk group will be able to manage these mount points.
    6. Mount it. That's it, you should now be able to mount ntfs volumes as an "unpriveleged enough" user. Here's an example of what you'd have to put in /etc/fstab:
    UUID=XXXXYYYYXXXXYYYY /mnt/example ntfs-3g noauto,noatime,user,uid=0,gid=6,fmask=137,dmask=027,rw 0 0
    uid=0 means root will be the owner of this mount-point and anything in it after it's mounted. This is due to the fact that even though users might own their mountpoints and have rwx permissions on them, you might still not want them to write to the mounted ntfs volumes. Remove this if you want them to be able to write to the volume.
    gid=6 means this will be managed by the disk group in my system. Perhaps the disk group has a different id in your system, run "id root" to find out, as root usually is part of this group.
    fmask = 137 means the owner (root) can do anything with files in this volume except executing files. Group members (disk) can only read files here, not create or execute them. And other users can't do anything in this volume.
    dmask = 027 means the owner can do anything with directories (execute here is needed to chdir), users can't write directories but they can read or execute in them (once again, needed by 'cd'), and finally other users still don't have any access.
    You can use whichever fmask and dmask makes sense to you, or use an umask instead.
    Last edited by anderfs (2010-07-15 11:34:48)

  • USB Drive unmounts from airport extreme

    I have a 1TB segate USB drive mounted on my Airport etreme which I mapped as drive z: on my win 8 laptop.
    Somtimes when the laptop comes out of sleep mode, the drive will not remount unless I reboot the PC.
    Somtimes I can't even remount the drive using the base station agent, it will not let me log into the drive.
    Yes the drive is formatted as fat32.
    Any suggestions?

    You can use thumb drive.. it has to be formatted correctly.. fat32 or HFS+ of course.
    And they are not very big.. so I am not sure how big your songs are.. in the apple world you have your songs on itunes and definitely this is unsuitable for the itunes library.. you still need itunes on a computer to share it to the network.

  • Mounting USB Drive in Single user mode

    My Intel Imac fails to boot up. fsck -y fails too ... can't think of any other way to get my data out ...
    I am left with the only option to copy my data into my usb drive in the terminal mode .
    But I am unable to mount my USB drive. I also need to know the mount point. can anyone provide me with help.

    The mountpoint can be anything you want. The tricky part is figuring out the device your drive is using. I don't know for sure (can't test it right now), but dmesg or one of the system logs might have that information in it if you boot to SUM with the external drive attached. The logs also might have a record of what device this drive used in the past when connected. It will likely use the same device every time.
    If not, you can guess. I have seen one of my external disks mount using the device disk1s2. If I were to attach that to my machine in SUM, I could then mount it like this:
    mount_hfs /dev/disk1s2 /Volumes/recover
    where the mount point /Volumes/recover is something I created (i.e. just a simple "mkdir /Volumes/recover"). This could be anything you want.

  • Stopping USB Drive Autostart?

    Whenever I insert a USB mass storage drive, Album Starter 3 starts and scans the drive (Win XP). I'd rather it starts only when I ask it to start, rather than every time I connect something to the USB port. How do I stop the Autostart?
    TIA, George Steeg

    Thanks for the tip. I will attempt to resolve my issue with this information. I'm not sure if this will solve my problem. The Photoshop Starter Ed.3., seems to autostart without my prompting it and its a problem. So once again thanks for the tip.

  • MBPR usb drives "unmounting" problem

    New MBPR 16GB 256GB 10.7.4
    Periodially mounted volumes dissapear with the "you didn't eject the drive first" warning.
    Has happened repeatably in front of me and have seen it upon returning to my computer after being left alone.
    Could be a bug in sleep functions?
    Anyone else?

    I have a solution that I just verified.
    My USB3 array kept unmounting while in Final Cut Pro X, and it was maddening. It did not suffer the unmounting bug while copying between drives…only when it was doing background tasks like transcoding it would run for about 15 min. then simply unmount and report "Disk improperly disconnected…" dialog. Of course it broke my mirror, corrupted files etc. as you might expect. I had to power cycle the array to get it to work again. My JBOD PM array has 5 drives…a 2 disk 2TB SoftRAID stripe, a single 1TB and a pair of 4TB mirrored in SoftRAID. Now I had configured this SansDigital esata/USB3 5 disk array before I got the new MBP that had USB3 on it, using an esata bus on an older machine and it was flawless for 2 months of work. All disks SoftRAID certified, no issues. I also got flawless (if much slower, as expected) operation connecting it to a USB 2 port on an old MBP.
    I had a eureka moment today, and I think it may help a lot of others suffering similar issues.
    I went on the internet and saw a bunch of folks on the Apple support forums having similar issues with USB3 unmounting drives.  Then it hit me….15 minutes was the time set in Energy Saver to sleep the computer or try to spin down drives (the "Put hard disks to sleep when possible" option is checked by default). From my Google search I read on a PC site that USB3 as a protocol hates to be slept in its current version, so...using the Mac equivalent of that PC sites Windows suggestion, I unchecked the "Put hard disks to sleep when possible" option in Energy Saver, and set the MBP to never sleep with Power Adapter connected, and I am pleased to report I have been working in FCP without incident for the last 5 hours. Everything is cranking away much faster than before and without a problem.
    I did not test sleeping the computer and having the drives eject (another issue reported as lot), but at least this looks like it is operating reliably. My assumption would be sleeping would kill the USB3 connection, so eject the drives when sleeping to be safe.
    Hope this helps,
    KJ Doyle

  • Manage USB drives / removal with VMWare Workstation in Unity mode

    We have a peice of legacy software that only runs on windows XP. Our deployment has it running on VMware Workstation in Unity mode. A constant issue is USB drives. The users need to connect USB drives to the legacy app. 
    The way i'ts currently managed: the drives are set to auto-mount into VMWare with the VID and PID of the drives. Then a DriveRemove.exe utility bat file is setup to eject the drives, and a shortcut is placed on the users desktop. Is there a better way to do this? 
    This topic first appeared in the Spiceworks Community

    Really disappointed in Apple after this!
    I've had my iPhone 4S still on iOS5, and wanted to update to iOS6 today. I tried over the air, but it kept failing and suggesting that I try it with iTunes. My iPhone hasn't been connected to iTunes for months, so I first had to update, which makes updating already quite annoying as it doesn't work as intended.
    After updating my iTunes, it found my iPhone and I hit Update. After some time it just stopped and failed on me, my iPhone went into recovery mode. After reconnecting to iTunes I get the message; "Your iPhone is in recovery mode, please recover" with a "OK" button. I hit that button and the Update/Restore screen disappears.
    Luckily I found the log files in my User data folder and were able to figure out the error number, but for a normal user this would be a point they would give up! My next smartphone might not be an iPhone, the hardware and the experience is great on an iPhone. But updating/settings/app-management and iTunes just suck!

  • WD My cloud USB drive mount command???

    Hello,
    I've a backup script which is autoscheduled and backs up my data to the usb drive. I would like to keep usb drive unmounted until the script starts since twonky scans my usb drive as well and I couldn't disable it from both twonky setup and my cloud UI. After reboot it starts scanning again. (if you know this, it will be a better solution)
    So after reboot I would like to unmount the usb disk. I found the unmount command in the forum. Thansk to Nazar.
    However I don't know how to mount the drive from the script.
    Can you please help me on this?
    Thanks...

    mount [ -o options,.. ] /dev/sdb1 /path/to/existing/directory  or if you know your stuffs let it auto mount on boot, edit /etc/fstab as below, then mount -a or mount /dev/sdb1: /dev/sdb1   /path/to/existing/directory   filesystem(i.e. vfat)  options(i.e. defaults)    backup-dump(i.e. 0)   pass-fsck(i.e. 0) Note all above is not supported by WD and warrants warranty void. Wrong fstab entries may not boot up your nas properly so I don't recommend this unless you fully understood. I did a mistake once while mounting additional swap space which end up opening the drive just to recover. Read more https://en.wikipedia.org/wiki/Fstab

  • Hard Drive Unmounting Itself

    Hi,
    I have a WD MyBook USB external hard drive that used to work fine. Now, it will not mount unless I unplug its power for at least 15 minutes, plug the power back in, and then plug it into my MacBook Pro. Once it mounts, it will then unmount itself after about an hour. The power light on the hard drive never turns off, though. I've searched the discussion and can't find any similar problems. Any help with this would be greatly appreciated. Thanks.

    I am having the same issue.... the USB drive unmounts at unexpected moments.
    For me, it happens always with iTunes open, or when trying to transfer files to or from the external drive.
    Mine is a new issue since the latest iTunes update. Apple refuses to give phone support and does not answer email event reports.

  • How to mount USB & CDROM drives from single user mode - Solaris boot disk?

    Hi All,
    I need to carry out ufsrestore on a single newly replaced system disk (no redundancy / mirroring) from either USB or CDROM drives from the following steps:
    ( i ) GRUB => e, e, cdrom –s, Enter, b (boot from Solaris 10 x86 media).
    ( ii ) Choose menu 1 for Install Solaris Interactive Mode to reach single user mode.Below are the commands that I have tried in single user mode without success:
    mount –r –F pcfs /dev/dsk/c1t0d0p0 /cdrom (after unmount Solaris CD)
      mount: /dev/dsk/c1t0d0p0 is not a DOS filesystem.
    svcadm –v enable smserver
      svcadm: Pattern ‘smserver’ doesn’t match any instances
    svcadm enable autofs
      svcadm: Pattern ‘autofs’ doesn’t match any instances
    devfsadm
      devfsadm: mkdir failed for /dev 0s1ed: Read-only file system
    mkdir /mnt
      mkdir: Failed to make directory “/mnt”; Read-only file systemPart of the problem is due to the current READ ONLY filesystems which does not allow the creation of mount point such as /mnt.
    I have been able to create both / root (/dev/dsk/c1t0d0s0) and /export/home (/dev/dsk/c1t0d0s0) filesystems with newfs that are awaiting for restore using ufsrestore.
    The only option I am left with is to attach a secondary disk to install Solaris 10 on either of them before bring the system to multi-user mode so that service such as volmgt, autofs, volfs are available to access USB & CDROM drives.
    Any suggestion on how to resolve this issue?
    Many thanks,
    Jack

    Hi JKGN,
    Is the directory a located under the root filesystem. ie /a? Are there any other mount point for say USB drive as well? I am not in a position to try it out right now but will get back
    to you soon on whether /a exist or not.
    Btw, the last thing I managed to do on this system at the time was added a secondary 1TB internal disk with the intention to restore both / and /export/home data onto this disk while
    making use of all the disk device management services such as the following services only available in a fully installed Solaris system (both single & multi-user modes) installed on the
    primary disk:
    # svcs smserver
    STATE          STIME    FMRI
    online         Jun_08   svc:/network/rpc/smserver:default
    # svcs autofs
    STATE          STIME    FMRI
    online         Jun_08   svc:/system/filesystem/autofs:default
    # devfsadm
    # iostat -En
    c1t0d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
    Vendor: ATA      Product: SAMSUNG HD321KJ  Revision: 0-11 Serial No: 
    Size: 320.07GB <320072932864 bytes>
    Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
    Illegal Request: 41 Predictive Failure Analysis: 0
    c0t0d0           Soft Errors: 0 Hard Errors: 5 Transport Errors: 0
    Vendor: PHILIPS  Product: DVD+-RW DVD8801  Revision: AD21 Serial 
    Size: 17.54GB <17538875392 bytes>
    Media Error: 0 Device Not Ready: 5 No Device: 0 Recoverable: 0
    Illegal Request: 10 Predictive Failure Analysis: 0
    c2t0d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
    Vendor: JetFlash Product: Transcend 16GB   Revision: 1100 Serial No: 
    Size: 0.00GB <0 bytes>
    Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
    Illegal Request: 7 Predictive Failure Analysis: 0
    # rmformat
    Looking for devices...
         1. Volmgt Node: /vol/dev/aliases/cdrom0
            Logical Node: /dev/rdsk/c0t0d0s2
            Physical Node: /pci@0,0/pci-ide@1f,1/ide@0/sd@0,0
            Connected Device: PHILIPS  DVD+-RW DVD8801  AD21
            Device Type: DVD Reader/WriterHowever, I was disappointed that "iostat -En" has not found the secondary disk (1 TB) even though it was available earlier, for Solaris installation as the only disk on the same system.
    As a result, I am left with no option but the need to rebuild this system with only a single primary disk while in single user mode. However, the single user mode that I am in is the
    one from Solaris installation disk with restrictive (_cannot create folder for mount point or running disk management utilities_) capability such as those services just covered, compared to one from a completed Solaris installation system with full access to all filesystems and utilities / commands in general.
    I would very much value your assistance on how to mount both CD & USB in this restrictive limited Read Only OS (assume that it is running from memory) in order to get complete access to
    the blank primary disk so that full restore with ufsrestore could take place.
    Thanks in advance,
    Jack
    Edited by: 797805 on 9/06/2012 04:15

  • Mounting and Unmounting USB drives [Solved]

    HI there:
    I want a program like in KDE that will automaticly mount and allow me to click to unmount my usb drives. I am building machines and I need them to be user friendly and fast. I am running openbox 3.5 with a lxpanel right now. Also how do you allow users to access the usb drives. Here is an example of an error. I am logged in as usera. I fire up shotwell plug in my camera. It detects it I click on the camera and it says
    "Shotwell
    Unable to fetch previews from the camera:
    I/O problem (-7)"
    I log in as root it works perfectly. I hope this all makes sense.
    Last edited by mich04 (2011-10-27 23:36:30)

    AliWam wrote:
    How do you start openbox?
    I am using startx with this ~/.xinitrc
    exec ck-launch-session dbus-launch openbox-session
    and it works well.
    Have a look here.
    Nice!  I just installed Xfce on my new netbook (I use awesome WM and a different automounting solution for my other Arch box) and adding "dbus-launch" right before "startxfce4" on the line that reads:
    "exec ck-launch-session dbus-launch startxfce4"
    fixed my problem.
    I'm a little confused though, in the wiki it says that, "In case you are wondering, dbus-launch will be launched by the xinitrc.d code at the beginning of the file...."  https://wiki.archlinux.org/index.php/Xfce
    My .xinitrc is functionally the same as the example in the wiki, so I had thought that somehow dbus-launch wouldn't be necessary.  Oh well, it's working now and that's all that matters, thanks for your suggestion AliWam!

  • How to stop importing from usb drive going into root ITMS directory

    First time I imported, everything was fine. I was trying to get rid of some duplicates and got rid of one of the main subdirectories (I had "Itunes Music" folder with two main subdirectories, let's call them "Laptop" and "Desktop." I noticed I had many duplicate artists from these, so I deleted the "Laptop" directory. Naturally, all these showed up with asterisks on iTunes. With no easy way to delete them all (can't sort based on asterisk, apparently), I removed EVERYTHING from my Library and attempted to copy over from the USB drive again. This time, the contents of "Laptop" went into the root "iTunes Music" folder (so there were now ~50+ folders including the "Desktop."
    This isn't working for me, since my objective is to get rid of the duplicate work (duplicate tracks I can somewhat stomach, but I also have some duplicate "Artists" which is driving me crazy). I removed everything from the library, deleting it all (~30+GB) and deleted all of the subdirectories from the iTunes Music folder.
    When I went to reimport it all again. I dragged the "Laptop" folder from Finder on the USB drive into the iTunes Music directory again (as I did the first time), recreated the and everything continues to populate the top iTunes music folder. Is there any way to stop this? I want the "Laptop" folder to stay in it's subdirectory structure distinct and separate from the "Desktop" folder so I can ensure I am not unnecessarily increasing my structure.
    One easy (though extremely tedious) alternative could be to import the folders one at a time... but I'd really like to avoid that. But for my first mistake, this wouldn't have been an issue. I haven't changed any settings on iTunes, so please advise!

    I have duplicate (different) stuff on the laptop versus desktop but some unique to each (and all kinda scrambled up). I first started importing on my old G3 ibook. It was slower and chugged harder and some are at really low bitrate, for example, and also lack album art. My XP desktop was made for gaming and is much more powerful, so I always did high bitrate and was much more careful to do all the album art, etc.
    Now I'm trying to consolidate it all on my new MBP... Mostly, though, it's a mess and I've been putting this off for years and it's mostly my fault. My biggest gripe is the large number of duplicate tracks. I can live with these when they're from different albums (compilations mostly), but not when one is a lower bit. I imagine I'm gonna be doing it the hard way, one album/artist at a time...

  • Single-user mode: How to mount and access an external USB drive?

    My MacBook Pro HD is acting up. Cannot boot normally or into "safe mode". Cannot reinstall OS without wiping out the HD. Need to recover some critical files but DiskUtil First Aid and Restore options cannot successfully complete. Problem traced down to "invalid node structure" which means I either have a hardware problem or my filesystem partition directory structure is corrupted. I need to recover some files that are not backed up (timin issue with my regular backup process).
    I can boot into single-user mode, mount the root file system (/sbin/mount -uw /) and can see/navigate the rot filesystem structure via good UNIX command line. Here's what I would like to do (in single-user mode):
    1. Mount an external USB drive (250 GB already formatted as Mac OS X Extended)
    2. Copy various files and/or directories from my HD to the external USB drive (UNIX cp command)
    I realize I could go spend $$ for the Disk Warrior or Data Rescue products (or something similar) that SHOULD help me recover my HD or files, but it seems silly to do this when I can see, touch and taste them from within single-user mode....
    Comments? Suggestions?
    TIA --
    Trent
    P.S. Once I've recovered my files, I'll try to reformat the HD and then reinstall the OS. And THEN go have Apple look at my machine (thank goodness for AppleCare coverage)!

    Resolution:
    1) Boot system in single-user mode (SUM) with external HD attached.
    2) Execute the following UNIX CLI commands once SUM boot process is completed:
    # fsck -fy
    # mount -uw /
    # mkdir /Volumes/target_directory
    # mount -t hfs -w /dev/diskXXX /Volumes/target_directory
    # cp -RXv /source_directory /Volumes/target_directory
    Where XXX is the device-level name for your external HD's data partition. In my case this was /dev/disk1s2. It may take some experimentation to identify this device name if your system has multiple HD's.
    3) Verify contents were successfully copied onto the /Volumes/target_directory.
    Comments and observations:
    - Do NOT use "/" as your source directory - cp will make a second (redundant) copy of /volumes/target_directory
    - I was able to successfully copy ALL files off my HD despite the fsck command's "invalid node structure" error message with this simple procedure. YMMV, depending on the state of your HD.
    - The repeated disk0s2: I/O error warnings displayed during the SUM boot process did not seem to have a negative effect on this procedure. I also received this same error warning intermittently as I navigated the mounted filesystem did not seem to be a problem, either. Again, YMMV.
    Commercial software:
    I downloaded ProSoft Engineering's Data Rescue 3 product (trial version) before spending $99 to attempt to recover my "bad" HD's data via mounting to a good system with FW target mode. It could not successfully complete its "QuickScan" process and immediately hung on block 0 of 390M during its "Deep Scan" process. The product did seem to function properly on an operational system. ProSoft's technical support was responsive and helpful but had no answer for my "Deep Scan" error.
    I did not attempt to use Alsoft's Disk Warrior 4 product. I could not find any trial software available and was reluctant to spend $100 based upon the mixed reviews and comments on this discussion forum as well as other reviews. Alsoft does claim to address the "invalid node structure" error in their marketing materials. Hindsight being 20/20 - I saved $100 by using this simple procedure.
    Final note:
    Neither Leopard nor Snow Leopard's installation DVD could recognize the bad internal HD when trying to do a reinstall. While DiskUtil was able to "see" the bad internal drive it immediately failed when I tried to do an "erase and format". Took the system to my local Apple store and the Genius ran a tool called "SMART Utility" from Volitans Software (www.volitans-software.com). SMART utility confirmed that my HD was bad so it was replaced. AppleCare pays for itself (once again!).

  • All USB drives mount as read only for user

    I have searched a bunch and thee results I find seem to be irrelevant to my situation. Most relate to a single USB media that is a problem and won't read or write.
    On a new Arch install on a new computer (my third base system install). Running Gnome.
    All USB mass storage devices mount as read only for the logged in user. Root has write permissions and I can mkdir no problem. It is not an issue with the USB drive itself as this occurs with multiple USB media (I've tested several SD cards on a reader and at least two drives, all the media works correctly on my existing installations)
    I'm posting the contents of my /etc/group file in case there's an obvious error there I don't see, and my dmesg output upon plugging in the drive. User name is changed in the group file posted to "archie"
    This is a single-user system.
    /ect/group
    root:x:0:root
    bin:x:1:root,bin,daemon
    daemon:x:2:root,bin,daemon
    sys:x:3:root,bin
    adm:x:4:root,daemon
    tty:x:5:
    disk:x:6:root
    lp:x:7:daemon
    mem:x:8:
    kmem:x:9:
    wheel:x:10:root,archie
    ftp:x:11:
    mail:x:12:
    uucp:x:14:archie
    log:x:19:root
    utmp:x:20:
    locate:x:21:
    rfkill:x:24:
    smmsp:x:25:
    http:x:33:
    games:x:50:
    lock:x:54:
    uuidd:x:68:
    dbus:x:81:
    network:x:90:
    video:x:91:
    audio:x:92:
    optical:x:93:
    floppy:x:94:
    storage:x:95:
    scanner:x:96:
    power:x:98:
    nobody:x:99:
    users:x:100:archie
    systemd-journal:x:190:
    archie:x:1000:
    avahi:x:84:
    polkitd:x:102:
    rtkit:x:133:
    gdm:x:120:
    brlapi:x:999:
    kvm:x:78:
    ntp:x:87:archie
    dmesg output
    [ 968.044188] usb 4-3: new high-speed USB device number 4 using ehci-pci
    [ 968.170628] usb-storage 4-3:1.0: USB Mass Storage device detected
    [ 968.171435] scsi7 : usb-storage 4-3:1.0
    [ 969.174450] scsi 7:0:0:0: Direct-Access Generic USB SD Reader 1.00 PQ: 0 ANSI: 0
    [ 969.175068] scsi 7:0:0:1: Direct-Access Generic USB MS Reader 1.03 PQ: 0 ANSI: 0
    [ 969.939417] sd 7:0:0:0: [sdb] 15572992 512-byte logical blocks: (7.97 GB/7.42 GiB)
    [ 969.941028] sd 7:0:0:0: [sdb] Write Protect is off
    [ 969.941037] sd 7:0:0:0: [sdb] Mode Sense: 03 00 00 00
    [ 969.944664] sd 7:0:0:1: [sdc] Attached SCSI removable disk
    [ 969.945509] sd 7:0:0:0: [sdb] No Caching mode page found
    [ 969.945517] sd 7:0:0:0: [sdb] Assuming drive cache: write through
    [ 969.952682] sd 7:0:0:0: [sdb] No Caching mode page found
    [ 969.952693] sd 7:0:0:0: [sdb] Assuming drive cache: write through
    [ 969.956396] sdb: sdb1
    [ 969.965003] sd 7:0:0:0: [sdb] No Caching mode page found
    [ 969.965011] sd 7:0:0:0: [sdb] Assuming drive cache: write through
    [ 969.965015] sd 7:0:0:0: [sdb] Attached SCSI removable disk
    I'm sure I'm just missing something in user management, but I can't find what.
    Last edited by hooya (2014-04-27 03:10:49)

    I am also having the same problem. Root can read and write to automounted drives, but my user cannot. I've tried with a variety of drives, I am assuming they are being automounted by root instead of the logged-in user somehow. (I am running x directly, and am not using a display manager, if that has anything to do with it).
    When I look at how it is mounted it is as follows:
    /dev/sdc1 on /run/media/myuser/drivename type vfat (rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2)

  • Problem with USB drive not writing/freezing on unmount.

    I have a sandisk cruzer blade USB drive, which I have used for the past hours extensively. At one point, I couldn't manage to write data to it. It acted like it had, but it didn't, as it silently remounted as readonly. I solved this by remounting as rw and retried.
    Now, when using the same drive, after writing around 2 GiB worth of data to it (creating files), and attempting to unmount, the unmount command freezes for a long period of time. I check dmesg and it says its frozen. So I open up another tab to try and rescue the writes I made by typing sync. This also freezes and generates dmesg messages.
    As I'm typing this the commands seemed to have succeeded, but I'm wondering, what causes these problems? Is the problem known?
    dmesg output:
    [ 1440.339510] INFO: task umount:1540 blocked for more than 120 seconds.
    [ 1440.339518] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    [ 1440.339523] umount D ffff88021da81950 0 1540 1539 0x00000004
    [ 1440.339531] ffff8801d9ad7c70 0000000000000082 0000000000014500 ffff8801d9ad7fd8
    [ 1440.339538] ffff8801d9ad7fd8 0000000000014500 ffff88021da81950 ffff88022ec94500
    [ 1440.339545] ffff8801d9ad7bc0 ffffffff81091995 ffff88022211c380 0000000000000002
    [ 1440.339551] Call Trace:
    [ 1440.339565] [<ffffffff81091995>] ? check_preempt_curr+0x85/0xa0
    [ 1440.339571] [<ffffffff8108ecfa>] ? ttwu_stat+0x9a/0x110
    [ 1440.339579] [<ffffffff81093a0c>] ? try_to_wake_up+0x1fc/0x2c0
    [ 1440.339586] [<ffffffff814e1029>] schedule+0x29/0x70
    [ 1440.339593] [<ffffffff814dd909>] schedule_timeout+0x219/0x290
    [ 1440.339599] [<ffffffff8107b746>] ? __queue_work+0x136/0x390
    [ 1440.339606] [<ffffffff814e03c3>] wait_for_common+0xd3/0x180
    [ 1440.339612] [<ffffffff81093b10>] ? wake_up_process+0x40/0x40
    [ 1440.339617] [<ffffffff814e048d>] wait_for_completion+0x1d/0x20
    [ 1440.339625] [<ffffffff811c8bd0>] writeback_inodes_sb_nr+0x80/0xb0
    [ 1440.339648] [<ffffffff811c8c25>] writeback_inodes_sb+0x25/0x30
    [ 1440.339655] [<ffffffff811cdedd>] sync_filesystem+0x2d/0xa0
    [ 1440.339662] [<ffffffff811a1cb0>] generic_shutdown_super+0x30/0xe0
    [ 1440.339668] [<ffffffff811a1f97>] kill_block_super+0x27/0x70
    [ 1440.339678] [<ffffffff811a22fd>] deactivate_locked_super+0x3d/0x60
    [ 1440.339684] [<ffffffff811a28e6>] deactivate_super+0x46/0x60
    [ 1440.339689] [<ffffffff811bdeaf>] mntput_no_expire+0xef/0x150
    [ 1440.339695] [<ffffffff811bf0b1>] SyS_umount+0x91/0x3b0
    [ 1440.339701] [<ffffffff814ea5dd>] system_call_fastpath+0x1a/0x1f
    [ 1560.250364] INFO: task umount:1540 blocked for more than 120 seconds.
    [ 1560.250371] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    [ 1560.250375] umount D ffff88021da81950 0 1540 1539 0x00000004
    [ 1560.250383] ffff8801d9ad7c70 0000000000000082 0000000000014500 ffff8801d9ad7fd8
    [ 1560.250390] ffff8801d9ad7fd8 0000000000014500 ffff88021da81950 ffff88022ec94500
    [ 1560.250397] ffff8801d9ad7bc0 ffffffff81091995 ffff88022211c380 0000000000000002
    [ 1560.250403] Call Trace:
    [ 1560.250416] [<ffffffff81091995>] ? check_preempt_curr+0x85/0xa0
    [ 1560.250422] [<ffffffff8108ecfa>] ? ttwu_stat+0x9a/0x110
    [ 1560.250429] [<ffffffff81093a0c>] ? try_to_wake_up+0x1fc/0x2c0
    [ 1560.250435] [<ffffffff814e1029>] schedule+0x29/0x70
    [ 1560.250442] [<ffffffff814dd909>] schedule_timeout+0x219/0x290
    [ 1560.250448] [<ffffffff8107b746>] ? __queue_work+0x136/0x390
    [ 1560.250454] [<ffffffff814e03c3>] wait_for_common+0xd3/0x180
    [ 1560.250460] [<ffffffff81093b10>] ? wake_up_process+0x40/0x40
    [ 1560.250465] [<ffffffff814e048d>] wait_for_completion+0x1d/0x20
    [ 1560.250473] [<ffffffff811c8bd0>] writeback_inodes_sb_nr+0x80/0xb0
    [ 1560.250493] [<ffffffff811c8c25>] writeback_inodes_sb+0x25/0x30
    [ 1560.250499] [<ffffffff811cdedd>] sync_filesystem+0x2d/0xa0
    [ 1560.250506] [<ffffffff811a1cb0>] generic_shutdown_super+0x30/0xe0
    [ 1560.250513] [<ffffffff811a1f97>] kill_block_super+0x27/0x70
    [ 1560.250522] [<ffffffff811a22fd>] deactivate_locked_super+0x3d/0x60
    [ 1560.250528] [<ffffffff811a28e6>] deactivate_super+0x46/0x60
    [ 1560.250533] [<ffffffff811bdeaf>] mntput_no_expire+0xef/0x150
    [ 1560.250538] [<ffffffff811bf0b1>] SyS_umount+0x91/0x3b0
    [ 1560.250545] [<ffffffff814ea5dd>] system_call_fastpath+0x1a/0x1f
    [ 1560.250550] INFO: task sync:1547 blocked for more than 120 seconds.
    [ 1560.250553] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    [ 1560.250556] sync D ffffffff811cdd00 0 1547 985 0x00000000
    [ 1560.250561] ffff8801be2e1e68 0000000000000086 0000000000014500 ffff8801be2e1fd8
    [ 1560.250567] ffff8801be2e1fd8 0000000000014500 ffff8801c1335460 ffff8801be2e1e70
    [ 1560.250573] ffffffff811326ab ffff8801be2e1de0 ffff88020bdbc280 0000000000000080
    [ 1560.250579] Call Trace:
    [ 1560.250586] [<ffffffff811326ab>] ? filemap_fdatawait_range+0x17b/0x1a0
    [ 1560.250594] [<ffffffff811cdd00>] ? generic_write_sync+0x60/0x60
    [ 1560.250599] [<ffffffff814e1029>] schedule+0x29/0x70
    [ 1560.250604] [<ffffffff814e1d85>] rwsem_down_read_failed+0xc5/0x120
    [ 1560.250610] [<ffffffff81292744>] call_rwsem_down_read_failed+0x14/0x30
    [ 1560.250616] [<ffffffff814dffa7>] ? down_read+0x17/0x20
    [ 1560.250620] [<ffffffff811a34cc>] iterate_supers+0x9c/0x110
    [ 1560.250628] [<ffffffff811cdf85>] sys_sync+0x35/0x90
    [ 1560.250633] [<ffffffff814ea5dd>] system_call_fastpath+0x1a/0x1f

    mr.MikyMaus wrote:You do know that flash memories have limited number of write cycles, right?
    Limited how? Like all storage devices have (in other words, after a while they break)?
    The drive is completely new, like 3 weeks or something.

Maybe you are looking for