Random NFS/CIFS drive mounting on boot

Hello, can someone please give me some insight as to where this drive is coming from? Everytime I restart my machine a CIFS drive mounts on my desktop and I cannot figure out where it is coming from, or how to prevent it from mounting. In the screenshot you will see that it says the server is an NFS://x-browser? What the heck is this? Any help would be appreciated.

Linc, Holding down command key does not work. Thanks for the suggestion.
Gerry, Parallels does not boot upon start-up. It only runs when I launch.
Interesting side-note: The desktop shows a CIFS drive, the sidebar shows it listed under shared and calls it "x-browser", and finally the finder shows "connected as: NFS"
Whoa, I hope that last bit makes sense.

Similar Messages

Solaris 10/08 w/ ZFS rpool NFS doesn't mount at boot time?

I've got an issue with NFS not mounting vfstab entered mounts during boot and was wondering if the latest Sol 10/08 with ZFS had anything to do with it.
1) #vi /etc/vfstab
server:/vol/share - /share nfs - yes rw,bg,hard,nointr,rsize=32768,wsize=32768,noac,vers=3,timeo=600
server2:/vol/share2 - /share2 nfs - yes rw,bg,hard,nointr,rsize=32768,wsize=32768,noac,vers=3,timeo=600
2) reboot -- -rv
Upon rebooting, the shares do not show up, but doing a mountall mounts them finally:
#mountall
mount: /tmp is already mounted or swap is busy
3) Doing a df -k at this point shows me they mounted.
So what gives? Why are they not mounting at boot? I tried to get around it by doing removing the vfstab entries, adding them into auto_master and then using cachefs, but my employer was not satisfied with autofs and wants them at boot and persistent via the vfstab. So what can be done to get this to work?
Thank you,
--tom

It appears I didn't have all of the services set online correctly:
#svcs |grep nfs
online Jan_05 svc:/network/nfs/status:default
online Jan_05 svc:/network/nfs/nlockmgr:default
So, I enabled the following:
#svcadm enable nfs/mapid
#svcadm enable nfs/cbd
#svcadm enable nfs/client
#scvs |grep nfs
Checked again:
#svcs |grep nfs
online Jan_05 svc:/network/nfs/status:default
online Jan_05 svc:/network/nfs/nlockmgr:default
online 15:48:24 svc:/network/nfs/mapid:default
online 15:48:33 svc:/network/nfs/cbd:default
online 15:48:42 svc:/network/nfs/client:default
Tested to make sure no errors were reported:
# svcs -xv
Then rebooted again.
Voila! It worked! Sometimes reading the documents on docs.sun.com pay off. I was just being too lazy to do it and gave up when I posted this. The solution is to check the services and ensure nfs/client is running correctly and then try rebooting again.

[SOLVED] NFS share not mounting at boot

Hi All,
I have an NFS share listed in fstab and it doesn't mount at boot; however, when i mount -a, it mounts fine. Any thoughts?
Thanks.
Shawn
Last edited by shawn.abdushakur (2011-05-06 12:21:27)

@damnshock: Good point . Here it is:
# /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 swap swap defaults 0 0
LABEL=arch / ext4 defaults 0 1
UUID=c1a8b2e0-bf9e-4382-ac4e-15c2aec65090 /srv/nfs ext3 defaults 0 0
/srv/nfs/shawn/Documents /home/shawn/Documents none bind
/srv/nfs/shawn/Downloads /home/shawn/Downloads none bind
/srv/nfs/shawn/Music /home/shawn/Music none bind
/srv/nfs/shawn/Pictures /home/shawn/Pictures none bind
/srv/nfs/shawn/Videos /home/shawn/Videos none bind
xbmc:/srv/nfs/watch /home/shawn/Downloads/torrents/watch nfs rsize=8192,wsize=8192,timeo=14,intr

External drive does not mount on boot

I have a Toshiba MK5055GSX 500GB external drive which I use for Time Machine but for some reason it does not automatically mount from a cold boot. Before I started to use it for Time Machine (it was formatted as NTFS at the time) I had not problems with it. All other external drives correctly mount on boot.
I had thought it might be a problem with the drive itself but if I disconnect it and reconnect it with my iMac running it mounts every time without fail. If I reboot after it has mounted it also mounts at boot. Only if I start the iMac using the power button with the drive already connected does it fail to mount and the results are consistently repeatable.
Does anyone have any ideas why this might be happening and how to fix it?

Does this drive have a separate power brick? If it does I suggest using it to see if that fixes the problem. If the enclosure has both USB and Firewire ports try using the drive on a Firewire port instead of a USB port.
It sounds like the drive is not spinning up early enough in the startup process to be detected.
Not knowing how you prepared the drive for the Mac, you should re-prep the drive as follows:
Extended Hard Drive Preparation
1. Open Disk Utility in your Utilities folder.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (for Intel Macs) or APM (for PPC Macs) then click on the OK button. Click on the Partition button and wait until the process has completed.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.

NFS mount on boot failing after systemd upgrade

Hello,
after upgrading systemd (208-2 --> 208-3), nfs mount on boot will fail. Tested multiple times. After downgrading back to 208-2, all worked fine.
Output of journalctl --reverse:
Dependency failed for Remote File Systems.
Dependency failed for /mnt/demeter.
Dependency failed for File System Check on /192.168.20.70:/data.
Timed out waiting for device 192.168.20.70:-data.device.
/etc/fstab, the nfs line:
192.168.20.70:/data/ /mnt/demeter nfs4 defaults 0 5
uname -a:
Linux eros 3.12.5-1-ARCH #1 SMP PREEMPT Thu Dec 12 12:57:31 CET 2013 x86_64 GNU/Linux
I'm using the latest packages (expect grub, it's the version before the current, because of huge ugrade problems, too).
Greetings,
Sebastian

Ah, big thanks. I thought the last column is the mount order, because it's called "pass". I changed it to zero, and now it works.
Greetings,
Sebastian

My G RAID thunderbolt drive mounted just fine onto my iMac this morning. And now it will not mount despite my various efforts. I don't know what else to do. Can someone help me with this?

My G RAID thunderbolt drive mounted just fine onto my iMac this morning. I copied some files from another drive onto the RAID drive, ejected it, and worked on another project for a few hours. When I went to mount the RAID drive again so I could work on the project associated with the drive (I'm a freelance video editor) it would not mount. I've tried everything. It boots up perfectly fine, the drive seems to have no hardware problems. It shows up on Disk Utility and in System Information but is listed as not mounted. I've verified it on Disk Utility and it tells me everything with the drive is fine. I've tried all the various restarting my iMac, ejecting and reconnecting the drive, shutting down the whole system and starting it back up, relaunching Finder, and nothing works. Starting to panic because this is a client's drive, I have no idea what the issue is, it worked perfectly fine only hours ago, nothing happened to it in the meantime, and I fear continuously connecting and ejecting it because I don't know what the state is with the data and if this is only going to further aggravate the problem. I've been up and down Apple and g-raid forums and can't get a straight answer anywhere. I need to know that the data is safe, the drive is undamaged, and how to get it to mount on my iMac. Can anyone out there help me with this??

welcome to the BT community forum where customers help customers and only BT employees are the forum mods
in order for the forum members to help please can you post the adsl stats from your router you may need to 'show detail' to get all stats (if hub enter 192.168.1.254 in your browser and navigate to adsl or if HH4/5 then go to troubleshooting then logs and you are looking for 2 line together when hub last connected to internet and they will show your connection speed and noise margin or if netgear enter 192.168.0.1). Then run btspeedtester (MAC users may have problems). when first test completes then run diagnostic test and post the results ( do not reset the router).
Have you tried the quiet line test? - dial 17070 option 2 - should hear nothing - best done with a corded phone. if cordless phone you may hear a 'dull hum' which is normal
Someone may then be able to offer help/assistance/suggestions to your problem
If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post.
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

External HDD won't mount at boot. [Solved]

Edit:
I've noticed that this is an issue regarding my NTFS partition being on an external drive. Please check post #8 by me to get further details.
Hello guys, I'm having some problems getting my external NTFS HDD to mount automatically at boot. I have installed HAL and NTFS-3G, but I'm still getting problems. Mounting once the computer has finished booting is no problem using the simple mount command (sudo mount /media/pebble). I see no reason why this should be having problems mounting at boot with my fstab entry, but no errors occur when mounting manually.
Fstab entry:
/dev/sdc1 /media/pebble ntfs-3g fmask=022 1 0
rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="America/Vancouver"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(fuse)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="r3-desktop-arch"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
#eth0="dhcp"
eth0="eth0 192.168.0.23 netmask 255.255.255.0 broadcast 192.168.0.255"
INTERFACES=(eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng network netfs crond dbus hal alsa)
Do I need to load HAL earlier? What am I doing wrong?
Last edited by ryeguy146 (2009-11-05 10:04:32)

I just noticed something, I don't think that this is an issue with the partition being NTFS, but rather with it being on an external hard drive (/dev/sdc). I say this because I just rebooted and noticed another NTFS partition that I have in my fstab is mounting (/dev/sda5). It's an internal HDD, and I didn't notice that it mounted up because I rarely use it. But there it is.
I suppose that I should define /dev/sdc. It is a Western Digital External HDD running off of a USB 2.0 cable. I don't know why this makes a difference, but it apparently does. Both entries in the fstab are identical for their respective devices and mount points.
Now that we have that figured out, I think that I'll change the title of the thread. So any ideas on how to solve this one?

External drives mount as read only

I am running OS X 10.6, on a MacPro. Something happened recently to make my external hard drives mount as read only. The only way I've found to be able to fix them is to run Disk Utility every time I start up my computer. Does anyone have an solution to this?
Also every time I run the Disk Utility, at the end of the repairs it says "Updating boot support partitions for the volume as required." I do not know if this is related, but I haven't been able to find anything relevant in relation to my problem with the drives mounting as read only.
Message was edited by: HeatherK

You might give this a try:
Select the drive and Press COMMAND-I to open the Get Info window. At the bottom open the Ownership and Sharing section. Be sure the box labeled "Ignore permissions on this volume" is unchecked. If it is checked then click on the lock icon, authenticate, then uncheck that box. Close the window.
Open the Terminal application in your Utilities folder and at the prompt enter or paste the following:
sudo chown root:admin
Put a space after "admin" then drag the drive's icon into the Terminal window. Press RETURN. You will be prompted to enter your admin password which will not be echoed.
See if this fixes the problem.

[Solved]IDE Drive mounting problem.

Hey all, I've got an annoying problem with one of my IDE drives.
Basically I just can't get it to mount, during boot up I get a few errors:
end_request: I/O error, dev sda, sector 0
Buffer I/O error on device sda, logical block 0
ata2: EH complete
unable to read partition table
Corrupt partition table, simple enough? I wish. I can mount the drive without error in both my Windows and Ubuntu 7.10 install. Which leads me to think it dislikes using the PATA driver or whatever the change was in later kernels.
The really puzzling part is that I can wipe the drive and create a new partition with parted, then mount it manually and copy data to it. But as soon as I reboot I am back the start, getting I/O errors and can't mount.
A couple of guys on IRC were saying to rmmod the pata drivers and modprobe the ide ones, but I have no experience with either of those functions. And from what I can see there is like 15 different IDE drives I could choose from, so have no idea what I should be doing.
Any help is appreciated.
Last edited by BluntBox (2008-05-02 06:27:42)

Well as insane as this seems to me, removing the jumper on drive and making it cable select fixed it...

"Drive not properly ejected"--How do I keep a USB drive mounted constantly?

I have a 2-month-old iMac, and have had a USB external SATA-enclosure 2.5" 500gb drive attached the whole time. About a week ago, it started randomly giving the "Drive not properly ejected" message and usually it remounts after a few seconds. Sometimes it doesn't and I have to unplug it and plug it back in.
I thought the drive was at fault, so I switched it with a similar drive that was connected to my AirPort Extreme base station. The problem stayed with the Mac. Also I imagined that (somehow) the iMac wasn't supplying enough power, so I bought a powered USB hub. The result is the same.
I don't understand how it can work for two months and then suddenly get this problem. The only change along the line is that about a week ago I did a software update ("About this Mac" says it is 10.6.7). The latest update DOES coincide with the appearance of this problem.
How do I resolve this?
(Notes: There at least one other thread here where people seem to think that this is a Time Machine problem. I think this is because many people connect large external drives for the purpose of backup. I upgraded to iMac from Mac Mini. I installed Snow Leopard right after I bought the iMac and then tried to restore from my Time Machine backup. Something went wrong, so I mirrored my Mac Mini drive onto a 500gb SATA 2.5", put it in a FireWire enclosure and boot from that. I use the iMac's internal 1T drive for Time Machine. That may sound like "lazy man solution", but it could have a great advantage someday where I could plug that FireWire drive into my Mac Mini and not have any downtime should iMac need to be repaired. The random disconnecting of the USB drive doesn't coincide with any Time Machine events. TM is working fine.)

Kappy,
Thank you for your help with this problem!
Your hypothesis for the drive/enclosure being a problem is good thinking, however:
-The problem never existed for the first two months I had the iMac.
-I can switch similar drives with iMac and AirPort Extreme, and the problem stays with the iMac.
-It has nothing to do with Time Machine as I am using a FireWire drive to boot, and the iMac internal 1TB for Time Machine.
-A friend suggested a cable problem, but I have tried many combinations and it wouldn't explain why suddenly after 2 months three sets of USB cables can fail at the same time (at least one, I used for 3 years with Mac Mini.)
I now have a 111gb drive connected to my AirPort Extreme and it has been copying files to my FireWire drive slowly but surely for two hours now. The same drive disconnected after 13 minutes on the iMac. All indications are pointing to OSX 10.6.7. The perfect test (for anyone with convenient resources) would be to install Snow Leopard from disc on a clean Mac and not upgrade it, plug in a USB drive and see if it can last a day or two. Then, upgrade to 10.6.7 and see what happens. I hope someone can try this.
(Is this a ploy to try to sell more FireWire equipment? I hope not.)

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

Driver Signing for Boot Images - 2008r2 Site Server

I was trying to update a driver in our boot image due to instability in the previous version. This new driver officially supports Server 2012 R2 (as well as 2012, in a single driver) and is digitally signed.
However, the certificate is not recognized by our Site Server which runs on 2008r2 (because it is a 2012 driver), and DISM.log is flagging the driver as Unsigned, and I cannot update the boot image - it fails every time.
I'm able to work around this by injecting it myself with /forceunsigned, but it doesn't seem to be the "correct" way of handling this. I can also do the mount and driver add on my 8.1 workstation, and not need /forceunsigned (thus proving
it IS signed.)
While it's flagging almost every other driver as unsigned (which is incorrect) - those other drivers aren't deemed "boot-critical", so it allows them.
This one is a SCSI driver, hence it blocking it.
Signature status of driver \\SCCMServer\ConfigMgrDrivers\Server 2012\SCSIAdapter\hpsa2_62.8.0.64\hpsa2.inf is: UNSIGNED - CDriverPackage::InitSignatureStatus
Cannot install non-signed boot-critical drivers on amd64 images. Use /forceunsigned switch to override. \\SCCMServer\ConfigMgrDrivers\Server 2012\SCSIAdapter\hpsa2_62.8.0.64\hpsa2.inf - CDriverManager::CheckClientAddDriverScenarios(hr:0x80070032)
For those of us who have our site servers on 2008r2, I'd call this a bug. Anyone else getting this? Is my workaround the supported solution for people not running site servers on Server 2012 / 2012 R2?

I had similar problem with one driver in the past. The way I 'fixed' my situation was that I manually injected the driver to .wim -image with DISM and then re-added the Boot Image to ConfigMgr 2012. The driver won't show up in the properties of the boot
image but I didn't really care, because I just wanted to get this thing working.

ATA drive won't boot alone-gray spinning startup screen. But will w/others

I'm troubleshooting a friends G4-PCI. And i can't get past a certain problem with the hard drives.
The hard drive (a 2003 80gb maxtor) doesn't want to boot.
But it will boot 10.4.11 if something else is in as well. So alone, i get only a flashing question mark. If another bootable hard drive in as well, the maxtor will boot. Same with a retail Tiger install disc.
This is the situation after all the things that i have tried which are these;
The initial problem was that it would crash if any real work was attempted. Then after a few powerbutton downs, the spinning 'watch' with gray apple screen at the beginning of the boot.
What i have done. Transfered all files onto a bootable drive, by first booting into the installer DVD in order to direct the subsequent boot to be on the good drive.
question 1) there is no 'option' boot in order to choose the volume, on the PCI, correct?
Once booted into the good drive, the maxtor mounts no problems.
Disk Utility. Disk Warrior. Still the Gray screen spinner. Fine.
Zeroed the drive. And super dupered the good drive (also a 80gb, 20% full) onto the maxtor. I figured if one copy boots, then the other will. After choosing the maxtor in system prefs, it booted fine. I then took my drive out. Then booted to test again, the maxtor alone. And again, the spinning gray apple startup menu that just keeps spinning.
Both drives were cable select and i tried both positions on the cable.
question 2) What did i miss?

You may have confused the G4 by not correctly setting the volume Jumpers to Master and Slave correctly. Look at the coonnection pins on the drives and you will see one of them has a small plasticlink which slides over two of the pins. That’s your Jumper. You may need tweezers to lift it off the pins. Your main Drive is served by the first of the two IDE cable connections, (the one closest to the Motherboard). Set that drive as Master. There should be a diagram on the HDD case to show which pins the jumper slides onto to create the Master. The second drive needs no jumper as it is the Slave volume. It sounds like you may have used your Slave as a start-up volume without transferring the Jumper onto that drive to make it a Master. Check it out. Good Luck.

Install: Error Message from mount, invalid boot interface"

Hi,
I'm booting into installation from CD1, and after the configuration assistant screen, I select the CD as the boot device, then get the error screen:
"Error Message from mount, invalid boot interface".
I've tried re-burning a new CD, but get the same error.
Any ideas to resolve this? Thanks in advance
Solaris 9 x86 12/02. AMD Duron 1300, EIDE CD Drive / 40Gb internal HD

Not up on my x86 here, and it has been a long time since I was installing from CD, but shouldn't your book device be the disk where you want the installation to go (in your case the presumable 2nd partition on your 40Gb disk).

Irregular flash drive mounting

Is there a USB equivalent to "SCSI Mounter" (from way back when) that lets you actively search for USB drives and mount them? I have an Adaptec Duoconnect Firewire+USB2 PCI card. I prefer to use this because of the USB2 capability. On occasion I have problems mounting flash drives with the card. I have two 1 GB flash drives, SanDisk Cruzer, and Imation. I have two cables plugged into two of the card's ports to allow me to plug in the drives from the front of the computer. Today after the computer had been asleep for a few hours I tried plugging in the drives after waking up the computer, and they would not mount (tried repeatedly plugging and unplugging). However, I plugged in one drive in the native USB port on the back of the computer and it did mount. I then tried the same drive in the cable and it still wouldn't mount. I restarted the computer and they both mounted in their cables. Sometimes the Imation drive won't mount in one of the cables but will in the other. After restarting today it would mount in the cable in which it usually won't. At first I wondered if it was a power supply issue, or cable resistance, but I changed nothing other than restarting the computer. As I said, this isn't the first time I have had problems with the Imation drive mounting, but I thought it might just be a problem with that drive on that cable (worn connectors). Now I'm thinking it is more a software issue. I can't say for sure if it's just a post-sleep thing, though I often leave my computer switched on 24/7 so I' usually using it in a post-sleep mode.
I don't see anything on Adaptec's website about Mac drivers so I don't think I can try that.
Brian

Actually, the drives are disconnected from the Mac when it goes to sleep (I already worked out that problem in another post). The real problem I had with leaving the drives plugged in was if I left the Imation drive plugged in and the computer went to sleep the computer would not wake again and I had to hard boot (restart button). I didn't seem to have this problem when I left the SanDisk drive plugged in, though of course the computer would give me a warning about the drive when I woke the computer.
This seems to be more a matter of maybe the card, or parts of it, not waking from sleep consistently. The card works with all drives in all ports when I first start up or reboot the computer. After it has been to sleep a few times the Imation drive has problems first. Last night was the first time I couldn't get either drive to work with the card until restarting, then both drives were recognized. I just started up my computer now and all drives work in all ports.

Random NFS/CIFS drive mounting on boot

Similar Messages

Maybe you are looking for