RAID Mounting in Thunar like a removable drive.

Hey everybody, i've just setup a RAID 10 and i really want it to display in thunar like my filesystem and removable drives do.
i've already mounted the raid /dev/md0 under a self created folder in /media but it does'nt show up.
the weird thing is if a program wants me to select a folder or something and pops up a filebrowser it does show, but i think it's a gtk thing it shows me.
does anybody have any ideas?
i'm on arch 64 running xfce4.6

gtkam while nice is overkill for my needs.
With help from another thread (https://bbs.archlinux.org/viewtopic.php … 3#p1035033)
Turns out Thunar will see the camera but not mount it through gvfs
I ended up having thunar run this script when it sees the camera was connected
#!/bin/bash
CAMPORT=`gphoto2 --auto-detect | grep '2000 IS' | cut -c 36- | sed 's/ //g'`
thunar "gphoto2://[usb:$CAMPORT]/"
gvfs-mount --unmount-scheme gphoto2

Similar Messages

  • Mount Digital Camera like a Hard Drive-HELP TONIGHT PLEASE

    I need to figure out how to make my digital camera mount on my desktop like a hard drive. I need to put Images ONTO my memory card, but when I hook up my (Kodak) camera, it always opens in either Image Capture or iPhoto, and only allows me to download images ONTO my computer. I need to put pictures ONTO my memory card. Please help!!!

    Digital Camera  Disks can be a problem getting mounted and/or accessed on a Mac. Windows has a proprietary system for integrating camera  disks but that system is not shared with Apple.
    Some cameras have a menu setup setting for disk usage. You might explore your camera's menu and look for a setting to tell it to "act like a data disk". Use the "Data Disk" option to bypass Microsoft's sabotage of your camera 
    You can name your camera 's disk so the "NO_NAME" part will be something like "Camera". To do this, select the camera  disk and press (at the same time) command key (AKA applekey) and the i key, which brings up the infowindow. You can rename your camera  disk there.
    Another cool trick is to assign your camera  a custom icon, I have mine set as a camera  which makes it easy to find on the Desktop.
    I suggest ignoring applications in both Mac and XP and copying your pictures directly in Finder. When it mounts the camera  disk, navigate to the pictures folder and drag it to your desktop and the entire folder will be copied. You can then open the folder in whatever application you want, I use GraphicConverter.

  • Auto-detect & mount disk partitions and removable drives

    I use ubuntu in addition to my current wip of installing arch linux.Now i have installed lxde desktop. But i am not able to see any of my partitions of my disk and other hdd. Besides removable drives also dont get mounted.
    Similarly if a new partition is created the same also gets autodetected in ubuntu. eg my arch linux partition. I need not go to do any fiddling in the system to recognize the same.
    So is it possible to achieve the same under archlinux?So want to know how to get  the same done.
    what i want is to have the partitions[ext & ntfs] detected when the filemanager is opened and mount/unmount at my will, just as i do now in ubuntu.
    So far what i have done is based on the lxde wiki, i installed the polkit-gnome gvfs package but nothing is mounted.
    i would like to have specific instructions to how to work out and get the above  done.
    pls guide to the same.
    Last edited by beopen (2012-08-12 12:55:15)

    cfr wrote :
    What do you mean when you say that pcmanfm is not displaying *any* partitions? You see no files at all? Or do you mean: it is not showing partitions not listed in /etc/fstab?
    I mean it is not showing partitions not listed in /etc/fstab. As of now pcmanfm shows only the arch systems partitions which I created while installation : root, and home. Balance of partitions of other systems of the same drive and second hard drive is not shown.
    When you say that in Ubuntu, newly created partitions show up automatically, do you mean that if you change the partitioning on your internal drive, the changes are automatically reflected in /etc/fstab?
    Yes the changes are automatically reflected in the filemanager of ubuntu, ie. Nautilius. However Ubuntu fstab as you see in the previous post of mine contains no entry to other partitions other than just ubuntus.In the fstab I posted above you can very well see it just shows 4 partitions of hdd1  [similar to the way the arch fstab shows only its own] where it is installed :boot,root,home, swap. Whereas there is two more partitions there viz windows and a ntfs. You don’t see them in fstab, but when you open the nautilius filemanager you can see the drives. See the image link of my filemanger posted below at the end. In that shared data and windows are two ntfs partition of hdd1 where ubuntu is installed. Arch is installed on 2nd hdd alongwith a Ubuntu.289gb partition is a ubuntu LVM along with arch root and arch home you can see.
    If you mean that Ubuntu automatically adds, mounts and unmounts partitions on removable drives when e.g. a USB stick is inserted or when you change the partitioning on one and create a file system, that you can configure to work automatically in arch.
    Yes ubuntu automatically adds, mounts and unmounts partitions on internal drives and also removable drives when e.g. a USB stick is inserted  . As you can see in the image i have posted, it shows all my internal drive partitions automatically. No fstab editing nothing. No fiddling with system files so far i have done in ubuntu. For eg i installed arch a month back, the same you can see is automatically seen in the image. All i required was to   update grub  to recognise árch'. Post that when you boot, automatically the new arch partitions are seen. No fstab fiddling anything. Thus tomorrow morning if i create a new partition on my hdd via ubuntu all i require is to reboot post the creation and i will see the new partition asap.
    As you can see in the image all my partitions are seen, the one i want i click it and it gets mounted, if i dont want it stays/gets unmounted. And its not just ubuntu i saw the same in some other distros also like suse,centos,fedora.
    As far as the lxde wiki is concerned, there it is mentioned to install polkit gnome gvfs for mounting and i did the same but nothing still happens.
    So this is what exactly i am asking how to do the same on my arch system. So if i am guided i wil go ahead and work to achieve the same.
    image link of file manager : NautiliusFileManager
    Last edited by beopen (2012-08-15 13:00:26)

  • Confusion over removable drive mounts? [Solved]

    I've installed Arch with the XFCE DE and i'm more then pleased with it! :-D
    However, i'm baffled by where my mounts are located? I have nothing in /mnt/ or /media/, which is where i would usually start looking for my removable drives.
    I followed the 'beginners guide' to the letter, i'm assuming things have changed somewhat.
    #!/bin/bash
    # /etc/rc.local: Local multi-user startup script.
    # create optical drive symlinks
    ln -s /dev/sr0 /dev/cdrom
    ln -s /dev/sr0 /dev/cdrw
    ln -s /dev/sr0 /dev/dvd
    ln -s /dev/sr0 /dev/dvdrw
    This is the section that is new to me, i'm just trying to find out where i can navigate to in the CLI to my removable media?
    I have managed to get XFCE to mount everything after following the XFCE wiki.
    Last edited by ashlee84 (2011-09-19 17:15:39)

    Arch specific cd symlinks are now no longer created.
    On 2011-05-19 udev 169-1 removed cdsymlinks.sh (among other things)
    http://projects.archlinux.org/svntogit/ … 60ccd3d56e
    You need to mount your optical discs somewhere (unless they're AudioCds or blank discs) so you go to the mounpoint of your choice. The symlinks allow you to use other device names, not just /dev/sr0, e.g. both
    mount -o ro /dev/sr0 /media/cd
    mount -o ro /dev/cdrom /media/cd
    should work. Now just
    cd /media/cd/
    Last edited by karol (2011-09-19 16:57:48)

  • Raid array being seen as 2 individual drives

    Hi. Here is the issue as posted in other places. Still searching for the answer to this one.
    Specs:
    K7n2 delta2 platinum with b50 bios
    2x1gb crucial pc3200 2.5cas ram
    AMD Barton 2500
    2 x 160gb 7200rpm 8mb cache SATA Samsung Hdd's
    Thermaltake 430w psu
    Gainward fx5700 ultra graphics
    OS's: original xp corp, slipstreamed xp corp sp2
    raid drivers: nvraid.sys v4.27, 5.10, 5.11 (also the needed nvatabus.sys with those)
    I am NOT overclocked.
    fsb 166
    1:1 ram/cpu
    no spread spectrum or other garbage
    ddr400 patch disabled
    PSU gives presumably stable reading (according to what I see), with amperage ratings above the required.
    checked and rechecked cables for bad ones
    ran mulitple scans on drives, all come up drives OK
    I HAVE installed into Raid 0 already, this is not an issue of hardware failure as far as I am concerned.
    So here is the scenario
    I have properly set up the array, using correct bios settings and the raid setup utility, for a raid 0 array of those 2 hdd's listed. When booting into xp, either version, I have used all 3 of the driver sets listed. I have been reinstalling to do some performance tests on different configurations.
    Anyway, for the last few nights I have been trying to get the windows setup to see the raid 0 array as one 300gb drive. It does not, no matter what I try. It sees them as 2 drives, each being 160gb (or thereabouts). These drives are matched, same firmware, same lot, so that should not be an issue.
    I have used numberous tools to delete the mbr on the drives, both in an array and as single drives. I have done the same as well as tried an install and formatted each drive individually, still the same effect when the raid array is recreated.
    Basically, I can find no good reason why the array is seen as individuals and not as an array. It is interesting to note, that even though xp setup sees the the array as 2 drives, I can complete the text based portion of setup. However, rebooting to start the GUI portion of setup, it will not boot. Obviously becuase the bios has the controller as the nvraid controller and it is supposed to be a raid 0 array, so I expected that.
    Short of rewriting the mbr, either by deleting it or by changing each drive by formatting/partitioning/installing an OS on them, I cannot think of how to fix this. I know the drives and xp cd's work because I have already installed with them.
    I understand what to do in the bios portion, and in the raid setup utility portion. I know that I can boot into windows as a single drive and use the nvraid tool to set it up, but that is not the way it should be, and that is not the way I am going to learn WHY this is happening.
    Roger that. First set in bios enable raid (in this bios I have to enable IDE array, then choose which controller to actually enable raid on, which happens to have been SATA 1 & 2).
    Second, upon reboot, I use the F10 key to enter raid utility. Then, set to striping, set stripe size (which was one of the things I am testing), and add the drives to the array. Next step is to create it. It asks to clear disc data, and it is done.
    Have deleted that array as well as just cleared it. Have deleted it and reboot and rebuild it. Have deleted it, reboot, change bios back to non-raid, reboot. Reboot. Change bios back to raid enabled. Reboot. Rebuild array in raid utility, reboot. Run setup, only see 2 hdd's, not one array.
    Umm, yep, that is about it.
    More to the story now.
    From some other posts I tried this.
    1. destroy array. reboot. disable raid in bios. reboot. verify sata's visible as singles in bios.
    2. power down. pull plugs on sata's. reboot. no drives visible.
    3. pull power. jumper clear cmos. wait 60 seconds. re-pin jumper. power up.
    4. verify no drives. verify default bios settings. all is good
    5. plug drives in. reboot. seen as singles. erase mbr on both drives. reboot
    6. enable raid in bios, and choose sata 1 & 2 as "enabled". reboot.
    7. use F10 key to setup raid. Here is the interesting part. Even though I deleted the array prior to all of this, and removed the drives to force an ESCD update, and cleard the cmos with the board jumper, and then before raid was enabled, cleared the mbr on the drives, when I started the raid utility, the array was already set up. That is the problem, whatever that is. I have read snippets where it is claimed that this chip or bios or whatever stores some kind of a table on this stuff, but this is a bit out of hand.
    That combination, IMO, should have cleared anything out. But, the saga continues.
    Thanks for you help BWM
    [Edit] BTW, I have finally found a utility that will see a raid array and allow me to clear the arrays mbr. It is called SuperFdisk and is at ptdd.com. So far the only one that see's the 2 drives as 1.
    Yeppers.
    Started with v5.10 which came on a floppy with the mobo. Told setup to use both, nvatabus.sys and nvraid.sys. Even switched which one of the 2 I picked first, just to see.
    Same thing with v4.27 and v5.11. Also tried it with just the nvraid.sys and just the nvatabus.sys (which obviously does squat for raid, lol)
    Trying some new things now. Post in a little bit.
    I am officially at 'Wit's End'.
    Here is what I have tried now.
    1.pull drive cables. pull power. jumper clear cmos. wait. power up. no drives
    2.plug sata 1 in. boot. drive detected.
    3.boot to command.com, run MHDD, which is a nice russian utility similar to Spinrite. Used this to clear the mbr at hardware level, and do a complete erase.
    4. reboot to command.com. run superfdisk. erase mbr.
    5. pull plug on sata 1, and plug in sata 2 with sata 1 cable. repeat the erasure steps listed above.
    6. pull plug on sata 2, no sata plugged in. reboot
    7. change bios to raid enable on sata 1 & 2. power down
    8. plug in sata 1 & 2. power up.
    9. inspect raid utility. no listing of any arrays. reboot
    10. in raid utility, build array. did NOT clear discs. reboot
    11. attempt install. single drives found again (used both drivers).reboot
    12. in raid utility, optioned to CLEAR discs (funny, rebuild option is never valid).reboot
    13. attempt install, both drivers, still seen as 2 individuals.
    Things to note. When creating an array when presumably there are none, it assigns the raid array an ID of 2. Upon reboot, the ID is now 1. Don't know what difference that makes.
    Also, tried the install listed above with APIC functionality both off and on. Also, when on, set MPS to both 1.1 and 1.4. In addition to this, each variant I tried manual HAL layers of, in this order, ACPI (the one that actually spells ACPI out), ACPI Uniprocessor, MPS Uniprocessor, and let it choose it for me.
    So, here I sit in a barca-lounger at 'Wit's End', with a warm cup of java and a dinner mint.

    Here is the final product on the floppy disk that I used to  successfully install a stable raid 0 on the MSI K7N2 Delta 2 Ultra 400  Platinum ms-6570e motherboard.
    On root of floppy, from driverset 6.70. (after much testing, I used  driver pack 5.10 for my nic and smbus. I used the realtek sound  drivers off the cd for audio. I have used every driver pack I could  find, and while some did offer better I/O or read/write latency, this  set in general provided the most stable environment. The only drivers  I used were these floppy drivers for SATA, the nic and smbus just  mentioned, the sound just mentioned, and updating the nvide drivers to  mside drivers)
    <from sataraid directory>
    disk1
    idecoi.dll
    nvatabus.sys
    nvraid.cat
    nvraid.inf
    nvraid.sys
    nvraidco.dll
    <from legacy directory>
    nvata.cat
    nvatabus.inf
    I used the txtsetup.oem from the sataraid directory, but edited this:
    [Files.scsi.RAIDCLASS]
    driver  = d1,nvraid.sys,RAIDCLASS
    inf     = d1,nvraid.inf
    dll     = d1,nvraidco.dll
    catalog = d1,nvraid.cat
    [Files.scsi.BUSDRV]
    driver = d1,nvatabus.sys,BUSDRV
    inf    = d1, nvraid.inf
    dll    = d1,idecoi.dll
    catalog = d1, nvraid.cat
    To this:
    [Files.scsi.RAIDCLASS]
    driver  = d1,nvraid.sys,RAIDCLASS
    inf     = d1,nvraid.inf
    dll     = d1,nvraidco.dll
    catalog = d1,nvata.cat
    [Files.scsi.BUSDRV]
    driver = d1,nvatabus.sys,BUSDRV
    inf    = d1, nvatabus.inf
    dll    = d1,idecoi.dll
    catalog = d1, nvata.cat
    Now, it is important to note that I installed or attempted to install  at least 50 times. Bare minimum. I noticed when I use this custom  driver disc that in the GUI portion of setup, XP asks me for files  from the disc. I tried lot's of different things to alleviate this,  and denied some of them.
    One thing that really bugged me was that the bios would see my #2  optical, slave on secondary IDE channel. A dvd/rw drive. And I could  even start the setup from it. But, once I got about 3/4 through copy  file stage on text setup portion, I would hang. Becuase the drive was  no longer accessible. Booting from the master would get me to the  desktop, but the slave optical was nowhere to be found. Updating the  ATA/IDE controller to the ms ide drivers would get it visible, but I  kept having issues with stability after I did that.
    The most stable method I found was to use my above listing of driver  files for the floppy, and when in GUI mode setup asks about NVCOI.DLL,  I skipped it, ignored it, and did not let setup install it. That  actually got me to the desktop, with access to the slave optical as a  "removable drive". It even knew what the hardware was. It just could  not access it. On a reboot however, back to not seeing it. This method  however did allow me to update the nvide driver with the mside driver  with no stability issues. So, for me it was a raving success.
    Here are some links regarding the SATA RAID driver workaround:
    http://66.102.7.104/search?q=cache:jHbX5bNfGx4J:www.msfn.org/board/lofiversion/index.php/t51140.html+nforce2+nvraid.sys+ms+ide&hl=en&client=opera
    http://www.aoaforums.com/frontpage/index.php?option=content&task=view&id=292&Itemid
    http://66.102.7.104/search?q=cache:J9UhG2Kd8W4J:www.short-media.com/forum/showthread.php%3Ft%3D32751+xp+2+sata+raid+0+seen+as+individual&hl=en&client=opera
    Early on one problem I noticed was that in text setup mode of xp  installation, there were long pauses that I have never seen before. I  noticed that with both ide and sata installs. Also I noticed that when  booting there was a really long pause when the xp logo is first seen  in a sort of dim state till when it became bright and vivid.
    Come to find out that this is a more or less typical scenario. Most  instances that I read about were all pointing to the nvide driver. So,  I found if I just updated the PATA controller to the standard ms ide  driver, that went away and the whole system ran better.
    It took awhile to figure out that if you install a driver with the  nForce2 chip, you had to uninstall it or you will have issues. Herein  was the main problem I encountered with the SATA RAID installs. The  nvatabus.sys driver was required for an SATA RAID install. Omitting  the ata driver was impossible. And for awhile I had no success  updating the ms ide driver once I was to the desktop without major  instability. Here are some links regarding the drivers for this  chipset:
    http://www.nforcershq.com/forum/latest-drivers-for-nforce-3-vt60240.html
    In my browsing I came across some pretty interesting articles  regarding ACPI. One thing I started playing with was the different HAL  layers that xp installs on it's own, vs. me picking one manually (F5  key). I must have started the setup at least 50 times to figure out  this: that this particular board does not give me the bios settings to  install xp with anything but the ACPI Uniprocessor Hal. For instance,  the MPS Uniprocessor HAL is much more responsive, but it lacks the  IRQ's needed for setup to see the raid array. I booted to each one,  some locking the system up, some booting OK. The one I found the best  performance with early on was the one that spells out ACPI, not just  initialized. (sorry, I don't want to look it up).
    I seemed to be getting closer, but I could not find the needed bios  settings to properly manage my ACPI, and since I was trying for RAID,  I could not use the one that did work. Here is a link for that kind of  stuff.
    http://www.fceduc.umu.se/~jesruv98/info/acpi/acpi.html
    Another thing that I did not like was being forced to use the dynamic  overclocking feature of this board. I have a 333mhz barton core, and I  have ddr400 ram. In optimized (fool proof) mode in bios, I was running  asynchronous. I did not want that. So I set it down to run at 166mhz,  with very slow and conservative settings on everything. Unfortunately,  if I did this "manual" method, I was forced to use the dynamic  overclocking. I thought I had that figured out. So I set everything to  "optimized". But, as it turns out, the system had terrible stability  without the dynamic overclocking set to at least Private. What this  meant is that I could not rule out that my stability issues  (corruptions and hangs and bsod) were from being overclocked even a  tiny bit or not. And as if that were not enough, this bios has a  special set of settings you must unlock to see. And one of those is  paramount in achieving a stable system. It is called the DDR400 patch,  and it is enabled by default. So, by pressing SHIFT+f2 AND CTRL+F3,  these settings are now available. Like I said, I had to disable that  DDR400 patch setting.
    I also found out from the first day that my board shipped with the  latest bios. I flashed the 2 prior versions with no success in more  stability. After about 6 weeks of getting whipped on by this board, I  found mention of some modded bios's for this board. I have used modded  bios's in the past, some worked wonders, others required some serious  effort to recover from. What I found out about this board is that  there are 2 players who make the modded bios's. Here is the first  index I found from a german website. This one actually is for the  older B4 version only for the Platinum.
    http://storage-raid-forum.de/viewtopic.php?t=2824
    And here is an english forum for pretty much the same thing
    http://www.nforcershq.com/forum/bios-mods-for-k7n-and-k8-boards-vt55014.html
    These links have a bit more information, and I decided to go with  these. I tried versions b61,b62 and b71. I found b71 to work the best  for me. Mind you I am not into overclocking or what-have-you. Just a  rig that performs as well as it was advertised to do. Try these out  for the bios information:
    http://forums.pcper.com/showthread.php?t=385480
    https://forum-en.msi.com/index.php?topic=84715.0B62
    Here is a page that had a bunch of misc stuff I found interesting:
    http://66.102.7.104/search?q=cache:QkvLeKcbwjQJ:www.amdzone.com/modules.php%3Fop%3Dmodload%26name%3DPNphpBB2%26file%3Dviewtopic%26p%3D75383+nforce2+ultra+nvraid+driver+freeze&hl=en&client=opera
    In the end, I have, I think, conquered this board. My findings can be  summed up as follows, all in my opion only I guess.
    1. There are some ACPI/APIC issues with this board or this chipset. I  believe it also included drivers and some can be attributed to XP.
    2. There are some major bios issues with this board.
    3. There are some major driver issues concerning SATA/RAID. I am not  sure who get's the boob prize, nVidia or MSI.
    The only way I have found to get RAID 0 installed and stable is to  modify my bios (which is a modded beta version), modify my driver disk  for SATA/RAID, modify my install sequence for those drivers, modify my  drivers within windows after setup, use different drivers from  different driver packs for different pieces of hardware, and modify my  HAL layer after everything else is done, to achieve peak performance.
    If I had not spent soooo much time trying to get a stable install, I  would have built up an Unattended CD, which has some possibilities for  forcing non WHQL drivers. But, hey man, I am totally burn out on this  board. And all it was for is a spare LAN box for when I go to a  lanparty. Sheesh. Murphy's law.
    Oh, and I also found out, with my own eyes, that the Soyo KT600  Dragon+ that I dumped for this wonderful board, is way faster. Faster  read/writes, faster throughput on the nic, faster booting, much faster  installs of xp. As a matter of fact, I could get my KT600 to get a  consistent thruput on the network to my older KT266a board at 99%.  That is pretty fast. 2 of these Platinum boards, on a sweet switch  that is tweaked, will only go up to 91%, no matter how much I tweak  them. The gigabit connects via a crossover cable at about 38% of full  bore. This is tweaked stuff, but still. I listened to the hype. Dual  channel memory, giglan, etc etc.
    I hope this may help anyone else out there who is still fighting with  these issues.
    Out.
    sul

  • Windows detects shuffle as removable drive and i can't resto

    hey guys, need help.
    my shuffle was working perfectly last night, but when i put it in my office pc, it detected it as a removable drive. when i tried to explore the disk using explorer, it said the there was an i/o error.
    now i am at home and the same thing happens. and, when i try to restore it to factory settings using ipod updater software (latest), there is a "can't mount ipod" error. what's happening and what can i do to restore or fix it?

    Are you using Version 1.1.2? The problem you describe sounds a lot like the problems posted here related to that Firmware version

  • Capturing to removable drives question

    MacOS 10.6.5/ 8 core 2.1/ 6 gig ram/ fibre channel array/ CS5 production premium/ AJA Kona3 / Facilis Terrablock
    premiere sees the shared array as a removable drive which in a sense it is. I can mount and unmount partions via a control panel.
    on partions to which I have write status it will not let me select those partitions as they are "removable"
    Is this how it works? Is there a workaround? How are others dealing with this?
    Thank You
    Doug Beal

    i forgot to mention. another option is to format the drive as HFS+ (the mac standard) and use something like MacDrive on the windows side to communicate w/ the drive....
    http://www.mediafour.com/products/macdrive6/
    cheers

  • Why iTunes hides it's Removable drive from explorer?

    Very strange behaviour (looks like a paranoia - to restrict the using of iPod directly (manualy or by 3d party software))!
    If not launch iTunes - I can see the Removable drive IPOD in explorer and work with it (for example to copy iTunes to another computer).
    But as iTunes runs - it hide the Removable drive and there is no way to restore it exept unload iTunes and unplug-plug iPod.
    Is it ususal behaviour or something wrong with my device?

    Why iTunes hides it's Removable drive from explorer?
    It doesn't. Plug in the iPod. It shows up in Windows Explorer (and the desktop) just fine.
    As soon as iTunes is done updating it, it is ejected and it is removed. All hardware, when removed, is no longer available in Windows Explorer.
    You have mistaken what an iPod is.
    The iPod was designed to play music.
    iTunes was designed to play music (and later adapted) to be the interface for the iPod.
    iTunes does not try to hide anything. As I stated before, iTunes is designed to make it very, very simple to use the iPod. Plug it in, wait a few minutes for it to update and unplug it. That's it.
    Why should the iPod stay mounted on the the desktop when it is no longer in use?
    If you start using the iPod for other functions (as a disk drive), you start making it less simple/more complicated.
    Now you have plug it in, wait for it to mount add or delete files you want and eject it.
    If iTunes was going to "hide" it, either the function would not be included and/or it would not be well documented on how to enable it.
    this fact does make imposible for other software to discover and work with iPod.
    Then using your example, Windows Media Player is full of bugs because it will not run it on Mac OS X.
    Also, it will not run on my car radio or work on my fax machine.
    It's not a bug if you do not make an application or hardware work with other stuff you are not concerned with.
    A bug is something that is not working correctly when it is supposed to.

  • Ubuntu Formated Removable drive

    Hello.... I recently got my MBP (like 30 min ago) and got all my data on a ubuntu formated removable drive. It is ext3 and for some reason is not mounting on mac OSX. does anyone know how i can mount it?
    please help

    For others looking: Read/write mounting of ext2 and ext3 is available on MacOSX via
    the Fuse-ext2 project at http://sourceforge.net/projects/fuse-ext2/

  • Xserve SSD OS drive Raid 5 array - What if SSD OS drive is corrupt or fails

    Xserve SSD OS Drive option with Raid 5 array - What if SSD OS drive fails or the OS becomes corrupted? Could you just re install the os and then upload all of your server settings and it would be able to talk to the raid array and be good to go?
    Additionally if the os is in the raid 5 and becomes corrupted and you are not able to get the os to boot would the raid 5 data not be able to be accessed? Or could you just reinstall the os on the array and be ok?
    This would be the same if the os is inside a software mirror set?
    Thanks in advance!!!

    Hi
    If you're asking can OSX Server be reinstalled without a reformat the answer would be no. This assumes you're using the OSX Server Installer DVD. Assuming no other hardware issues you should be able to access any/all data on any of the Drives using Target Disk Mode and another mac. This will at least allow a transfer of important data to another source. Having said that you should be keeping back-ups anyway.
    You can export Server Admin's configuration as a series of property lists. You can export Users, Groups and Computer Lists from WorkGroup Manager. You can archive the whole of the LDAP database - which will contain everything except home folder information - using Server Admin.
    I'm not sure if this is still the case but one of Apple's Best Practice tips was to setup and configure the Server exactly as you wanted it first. Once you're happy use any one of probably half a dozen methods to make a Bootable cloned backup. A free built-in method would be to boot from an appropriate Installer Disk and save the Server OS as a .dmg to a connected USB or Firewire disk. Or use something like CarbonCopyCloner to do regular scheduled clones to an externally attached drive.
    My 2p.
    Tony

  • Setting up RAID 0 and scratch disk from blank drives?

    Folks,
    Howdy again from NC. I've been setting up an AMD Phenom II 955 to handle PPro CS5 as well as possible, within limits. I built four of these machines for my math class, and am going to give CS5 a go on one of them before caving in and migrating my Production Premium to an i7/X58 platform. Maybe I'll get lucky and find this computer works acceptably with PPro, especially if I transcode my T2i AVCHD footage (likely Neoscene).
    I put three new disks into my build yesterday and would like some pointers on setting them up, if I may ask. I have read through a number of posts on this, but don't find direct answers, unfortunately. I've never set up a RAID and want to get it right.
    I have two Caviar Black drives for my RAID and a Hitachi Deskstar for my scratch disk. The Blacks are new out of the pack and the Hitachi has had zeros written to the drive. How to begin?
    Anticipated issues:
    * Do I need to format the drives in a certain way? I had planned on going into Disk Management and setting up a volume on each as my first move. Right now, they aren't even recognized under My Computer. Under Disk Management, all three show as unallocated.
    From memory, I right click in the unallocated space and select an option for setting up the volume. Prior to this I only used straight-up drives, no RAID, and after writing zeros to a drive selected "New Simple Volume". It seems to me this is the move to make on the single scratch disk.
    But how about the two RAIDed drives? We also have options to set up as "New Striped Volume" or "New Spanned Volume". If the answer is to set as as "New Striped Volume" for the RAID 0 I have planned, do I do this before or after installing the RAID software?
    * My documentation for setting up the RAID on my motherboard doesn't indicate when to change my BIOS setting for the two SATA channels from IDE to RAID. Should I do this before or after running the software to set up the RAID? Do I need to go into the software setup with the two SATA channels already configured as RAID?
    Right now, all SATA channels are configured as IDE.
    * After getting my disks set up, I'd like to optimize my system for editing (turning off unwanted features, etc.). I've been looking all over for a link to an outside site I had bookmarked from a prior post, but lost it on re-install. Anyone recall what the favored link was? It started as a long page of instructions in simple typeface.
    In the end, my disks are as follows (unless someone makes a case to use them differently):
    OS/Programs - 1TB Caviar Green. Yes, I know the deal on green drives, but I needed to use this drive somewhere. I figured using it as the OS drive would be the best spot for the slowest drive. Maybe I botched this and should have used the following drive for the OS? I had transfer rates in mind and thought the Scratch drive should be faster?
    Scratch - 750GB Deskstar 7K100 series. This drive was tops 18 months back when I bought it.
    RAID 0 - Two 640GB Caviar Blacks (32 meg cache, twin processors). A bit older in the Black lineup, but the drive charts show them working quickly.
    To ask one dumb last question, which will really show my newbieness, I use the scratch drive for page files (right? and what else?) and the RAID for holding any media to be worked upon and for encoding the final project?
    I've been reading on this forum for over a month and am amazed that as I have the drives for a RAID, I can't find good links to tell me what to do. I know I am asking redundant questions here but have already spent two hours with the search engine and am only getting tangential anwers (ha! math joke).
    Sorry to be asking such newbie questions all over again, but my luck with the search engine hasn't been so good of late. Maybe Bill's idea of creating a sticky section for common questions is a good idea.

    about 75-80% of the systems we ship, ship with this config (others would be bigger arrays or no array)
    1)OS
    2) project drive 2 x raid 0
    3) render to/export drive 2 x raid 0
    4) back up (pick your poison)
    while i cant speak to the older WDs (we have not used them for 3-4 yrs until now)
    i can tell you with Seagate and now WD we have not seen the issue that applies to this inRaid 0
    we are aware of the timeout issue this happens with controller cards and seagate or WD with large raid 5/6
    simple answer use enterprise drives for raid 5/6
    if you look at all the external raid resellers Sonnet etc they all use enterprise drives (mostly seagate)
    so do we for large raids.
    (drobo does not so buyer beware (green), we like to sell drobo without drives in it and use ours)
    again BACK UP do not assume your raid 3/5/6/10/1 whatever is bullet proof, trust me its not
    so even if you have a loss it should be at best nominal
    something i dont think i have seen mentioned enough either
    the single most common cause of drive failure (or any component failure) is Dirty Power!
    dirty power can be spikes but are usually brown outs (very common in large older cities) or even low voltage coming into the home/office
    this is the most common.
    rather than a clean 120v you could see it as low as 105v
    the other is being on a circuit with a large appliance.
    ever see your lilghts flicker when the AC kicks on?
    buy a good inline filter UPS. add 20% MORE wattage than your power supply
    dont forget to add accessories LCDs, Audio interfaces, speakers/studio monitors etc.
    Scott
    ADK

  • Automountd crash - can't see removable drives

    Hi,
    I have a Power MAC G4 tower running Leopard (v10.5.4). I also have a Western Digital external hard drive (250 GB) attached via firewire that contains my iPhoto Libraries.
    Recently, the WD drive does not appear in my Finder window. It is detected by the System Profiler app but not the Disk Utility. I am also having similar issues with a thumb drive via USB.
    I have attached the WD drive to a PowerBook G4 notebook (also running 10.5.4) and it sees the drive with no problems.
    The tower also has a patch for MobileMe - coincidentally, the WD drive stopped showing up in Finder when I installed this patch. The notebook does not have this patch.
    Also, I see in my /Library/Logs/CrashReporter that I have several recent crash file reports from the automounter. The automount crash log seems to appear even with the WD drive powered off during boot of the tower.
    Has anybody run into this problem and have some advice on how to see my removable drives again?
    Thanks in advance,
    -Brenda

    Hi bstef,
    Something definitely seems wrong with your system. automountd should not be crashing, and based on the description you provide about your external drives, I wouldn't be surprised if other daemons (like diskarbitrationd) are also crashing.
    You might want to have a look at your system.log, which you can see in the Console application. In that log you're looking for further clues as to what is causing some of your system processes to crash. It would probably be a good troubleshooting step to open the Console, view the system.log, then try to attach one of your drives that is not showing up. Hopefully you'll be able to see in real time some system errors.

  • Firewire removable drive eject problem

    Hi
    I have one of those intermittent failures which is driving me crazy. I've got a Granite Digital removable FW-800 drive hooked up to my Quad (10.4.7). Also have a SATA removable drive bay. Most of the time, external drives work just great, and there's no problem.
    However... often enough to make me ask it here, I'll eject the drive, via drag to the trash in the dock, or via contextual menu "eject" and, after a bit longer pause than usual, the icon will disappear from the finder's desktop. Everything looks good, but...
    ... when I go to turn off the drive, or remove it, I get an "improperly put away...may damage drive" message.
    And then... it's totally impossible to restart or shut down the machine. A power off is needed.
    Leaving aside comments on how long the software should be looking for an obviously missing drive before simply giving up (hint: infinity is too long) there's this.
    What's happening? (don't say that something is open on the drive... nothing is) and two, is there something I can do once I get this message to prevent the infinite look? Terminal command? Anything?
    OK: one more thing - am I the only person this happens to?
    TIA
    Tracy
    ex-programmer and Mac user since 1984...

    Gleaned from a string of several painful experiences...
    When "OFF" isn't really "off."
    When it's a switch on the back of some, and certainly firewire boxes fall into the "some" category, peripheral boxes. I spent I don't know how many hours chasing this down because I forgot something I'd learned a few years ago: it's OK to switch off the power to an external firewire box using the switch on the back of the box, but it's NOT OK to switch it off by turning off (unplugging) the "brick" or using a master controller that turns off the AC power.
    Why? Because "off" isn't really "off"... keeping the "brick" alive keeps the system informed about the firewire device's presence; turn it off "at the wall" and you're going to seriously confuse the system. In my system, it would work this way: if I left the box switch in the "on" position, then when I turned on the wall power, the hard drive would show up on my desktop.
    Now, I was always religious about ejecting the drive before I powered down, but my mistake was powering down "at the wall" instead of using the switch on the back of the box. I figured I'd save the power drained by the brick when I wasn't using the drive.
    Bad mistake. About 50% of the time, when I'd eject the -next- drive I mounted externally, I'd get a message saying "improper device removal"... and my system would -seriously- choak up. Nothing would run; nothing would quit and I'd be faced with a forced hard power-off of my whole system.
    Once I recalled what the heck I was doing wrong, and reverted to "once powered on, leave it on" the problems went away.
    The problem seems to affect external SATA drives as well (although I'm not as positive of that as I am of the firewire issue.) So: leave the boxes plugged into the wall, and only use the switches on the back to turn them on and off. If the wall-wart bricks are eating up extra power, I'm afraid that's the price you pay for the modern age.
    hth
    Tracy

  • We have created two partitions in removable drive(USB). One of the partition is active and the other is hidden. We are trying to acess the hidden partition in Win PE 3.0 environment using WMI

    We have created two partitions in removable drive(USB). One of the partition is active and the other is hidden. We are trying to access the hidden partition in Win PE 3.0 environment using WMI. VBScript code snippet used to detect the partitions is given
    below:- 
    SetobjWMIService = GetObject("winmgmts:"_&
    "{impersonationLevel=impersonate}!\\"&
    strComputer & "\root\cimv2")
    SetcolDisks = objWMIService.ExecQuery
    Select * from Win32_LogicalDisk")
    It will return the partition which is active but fails to list the partition which is hidden. The same piece of code was supported on WinPE 2.0

    I am giving the complete code, may be you are able to understand better. We are using Win32_LogicalDisk to retrieves the complete information of all the drives (like C:, D:) including removable drives. 
    Function
    LocalDriveFound()
        strComputer =
    SetobjWMIService = GetObject("winmgmts:"_
    "{impersonationLevel=impersonate}!\\"&
    strComputer & "\root\cimv2")
    SetcolDisks = objWMIService.ExecQuery
    "Select * from Win32_LogicalDisk")
    ForEachDiskDrive
    IncolDisks
            DriveLetter = Left(DiskDrive.Name,1)
            DriveType = DiskDrive.DriveType
            VolumeName = DiskDrive.VolumeName
            WScript.echo Driveletter &
    "|"& Drivetype &
    "|"&VolumeName
    SelectCaseDriveType
    Case2 ,3  
    'Fixed or removable
    If(VolumeName=USBVolumeName)
    Then
    If(DriveLetter<>
    "Z")
    Then
                        ChangeDriveLetterWithMountvol DriveLetter,
    "Z"
    EndIf
                    bIsLocal=
    True
    EndIf 
    If(VolumeName=USBRootName)
    Then
    If(DriveLetter<>
    "Y")
    Then
                        ChangeDriveLetterWithMountvol DriveLetter,
    "Y"
    EndIf
                    bIsLocal=
    True
    EndIf 
    CaseElse
    EndSelect
    Next
    SetDrives =
    Nothing
    SetFileSystemObject =
    Nothing
    End
    Function

  • SATA Boot as Removable Drive ?

    Recently a buddy installed a new ASUS board with SATA boot via onboard SATA. SATA drives showed up as removable. Didn't like that so we installed a SATA PCI card and they functioned normally.
    Then we freshened up an MSI MS-6788 board using the onboard SATA to boot a SATA Raptor drive. Did the F6, install other drivers during XP Pro install.
    These drives functioned normally.
    Which was one reason I chose MSI for the new build I just finished yesterday. Using the MSI P6N I installed a Raptor as the boot drive, a second Raptor and a SATA CD/DVD player.
    F6 during install was not necessary as it recognized the drive. It boots fine and all drives are recognized but again these are showing up as removable drives.
    Doe anyone know the definitive answer to this or what I'm doing wrong.
    MSI tech wrote me back a short note saying SATA showing up as removable is normal. I don't buy that. I have (and have seen) too many systems whereas SATA boot and internal devices "don't" show up as removable using both add-on cards and on board SATA.
    As well the older MSI MS-6788 does not show the devices as removable.
    Thanks...

    I totally agree. But this is far from a server board. Let me ask... when was the last time you "hot swapped" a SATA drive?
    Especially plugged into the onboard SATA.
    I just don't follow the concept. For the sake of being hot swappable...
    ... you get a c:boot and d: internal drive that show they can be ejected (when in reality they can't because they are being used).
    ...and then you can eject your CD/DVD drive (which I can't see the reason to do).
    ... and then to top it off you plug in a USB stick and it's the 4th ejectable device.
    Somewhere there should be the criteria to untick a box that says "this drive is not removable".

Maybe you are looking for