Mounting data partition + Finder issue

Hello,
I have now 2 disks in my MBP (SSD + HDD in Optibay). I want to use the HDD for data only storage and I would like to mount the disk in the folder
~/Data
So I created the dir and mounted the partition manually to test it :
sudo mount_hfs /dev/disk1s2 /Users/me/Data/
It works but there is a little annoyance:
I open Finder and go to my Home dir. Now I enter the Data directory where my partition is mounted. First, the sidebar does not show now that I'm in my user directory. Now if I want to step one level up using Cmd + UpArrow, I do not go back to my home folder as expected but to a list of all my disks.
Is there a way to fix that ?

I also tried with the "nobrowse" option but the behavior is the same.

Similar Messages

  • Snap-To-Grid Finder feature doesn't work for mounted data CDs (Icon View)

    I always use Icon View in Finder. And I AM aware of the CMD+J --> Arrange by --> Snap-To-Grid feature. I've set it for all my other Finder windows for my startup drive, and it works. (Actually, I set it to auto-arrange by Kind.) I've even used it as the default setting by clicking the "Set As Defaults" button at the bottom of the View Options window.
    But there seems to be a weird glitch where every time I insert a burned data CD with icon folders and such, my Finder window always opens a mess of icons, one on top of each other. I keep setting it back to CMD+J --> Arrange by --> Kind, and the icons organize into grids right after. I click "Set As Defaults" again. But when I eject the CD, then mount it again, Finder gives me a mess of one-on-top-of-the-other icons all over again. What gives? I just want to be able to set all my files to auto-arrange in Finder by Kind.

    But when I eject the CD, then mount it again, Finder gives me a mess of one-on-top-of-the-other icons all over again
    Of course it will.
    The CD is read-only - it can't be written to. Since the window position, view settings, layout, etc. are stored in the directory, there's no way for the Finder to write the changed settings back to the disk before you eject it.
    The issue occurs because what you're seeing is how the window was laid out when the disk was burned in the first place.
    Your solution is to re-burn the disk, positioning the icons where you want them before starting the burn.

  • I changed my system on my mac 10.6.8 by doing a migration of my data and now i do find issues when i open logic, like i cant close it anymore (need to use the force quit option) if i ll bounce anything it will crash and same thing will happen if i wanna i

    i changed my system on my mac 10.6.8 by doing a migration of my data and now i do find issues when i open logic, like i cant close it anymore (need to use the force quit option) if i ll bounce anything it will crash and same thing will happen if i wanna import something, if anybody has a idea??

    Hi
    This any help?
    http://support.apple.com/kb/TS3968
    CCT

  • Tutorial - How to triple boot OSX, Linux and Windows 8.1 with a shared Data Partition without any third party Win / OSX softwares

    This is not a question, but rather a personal guide that has proved to be running successfully.
    I would like to thank numerous sources, including Christopher Murphy's suggestions at:
    Re: Repairing Boot Camp after creating new partition
    Before proceeding, there are certain concepts needs to know:
    Why Boot Camp does NOT allow further partitioning of drives after Windows has installed?
    Answer: Because the way Apple configures the Mac to be recognized as non UEFI capable system on Windows.
    Quote from Christopher Murphy based on the above line:
    However, Windows on Macs right now use CSM-BIOS mode in Mac firmware that presents BIOS to Windows rather than EFI. Windows thinks it's on a BIOS computer, and therefore mandates the use of MBR for boot disks, rather than GPT. So that's why we have this hybrid MBR+GPT approach on Mac with Windows on it. You inherit the limitations of MBR, which is four primary partitions.
    So what does it means?
    It means that OSX + EFI + Recovery HD + Boot Camp partition = 4 primary partitions and thus any attempt to modify the disk will render booting issues of either system.
    For more info on GPT (GUID Partition Table disks VS Master Boot Record or MBR in short, you may visit: http://msdn.microsoft.com/en-us/library/windows/hardware/dn640535%28v=vs.85%29.a spx)
    So, how to overcome it?
    The general guideline is to install ALL GPT ready OS first then create a Data partition, before installing Windows (Which is again, NOT supported GPT due to EFI configuration by Apple where end-users are not able to modify it).
    Interestingly, since Mac Pro 2013 Late supports only Windows 8 and above, thus it is not known if this CSM-BIOS applies to it or not.
    Do take note that GPT disks in Windows can only be booted when the system meets the 2 requirements:
    http://msdn.microsoft.com/en-us/library/windows/hardware/dn640535%28v=vs.85%29.a spx#gpt_faq_win7_boot
    1) Windows x64 version (Which is a must for newer Macs. If you cannot go to Boot Camp 5, then you need Windows 7 x86 or 32bit version)
    2) UEFI system. However, Windows sees all Macs (With the possibility of Mac Pro 2013 Late is an exception. To be determined) as BIOS, or rather NON-UEFI system.
    In short, booting on GPT disks is not possible for Mac in Windows.
    Summary,
    It is tested that a combination of the following will not work:
    - OSX + Windows + Linux
    - Windows + OSX + Linux
    - Windows + Linux + OSX
    Usually it can create the system un-bootable or OSX refused to install due to the system does not recognize such partitions and / or Disk Utility refused to format a free space. An example screen-shot is provided below:
    The error message is shown as
    Title: "Failed to erase volume" Message: "Failed to wipe volume, as an error occurred: MediaKit has reported that the device does not have enough free space to execute the requested operations."
    The second thing is about the preparations we need.
    1) 1X Windows 7 or 8 DVD or USB thumbdrive
    1A) If you uses a DVD to install, you will need another thumbdrive to load the BootCamp drivers for Windows as well as may requires an external DVD drive for newer Macs
    2) 1X Linux DVD of your choice. Personally I choose Fedora 20.
    So ready? Let's go.
    1. Using Disk Utility, shrink the OSX's partition size to what is needed. For me, I give OSX 150GB. Do NOT create any new partition.
    Disk Utility should see something like below whereby only OSX partition is left with desired disk space. The remaining space are to be unused disk space for the moment.
    Note: Click on the top most item that should start with the size of your HDD / SSD. Then clicked on "Partition" and specify the desired OSX size. Hit "Apply" after that.
    2: Download Boot Camp drivers only via Boot Camp Assistant. The USB thumbdrive shall be used later after Linux's installation.
    Boot Camp Assistant should see this:
    I have only selected "Download latest Windows Support Files from Apple"
    3. Insert Linux DVD, reboot Mac into EFI mode (The left most first "EFI mode").
    Note 1: Before rebooting, please plugged in an Ethernet adapter because Wi-Fi drivers is not installed.
    Note 2: For Thunderbolt adapters, it must be plugged in before reboot as hot-swapping is not supported under Linux. More on the tips at the end of this article.
    Note 3: Press and hold "Option" after the screen turns black. Release Option key after you see the image as below:

    For the unfortunate part that did not make it on time to edit the images:
    9. Install the Windows Support software from your CD/USB drive to gain full functionality of your computer. Reboot and go to Windows again.
    Note 1: You may choose to eject disc at this point of time. For Apple SuperDrive users, you will need to wait until the drivers (i.e. Boot Camp support files) is installed and rebooted before ejecting is reasonably possible (As I failed to figured out how to right click without the drivers)
    Note 2: Unlike Windows 7 on KBase article TS4599 Keyboard/trackpad inoperative, black screen, or alert messages when installing Windows 7, USB stick can be plugged in after the Windows installation is done. This is because Windows 7 (And probably Windows 7 with SP1 DVD) does not have a built in USB 3 drivers when it was released back in 2009 where USB3 has not arrived then.
    Note 3: Due to TPM, Bitlocker is not supported without the use of thumbdrives.
    10. Using Disk Management to determine the given drive letter for the DATA partition (DO NOT DELETE and RECREATE partition or else you can goodbye to booting Linux and OSX). Disk Management will not allow you to format it as exFAT / FAT32 in graphical way.
    Note: You may remove or modify some of the disk letters in Disk Management. However, do NOT remove / modfify the drive letter for the partition with 200MB size in HFS. This is because it will disallow booting of Linux and neither could Windows nor OSX can do anything EXCEPT to reinstall Linux only.
    11. Open Command Prompt in Administrator Mode (Important!!), and key in the following command:
    format F: /FS:exFAT
    Give this volume a label after it has successfully formatted before hitting "Enter" again.
    Note: Mine Data partition was assigned as F drive. Please make necessary adjustment to "F:" should your Data partition is assigned to other letters.
    12. After that, Setup your Data partition structure as you like.
    Tip: Minimally create the important folders such as:
    - Music
    - Documents
    - Movie (Videos)
    - Downloads
    - Pictures
    All these folders are commonly used by the 3 OSes. I do NOT recommend changing of /home (OSX and / or Linux) and / or user home directory (Windows) either partially or as a whole.
    This is because of compatibility issue.
    On a side note, iTunes Media Library used in OSX and Windows are NOT able to be use interchangably due to hard-coded path used.
    13. Useful troubleshooting in Fedora / Linux:
    With references to these:
    http://chaidarun.com/fedora-mbp
    http://anderson.the-silvas.com/2014/02/14/fedora-20-on-a-macbook-pro-13-late-201 3-retina-display/
    http://unencumberedbyfacts.com/2013/08/16/linux-on-a-macbook-pro-101/
    I would like to highlight a few important points:
    1) Wi-Fi driver:
    http://rpmfusion.org/Configuration
    Note 1: The sound driver should be installed at Out of Box Experience. However, the Wi-Fi is not.
    Note 2: Install both free and non-free repository. By the way, some other software like VLC can only be found after the Free Repository is installed.
    Search for "akmod-wl" in Gnome-Package-Installer in order to install Wi-Fi drivers
    Note 3: For those who do not have Ethernet adapters and their Mac does NOT have a built-in Ethernet port, it is recommended to get one. This is because Fedora 20 does not have a good support for iPhone USB tethering. Unsure for Andriod / Blackberry / Windows Phone users.
    2) Grub Menu:
    It will show several options to boot into OSX, even of the capability to boot into x86 or x64 mode. However, neither of them is bootable except Linux and the rescue.
    Hence, it is recommended to remove the items by hand in this file:
    /boot/efi/EFI/fedora/grub.cfg
    Command to be used:
    "sudo gedit /boot/efi/EFI/fedora/grub.cfg"
    Parts to be removed:
    - For any extra kernels, delete the target entry by locating the line "menuentry" under "/etc/grub.d/10_linux" sector to one line above the next "menuentry".
    It is recommended to keep one main kernel, and one recovery at the minimal.
    - For other OS, delete all the entry (Since neither it can works) under "/etc/grub.d/30_os-prober" sector without removing the lines starts with ###.
    Auto Mount exFAT partition:
    - After installing extra packages for exFAT support (Since it is not supported by Fedora 20 from a default installation), you may wish to edit "/etc/fstab" in order to mount the exFAT partition during boot time.
    Command to be used:
    "sudo gedit /etc/fstab"
    Add the following line in gedit:
    UUID=702D-912D /run/media/Samuel/DATA                   exfat    defaults        1 2
    Note 1: For DATA partition, OSX & Boot Camp partition, Fedora defaults mounts under: "/run/medua/<Username with case sensitive>/<Partition Label Name>"
    Note 2: UUID is unique ID. You can find out the UUID by:
    Step 1: First determine the DATA partition number:
    "sudo gdisk /dev/sda"
    Step 2: Determine the UUID of this partition number:
    "sudo blkid /dev/sda8"
    Reference 1: http://manpages.courier-mta.org/htmlman5/fstab.5.html
    Reference 2: http://liquidat.wordpress.com/2007/10/15/short-tip-get-uuid-of-hard-disks/
    3) Overheating CPU
    Solution is to issue the following command in Linux terminal: su -c "echo -n 1 > /sys/devices/system/cpu/intel_pstate/no_turbo"
    4) System resumes immediately after suspend
    Solution is to issue the following command in Linux terminal: su -c "echo XHC1 > /proc/acpi/wakeup"
    5) What does not works well out of box:
    - Both GNOME and KDE's fonts are too small to be readable for out of box experience. Additional configuration is a need. (Some of the info can be found on "More Tips" later)
    - Thunderbolt hotplugging is NOT supported under Windows and Linux so far. Neither FaceTime HD camera works as well.
    - The red light in Headphone jack is always on. I do not have luck in switching off the light without losing the sound.
    Note 1: It is determined that the module "snd_hda_intel" is used by both cards (HDMI and normal output)
    Note 2: It is also known that blacklisting it can switch off the redlight at the price of muting the system.
    Note: Based on this article, http://support.apple.com/kb/TS1574
    A Mac (Except Mac Pro) needs servicing when there is a red light while the system fails to detect internal speakers. However, this article does NOT applies to this issue.
    5A) More Tips:
    Install gnome-tweak-tool for more customization
    Search for: "gnome-package" to install:
    Install Gnome Package Installer for advanced package repository
    Install Gnome Package Updater for advanced updates to be install (Whereby Fedora's App Store alike might not show the relevant updates)
    14. Verify if disk is still GPT:
    Use Gdisk to determine if the disk is pure GPT:
    http://ubuntuforums.org/showthread.php?t=1742682
    Command: sudo gdisk -l /dev/sda (The entire hard drive)
    You should see the MBR is "Protective" instead of anything else.
    15. Congrats, the system is ready for triple boot. (I forgot to eject my Windows DVD when the photo was taken)
    Note 1: You cannot set the default startup disk in Linux due to the lack of Boot Camp Control Panel in Linux.
    Neither is changing startup disk recommended in Windows due to the inability to display correctly.
    For me, I click "Cancel" whenever I am on this tab (Feel free to make other Boot Camp adjustments in other tabs).
    Only OSX I know that can show the startup disk options correctly.
    Note 2: For some reason, OSX likes to auto mount the EFI partition everytime it boots up. It is not known to have any issue for ejecting other disks or mounting disks via Disk Utility.
    Note 3: It is not determined if any Firmware or System upgrades will cause issues. It is only known that all 3 OS's regular updates should not be an issue.
    System Updates excludes Mac OSX 10.9.3 updates to OSX 10.9.4 type as I had done it on a OSX 10.9.4 Mac or Windows 8.1 to Windows 8.1 Update 1 since my Windows DVD comes with Update 1.
    System Upgrades refers to OSX Mavericks to Yosemite, Fedora 20 to Fedora 21, Windows 8.1 Update 1 to Windows 8.2 / Windows 9 for that matter.
    Note 4: Reset SMC and / or PRAM will NOT affect your ability to boot any of the OS (OSX, Recovery HD, Fedora & Windows 8)
    Yup, that is it!

  • Disk Utility - Partition map needs repair because a data partition needs loader space.

    I just finished setting up both my OSX and Windows installs from scratch after fitting an SSD, which in-turn was right before my logic board died and Apple replaced it, now it looks like I have some sort of hard drive issue brewing.
    This was my plan for the SSD, and how it currently displays in Disk Utility although that wasn't the case earlier:
    And in Terminal:
    My intention was to have two boot partitions for each OS, 'Macintosh HD' and 'Win 7 Pro' and a third shared data partition 'Projects' on the SSD, which I made in Drive Genius after installing Boot Camp. I don't want Macintosh HD accessible from Windows because I'll be using Paragon HFS+ or MacDrive to give write access and don't want OSs stomping on other OSs turf, hence needing three partitions. Everything looked fine until I just checked Disk Management under windows and realised it couldn't see the Projects volume. Even though it's fine in OS X, it was just marked black/unallocated space.
    So I booted back into OSX, all my files look fine so I ran Disk Utility and the Partition tab looked really odd - unfortunately I didn't get a screenshot. All volumes reported their size correctly but visually, Macintosh HD took up most of the drive. I could see 'Windows 7 Pro' under this, but the Partition Layout section had a scrollbar, which if I scrolled down showed 'Projects' squished into a tiny gap at the bottom. I ran a Verify, which reported no problems, and at some time since the Partition Layout has reverted to how it should look (as in the screenshot above), with 'Projects' book-ended by "Macintosh HD' and 'Windows 7 Pro'.
    Now when I run a Verify on Macintosh HD or Projects volumes, it says there's no problem, but if I run one on the drive, I get this message:
    Volume Macintosh HD on disk0s2 has 0 bytes of trailing loader space and it needs 134217728 bytes
    Problems were found with the partition map which might prevent booting
    Error: Partition map needs repair because a data partition needs loader space.
    I've only managed to find one other mention of this error here, but the fix is not relevant to me because I don't have Sophos installed. I've tried Single User/Safe Mode but it just boots into normal mode, so I can't do a fsck -fy.
    ** /dev/rdisk0s2 (NO WRITE)
    Can't open /dev/rdisk0s2: Permission denied
    That value in bytes is exactly 128mb, so I suspect the problem lies with one of the invisible partitions that show up in iPartition and Disk Management under Windows, but not in Disk Utility. I have backups and I suspect the root of the problem is partitioning in iPartition after installing Boot Camp, but I've never had issues with this approach in the past so I'm wary of just giving up and reinstalling Windows again will be massive hassle because I no longer have a SuperDrive and last time it refused to install from USB.
    Anyone have any idea what's going on? It seems like the sort of issue Disk Utility should just handle, at least in Recovery mode, but it's not playing ball. It also doesn't seem like a massive problem since my files all look fine and performance is OK, so I'm reluctant to do anything major.
    I'll update with a shot of the drive in Disk Management from Windows in a few minutes, in case that sheds light on anything. Thanks!

    Similar issue here. I manually partitioned my hard disk for triple boot (using Gparted on Linux), then everything was just fine until I ran bootcamp, to do something as simple as create a boot USB.
    I get the same error as a result and have to work my way into booting, by resorting first to a Linux live USB, then restarting from the live USB, to finally reach my rEFInd boot manager, or whichever boot manager should be initialized at startup.
    I suppose that the cause in my case is that some operation "scratched" the protective MBR. See this:
    http://www.mactech.com/articles/mactech/Vol.23/23.03/APMtoGPT/index.html
    I am hoping to fix it using an external Yosemite installation media: see this guide -
    http://www.macworld.com/article/2367748/how-to-make-a-bootable-os-x-10-10-yosemi te-install-drive.html
    And as a last resort to reinstall.
    I'll admit I am negatively surprised. I need this computer for professional reasons, and for the sake of "preserving the integrity of OSX", measures defined by Apple instead tend to make partitions far easier to damage. And this problem seems to affect a number of users.
    As for what I have to go through to fix it: a 5GB download, during which I have to register my credit card to the Apple Store. "Pay first, get your free software next."
    IF Disk Utility can fix it, from the external media, then fair enough. The hassle is unpleasant but it files as "a choice".
    Otherwise you can file it safely under software design calamity.

  • Partitioning - best way 500gb drive, 3 Linux OS's and a data partition

    Hi All
    This morning I killed my laptop. No, it wasn't Windows that annoyed me, I was watching the Rugby and wasn't really concentrating. It was 7am kick off though. Anyway, I have decided to completely rebuild the system, and as an interim measure have installed Ubuntu (cos it is simple and quick to install - btw Oneiric is actually not bad at all).
    Now, to the question. I have a 500gb hard drive on my laptop. I ideally would like:
    1) Essential - data partition of about 80Gb or so. I want this so that I can point Dropbox, Videos, etc. at this.
    2) Essential - Arch as the main system.
    3) Not really essential - Ubuntu - I do like Ubuntu, and besides i find it convenient to use one Dropbox account on Arch and one on Ubuntu. Ideally I would like to be able to use both on Arch but...
    4) Would like - CentOS or Scientific Linux. Essentially a RHEL lookalike. It's not really necessary but it would look better on my cv or whatever. Problem here being that CentOS et al use LVM.
    No Windows to complicate things.
    What I guess I'm really asking is what order to create the partitions and a suggested layout. I figure on giving a big chunk to the data partition, and then pointing all of the other systems at Documents, Video, Music etc. on the data partition. Whatever OS's I install I just want them to work along with each other, and essentially home (apart from settings) will be on the data partition, i.e. Videos, Music etc.
    Any suggestions welcome, particularly in terms of what to install first, second etc. Should the data partition be at the start or end of the drive? One swap partition? By the way my laptop has 3Gb ram.
    Thanks
    Rich
    Last edited by RichAustin (2011-09-18 16:39:24)

    DJQuiteFriendly wrote:The most convenient option (in my opinion) would be mounting your data partition to /home. This way, you could carry your configuration files for apps across distros, if you so choose. Your swap partition would probably only be useful to you if you want to hibernate because you have 3 gigs of ram already. I have 4 gigs on my laptop and I only went above 1 or 2 when I had tons of apps open at the same time. I haven't checked, but I imagine it's less for Arch. If you want to be able to hibernate, it has to at least be the size of your ram. Your root partitions for the distros should be 15-20gb each.
    Good point about Swap. I wouldn't mount the data partition as /home because of the possibility of different OS's screwing up the settings. However, I do point the .thunderbird folder at the data partition though because it makes it one heck of a lot easier to keep contacts etc. synchronised across distro's. Not sure this approach would work with everything though. Why on earth haven't Mozilla written a decent method of synching Thunderbird?
    tooke wrote:
    As for a layout, here's what I would do:
    /dev/sda1 - extended partition to hold everything else
    /dev/sda5 - data partition
    /dev/sda6 - arch, 15 GB
    /dev/sda7 - ubuntu, 15 GB
    /dev/sda8 - centOS/scientific/whatever, 15 GB
    /dev/sda9 - swap, 4 GB
    I had a similar layout in mind to this. Thanks for the suggestions.
    Rich

  • Solaris-x86 mount fat32 partition, the partition max size limit?

    solaris10 x86, laptop, 10G FAT32 partition for windows & x86 exchange data.
    the fat32 partition mount as normal, can be read fine.
    but write some file by x86, that can not find by windows.
    anyboy know did the solaris-x86 mount fat32 partition, the partition max size limit? or no limit, why this problem occur?

    Mounting Windows partition in Solaris
    The easiest way to share data now is to do it through a FAT32 partition. Solaris
    recognises it as partition of type pcfs. It is specified as device:drive where drive is
    either the DOS logical drive letter (c through z) or a drive number (1 through 24).
    Drive letter c is equivalent to drive number 1 and represents the Primary DOS partition
    on the disk; drive letters d through z are equivalent to drive numbers 2 through 24,
    and represent DOS drives within the Extended DOS partition.Syntax is
    mount -F pcfs device:drive /directroy-name
    where directory name specifies the location where the file system is mounted.
    To mount the first logical drive (d:) in the Extended DOS partition from an IDE hard
    disk in the directory /d use
    mount -F pcfs /dev/dsk/c0d0p0:d /d
    You can use mount directory-name after appending following line is in
    /etc/vfstab file
    device:drive directory-name pcfs no rw
    for example
    c0d0s0:c /c pcfs no rw
    If your windows partition like the following means
    C: - NTFS, D:-FAT32, E:-NTFS, F:-FAT32
    Then you can only mount D, F not C & E.
    Mounting D Drive:
    mount -F pcfs /dev/disk/c0d0p0:c /mountpoint
    Mounting F Drive
    mount -F pcfs /dev/disk/c0d0p0:d /mountpoint
    The driveletter only for fat not including other file systems (ntfs or any linux filesystems).

  • V570 - Has too many partitions - Can I nuke one? I need a separate Data Partition!

    Hi,
    I convinced a Buddy to buy a V570 two days ago. (I've used a Lenovo Laptop for work for a year, and it's been rock solid.) The box was delivered to his house a few hours ago. He lit it up and put his name on it, and then brought it to me, as I help his family out with their computers. (Our Wives are best friends.) I'm a bit geeky and usually know my way around these boxes. But I'm a little stumped on this one.
    Normally on laptops they come with tons of bloatware, and it's usually faster to go up to the OEM's site, download all the latest drivers and  utilities, then back up the original image before blowing it away, and installing a fresh Windows OS. One of the other main issues is most lappys have one big partition for the OS and Data. So if you get a Trojan or virus => it can nuke all of it. So I always divide the drive, and have a Data partition, so you don't lose everything if (when) something nasty occurs. 
     But in this case the Box really doesn't have too much bloatware, so I thought make the Factory backup disks, then uninstall the few unwanted programs, partition the C Drive, and create a Data drive in that space. I didn't even look at the hidden partitions so when I went to Create the Data partition I was warned Windows 7 64 Pro doesn't support more than 4 partitions on the operating system drive! If I go into Disk Management I see the typical small Win7 recovery 200 MB partition, a 654 GB C  partition, a empty (?) 29 Gig Lenovo partition, and a 14.75 OEM partition. I'm used to the first 2 partitions but what's the rational for the last two from lenovo? One is the "factory" image, and I assume it's the OEM partition, so what's the Lenovo partition for? Can I shrink C, and enlarge the Lenovo partition, so it can become the Data Drive =>  without affecting the lenovo drives function?
    I thought I may have to go with the new Windows install but I can find all the drivers /utilities software at the Lenovo Sites. So I'm a bit stumped and would appreciate your help.
    Thanks for the assist.
    Regards,
    -Jim-

    Jim,
         In one word, no.
         I would strongly advise you to just leave it alone, unless you want to spend hours on the phone to your friend, trying to fix all the problems your friend will encounter, with his "new" modded system.
         Please, I'm not trying to be nasty, or unkind. Those 4 partitions are the key to Lenovo's One Key Recovery. Lenovo has spent a lot of time, and engineering to make their systems as user friendly, and trouble free as possible. They built in the Enhanced Experience 2.0, and customized the Windows 7 software for fast booting. Just because you "can"  repartition the drive, doesn't mean you "should".
         These forums are filled with users who messed around with their drive structure, used a modded BIOS, or just plain screwed up their programs and hardware, just because they "could". Then they want some urgent help for their machines that went wacky. The moderators on these sites have a hard enough job, keeping track of the various systems "as shipped", to do any troubleshooting on those systems that the user has repositioned the drive, or deleted the programs that Lenovo has included for recovery.
         As you've said, there's not a lot of bloatware on Lenovo's machines. You shouldn't have to reload a "fresh Window OS". If you do, some of the Lenovo's Enhanced Experience 2.0 for Win 7, and some other functions will be toast. That's why you don't see all of the Windows drivers on their site. Lenovo only includes the drivers that have been modified for your V570. Stick with them.
         So, in the end, yeah you can mess with the partitions, but you shouldn't. See this thread to know what you are getting in to, and be ready for your friend's late night phone calls.
    http://forum.lenovo.com/t5/IdeaPad-Y-U-V-and-Z-series/new-disk-partioning-and-one-key-recover-featur...
    DragonRider
    I'm DO'ing IT
    Lenovo Y470 085525U 2nd generation Intel® Core™ i7-2630QM processor ( 2.00GHz 1333MHz 6MB )
    IdeaCentre A520 Intel® Core™ i5-3230M processor ( 2.60GHz 2600MHz 3MB )
    YOGA Tablet 2 Pro-1380F
    X1 Carbon 2nd Gen (20A8) ThinkPad + T420

  • Multiple LDAP Servers and Attribute-Based Data Partitioning

    Hello
    We currently want to implement following szenario on Netweaver 2004s. From the
    following SAP Help documentation we want attribute based data partitioning:
    http://help.sap.com/saphelp_nw70/helpdata/EN/4e/4d0d40c04af72ee10000000a1550b0/frameset.htm
    The difference to the SAP document is that we want a distribution of attributes over
    multiple LDAP servers. So we tried to fit that concept into xml. see attached xml source.
    The Portal finds both LDAP Systems but it is NOT that the useres are beeing merged
    but they appear as two distict users in the portal UME. If you do a lookup in the portal
    usernamagent system you get and see two users.
    User1: unique ID = USER.Datasource1.uid
    User2: unique ID = USER.Datasource2.uid
    Obviously the UME system was not able to merge that information of the two distict
    LDAP Systems. MSADS and Lotus Notes.
    Hence my questions:
    1) is it possible to distribute attributes over multiple ldap data sources
    2) any ideas why UME constructs two different users based in Datasource ID's specified in XML
    Thanks for any contributions or ideas,
    Ulrich Scherb
    <?xml version="1.0" encoding="UTF-8"?>
    <dataSources>
        <dataSource id="PRIVATE_DATASOURCE"
                    className="com.sap.security.core.persistence.datasource.imp.DataBasePersistence"
                    isReadonly="false"
                    isPrimary="true">
            <homeFor>
                <principals>
                     <principal type="group"/>
                     <principal type="user"/>
                     <principal type="account"/>
                    <principal type="team"/>
                    <principal type="ROOT" />
                    <principal type="OOOO" />
                </principals>
            </homeFor>
            <notHomeFor/>
            <responsibleFor>
                <principals>
                     <principal type="group"/>
                     <principal type="user"/>
                     <principal type="account"/>
                    <principal type="team"/>
                    <principal type="ROOT" />
                    <principal type="OOOO" />
                </principals>
            </responsibleFor>
            <privateSection>
            </privateSection>
        </dataSource>
        <dataSource id="NOTES_LDAP"
              className="com.sap.security.core.persistence.datasource.imp.LDAPPersistence"
              isReadonly="true"
              isPrimary="true">
              <homeFor/>
              <responsibleFor>
                   <principal type="account">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="j_user"/>
                             <attribute name="logonalias"/>
                             <attribute name="j_password"/>
                             <attribute name="userid"/>
                        </nameSpace>
                       <nameSpace name="com.sap.security.core.authentication">
                            <attribute name="principal"/>
                       </nameSpace>
                   </principal>
                   <principal type="user">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="firstname" populateInitially="true"/>
                             <attribute name="lastname" populateInitially="true"/>
                             <attribute name="email"/>
                             <attribute name="uniquename" populateInitially="true"/>
                        </nameSpace>
                        <nameSpace name="$usermapping$">
                             <attribute name="REFERENCE_SYSTEM_USER"/>
                        </nameSpace>
                   </principal>
              </responsibleFor>
              <attributeMapping>
                   <principal type="account">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="j_user">
                                  <physicalAttribute name="uid"/>
                             </attribute>
                             <attribute name="logonalias">
                                  <physicalAttribute name="uid"/>
                             </attribute>
                             <attribute name="j_password">
                                  <physicalAttribute name="unicodepwd"/>
                             </attribute>
                             <attribute name="userid">
                                  <physicalAttribute name="*null*"/>
                             </attribute>
                        </nameSpace>
                       <nameSpace name="com.sap.security.core.authentication">
                            <attribute name="principal">
                                 <physicalAttribute name="uid"/>
                            </attribute>
                       </nameSpace>                    
                   </principal>
                   <principal type="user">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="firstname">
                                  <physicalAttribute name="givenname"/>
                             </attribute>
                             <attribute name="lastname">
                                  <physicalAttribute name="sn"/>
                             </attribute>
                             <attribute name="uniquename">
                                  <physicalAttribute name="uid"/>
                             </attribute>
                             <attribute name="loginid">
                                  <physicalAttribute name="*null*"/>
                             </attribute>
                             <attribute name="email">
                                  <physicalAttribute name="mail"/>
                             </attribute>
                        </nameSpace>
                        <nameSpace name="$usermapping$">
                             <attribute name="REFERENCE_SYSTEM_USER">
                                  <physicalAttribute name="sapusername"/>
                             </attribute>
                        </nameSpace>
                   </principal>
              </attributeMapping>
            <privateSection>
                   <ume.ldap.access.server_type>MSADS</ume.ldap.access.server_type>
                   <ume.ldap.access.server_name>ldap1</ume.ldap.access.server_name>
                   <ume.ldap.access.server_port>389</ume.ldap.access.server_port>
                   <ume.ldap.access.authentication>simple</ume.ldap.access.authentication>
                   <ume.ldap.access.user>xxxxx</ume.ldap.access.user>
                   <ume.ldap.access.password>xxxxx</ume.ldap.access.password>
                   <ume.ldap.access.base_path.user>O=SMT_TEST</ume.ldap.access.base_path.user>
                   <ume.ldap.record_access>TRUE</ume.ldap.record_access>
                   <ume.ldap.unique_uacc_attribute>uid</ume.ldap.unique_uacc_attribute>
                   <ume.ldap.unique_user_attribute>uid</ume.ldap.unique_user_attribute>
                   <ume.ldap.access.context_factory>com.sun.jndi.ldap.LdapCtxFactory</ume.ldap.access.context_factory>
                   <ume.ldap.access.user_as_account>true</ume.ldap.access.user_as_account>
                   <ume.ldap.access.ssl_socket_factory>com.sap.security.core.server.https.SecureConnectionFactory</ume.ldap.access.ssl_socket_factory>
                   <ume.ldap.access.objectclass.user>person</ume.ldap.access.objectclass.user>
                   <ume.ldap.access.objectclass.uacc>person</ume.ldap.access.objectclass.uacc>
                   <ume.ldap.access.naming_attribute.user>cn</ume.ldap.access.naming_attribute.user>
                   <ume.ldap.access.auxiliary_naming_attribute.user>uid</ume.ldap.access.auxiliary_naming_attribute.user>
                   <ume.ldap.access.naming_attribute.uacc>cn</ume.ldap.access.naming_attribute.uacc>
                   <ume.ldap.access.auxiliary_naming_attribute.uacc>uid</ume.ldap.access.auxiliary_naming_attribute.uacc>
              </privateSection>
         </dataSource>
        <dataSource id="CORP_LDAP"
              className="com.sap.security.core.persistence.datasource.imp.LDAPPersistence"
              isReadonly="true"
              isPrimary="true">
              <homeFor/>
              <responsibleFor>
                   <principal type="account">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="j_user"/>
                             <attribute name="logonalias"/>
                             <attribute name="j_password"/>
                             <attribute name="userid"/>
                        </nameSpace>
                       <nameSpace name="com.sap.security.core.authentication">
                            <attribute name="principal"/>
                            <attribute name="realm"/>
                            <attribute name="domain"/>
                       </nameSpace>
                   </principal>
                   <principal type="user">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="firstname" populateInitially="true"/>
                             <attribute name="displayname" populateInitially="true"/>
                             <attribute name="lastname" populateInitially="true"/>
                             <attribute name="fax"/>
                             <attribute name="title"/>
                             <attribute name="department"/>
                             <attribute name="description"/>
                             <attribute name="mobile"/>
                             <attribute name="telephone"/>
                             <attribute name="streetaddress"/>
                             <attribute name="uniquename" populateInitially="true"/>
                        </nameSpace>
                        <nameSpace name="com.sap.security.core.usermanagement.relation">
                             <attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE"/>
                        </nameSpace>
                        <nameSpace name="$usermapping$">
                             <attribute name="REFERENCE_SYSTEM_USER"/>
                        </nameSpace>
                   </principal>
                   <principal type="group">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="displayname" populateInitially="true"/>
                             <attribute name="description" populateInitially="true"/>
                             <attribute name="uniquename"/>
                        </nameSpace>
                        <nameSpace name="com.sap.security.core.usermanagement.relation">
                             <attribute name="PRINCIPAL_RELATION_MEMBER_ATTRIBUTE"/>
                             <attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE"/>
                        </nameSpace>
                        <nameSpace name="com.sap.security.core.bridge">
                             <attribute name="dn"/>
                        </nameSpace>
                   </principal>
              </responsibleFor>
              <attributeMapping>
                   <principal type="account">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="j_user">
                                  <physicalAttribute name="samaccountname"/>
                             </attribute>
                             <attribute name="logonalias">
                                  <physicalAttribute name="samaccountname"/>
                             </attribute>
                             <attribute name="j_password">
                                  <physicalAttribute name="unicodepwd"/>
                             </attribute>
                             <attribute name="userid">
                                  <physicalAttribute name="*null*"/>
                             </attribute>
                        </nameSpace>
                       <nameSpace name="com.sap.security.core.authentication">
                            <attribute name="principal">
                                 <physicalAttribute name="samaccountname"/>
                            </attribute>
                            <attribute name="realm">
                                 <physicalAttribute name="*null*"/>
                            </attribute>
                            <attribute name="domain">
                                 <physicalAttribute name="*null*"/>
                            </attribute>
                       </nameSpace>                    
                   </principal>
                   <principal type="user">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="firstname">
                                  <physicalAttribute name="givenname"/>
                             </attribute>
                             <attribute name="displayname">
                                  <physicalAttribute name="displayname"/>
                             </attribute>
                             <attribute name="lastname">
                                  <physicalAttribute name="sn"/>
                             </attribute>
                             <attribute name="fax">
                                  <physicalAttribute name="facsimiletelephonenumber"/>
                             </attribute>
                             <attribute name="uniquename">
                                  <physicalAttribute name="samaccountname"/>
                             </attribute>
                             <attribute name="loginid">
                                  <physicalAttribute name="*null*"/>
                             </attribute>
                             <attribute name="mobile">
                                  <physicalAttribute name="mobile"/>
                             </attribute>
                             <attribute name="telephone">
                                  <physicalAttribute name="telephonenumber"/>
                             </attribute>
                             <attribute name="department">
                                  <physicalAttribute name="ou"/>
                             </attribute>
                             <attribute name="description">
                                  <physicalAttribute name="description"/>
                             </attribute>
                             <attribute name="streetaddress">
                                  <physicalAttribute name="postaladdress"/>
                             </attribute>
                             <attribute name="pobox">
                                  <physicalAttribute name="postofficebox"/>
                             </attribute>
                        </nameSpace>
                        <nameSpace name="com.sap.security.core.usermanagement.relation">
                             <attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE">
                                  <physicalAttribute name="memberof"/>
                             </attribute>
                        </nameSpace>
                        <nameSpace name="$usermapping$">
                             <attribute name="REFERENCE_SYSTEM_USER">
                                  <physicalAttribute name="sapusername"/>
                             </attribute>
                        </nameSpace>
                   </principal>
                   <principal type="group">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="displayname">
                                  <physicalAttribute name="displayname"/>
                             </attribute>
                             <attribute name="description">
                                  <physicalAttribute name="description"/>
                             </attribute>
                             <attribute name="uniquename" populateInitially="true">
                                  <physicalAttribute name="cn"/>
                             </attribute>
                        </nameSpace>
                        <nameSpace name="com.sap.security.core.usermanagement.relation">
                             <attribute name="PRINCIPAL_RELATION_MEMBER_ATTRIBUTE">
                                  <physicalAttribute name="member"/>
                             </attribute>
                             <attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE">
                                  <physicalAttribute name="memberof"/>
                             </attribute>
                        </nameSpace>
                        <nameSpace name="com.sap.security.core.bridge">
                            <attribute name="dn">
                                  <physicalAttribute name="*null*"/>
                             </attribute>
                        </nameSpace>
                   </principal>
              </attributeMapping>
            <privateSection>
                   <ume.ldap.access.server_type>MSADS</ume.ldap.access.server_type>
                   <ume.ldap.access.server_name>ldap2</ume.ldap.access.server_name>
                   <ume.ldap.access.server_port>389</ume.ldap.access.server_port>
                   <ume.ldap.access.authentication>simple</ume.ldap.access.authentication>
                   <ume.ldap.access.user>yyyyy</ume.ldap.access.user>
                   <ume.ldap.access.password>yyyyy</ume.ldap.access.password>
                   <ume.ldap.access.base_path.user>O=SMT_TEST</ume.ldap.access.base_path.user>
                   <ume.ldap.access.base_path.grup>O=SMT_TEST</ume.ldap.access.base_path.grup>
                   <ume.ldap.record_access>TRUE</ume.ldap.record_access>
                   <ume.ldap.unique_uacc_attribute>samaccountname</ume.ldap.unique_uacc_attribute>
                   <ume.ldap.unique_user_attribute>samaccountname</ume.ldap.unique_user_attribute>
                   <ume.ldap.access.context_factory>com.sun.jndi.ldap.LdapCtxFactory</ume.ldap.access.context_factory>
                   <ume.ldap.access.authentication>simple</ume.ldap.access.authentication>
                   <ume.ldap.access.flat_group_hierachy>true</ume.ldap.access.flat_group_hierachy>
                   <ume.ldap.access.user_as_account>true</ume.ldap.access.user_as_account>
                   <ume.ldap.access.dynamic_groups>false</ume.ldap.access.dynamic_groups>
                   <ume.ldap.access.ssl_socket_factory>com.sap.security.core.server.https.SecureConnectionFactory</ume.ldap.access.ssl_socket_factory>
                   <ume.ldap.access.objectclass.user>User</ume.ldap.access.objectclass.user>
                   <ume.ldap.access.objectclass.uacc>User</ume.ldap.access.objectclass.uacc>
                   <ume.ldap.access.objectclass.grup>Group</ume.ldap.access.objectclass.grup>
                   <ume.ldap.access.naming_attribute.user>cn</ume.ldap.access.naming_attribute.user>
                   <ume.ldap.access.auxiliary_naming_attribute.user>samaccountname</ume.ldap.access.auxiliary_naming_attribute.user>
                   <ume.ldap.access.naming_attribute.uacc>cn</ume.ldap.access.naming_attribute.uacc>
                   <ume.ldap.access.auxiliary_naming_attribute.uacc>samaccountname</ume.ldap.access.auxiliary_naming_attribute.uacc>
                   <ume.ldap.access.naming_attribute.grup>cn</ume.ldap.access.naming_attribute.grup>
              </privateSection>
         </dataSource>
    </dataSources>

    Hi Ulrich,
    Hope your problem is resolved. We are using EP7 and SP18. We are doing some study on your first issue. i.e. Distributing a user attribute into multiple LDAPs. Can you please let me know the feasibility? If yes, what are all step do I have to follow? Expecting your valuable answer. Thanks in advance!
    Regards,
    Kabali

  • Mount: can't find /dev/sda2/mnt in /etc/fstab

    I'm trying to install Arch on a virtualbox virtual machine to become familiar with it before I install it on my main system. I've created 4 partitions, dev/sda1=1007kB boot partition, dev/sda2/= 4gb root partition which I am trying to mount, dev/sda3=swap which I've already configure and dev/sda4=1792MB Home which I haven't mounted. I've formatted sda2 and sda4 in ext4, but whenever I run
    mount /dev/sda2/mnt
    I get an error message saying
    mount: can't find /dev/sda2/mnt in /etc/fstab
    I've tried to view fstab with the less command but I only got a bunch of tildes (~). I'm fairly new to linux so keeping the explanations simple would be appreciated.

    The above post should fix the immediate issue you are posting about - but there is another issue:
    VEL0CITY wrote:dev/sda1=1007kB boot partition
    Is that a typo?  Because that's not big enough for a boot partition.  The kernel itself is 3-4 times that size.  100MB is a common starting suggestion for /boot.  I can do with quite a bit less than 100MB, but not that much less.

  • Dual-booting with other Linuxes; shared data partition

    I've got two entirely-blank 320GB hard drives on my computer, and I'd like to dual-boot Arch and Debian on it (and potentially others later). How should I set up GRUB (or GRUB2-- the wiki says that it's a better option when dual booting with other distros) for each OS in order to have both of them able to boot, as well as retaining the capability of adding other distros? (Assuming that Arch's GRUB(2), not Debian's, will be installed to the MBR.)
    In addition, I'd like to keep my config files and data separate (with a shared data partition on HD 2).
    - What is the best way to set this up separately from the /home partition, i.e. mount /data on startup and be able to access it quickly from a filemanager or the commandline? I venture a guess that I'd edit /etc/fstab and add a symlink to /data within /home/USERNAME...
    - What is the right size for the /home partition in this setup?
    A tentative partition scheme is as follows (note that I have 4GB RAM, since that factors into swap size):
    HD 1
      4GB shared swap partition
      256MB ext3 Arch /boot partition
      20GB ext4 Arch / partition
      ? ext4 Arch /home partition *see note above*
      256MB ext3 Debian /boot partition
      20GB ext4 Debian / partition
      ? ext4 Debian /home partition *see note above*
      (free space)
    HD 2
      320GB shared ext4 data partition
    Last edited by DrKillPatient (2012-06-20 18:38:01)

    Most of it is a matter of opinion I think, but since I have a similar setup I'll throw in my two cents.
    DrKillPatient wrote:I've got two entirely-blank 320GB hard drives on my computer, and I'd like to dual-boot Arch and Debian on it (and potentially others later). How should I set up GRUB (or GRUB2-- the wiki says that it's a better option when dual booting with other distros) for each OS in order to have both of them able to boot, as well as retaining the capability of adding other distros? (Assuming that Arch's GRUB(2), not Debian's, will be installed to the MBR.)
    I use GRUB (legacy). Adding a distro in the grub menu is just a matter of finding the kernel and initram image of the distro and adding an entry. OS's generally either have a fixed location/name for the kernel and image or have a fixed link, so there are no problems on updates. I really don't like GRUB 2 and don't see the point of using it unless you are using something exotic that GRUB doesn't support.
    DrKillPatient wrote:I
    In addition, I'd like to keep my config files and data separate (with a shared data partition on HD 2).
    - What is the best way to set this up separately from the /home partition, i.e. mount /data on startup and be able to access it quickly from a filemanager or the commandline? I venture a guess that I'd edit /etc/fstab and add a symlink to /data within /home/USERNAME...
    - What is the right size for the /home partition in this setup?
    I just mount the data partition in /mnt/data and make symlinks from my home partition. In my case the data partition is ntfs, since I also use windows. My home partition contains 1.2 GB, of which 600 MB source code. So if you only keep configs in them it probably won't reach 1 GB.
    DrKillPatient wrote:
    I
    A tentative partition scheme is as follows (note that I have 4GB RAM, since that factors into swap size):
    HD 1
      4GB shared swap partition
      256MB ext3 Arch /boot partition
      20GB ext4 Arch / partition
      ? ext4 Arch /home partition *see note above*
      256MB ext3 Debian /boot partition
      20GB ext4 Debian / partition
      ? ext4 Debian /home partition *see note above*
      (free space)
    HD 2
      320GB shared ext4 data partition
    In my opinion a seperate boot partition is only useful for the OS of which the bootloader is installed to the MBR.

  • After update udev mounts all partitions automatically (but shoudn`t)

    Here goes: after updating udev from 167-2 to 168-1, it started mounting all partition at boot. No rules (the list and the rules are the default ones) seem to include this, and google said automounting MUST be set up by user.
    Downgrading fixes the issue, but I try to keep the system up to date, so this is not an option. Also I do not want to disable udisk mounting by polkit, since I want to keep the option of mounting them via KDE.
    Can anyone help please?
    P.S. arch x68_64
    Last edited by levantis (2011-05-17 16:05:35)

    same here...
    i changed the 'pass' value in the /etc/fstab to "0" for the mounted devices - this works temporarily for me so i can boot up the system.
    excuse me for my bad english

  • Shared Data Partition + Lion + Snow Leopard - What files go where?

    I have partitioned my new internal drive into 3 (which is currently in a enclosure).
    The 1st Partition reserved for Lion
    The 2nd for reserved Snow Leopard
    And the 3rd reserved for a shared Data parition
    I'm not enirely sure how to divde up the files. What should be put on the Data parition?
    And how to direct each OS parition to access the shared data partition?
    I would appreciate advice and example(s). Detailed information is always welcome.
    Thank you.

    darkhorse85 wrote:
    It would excellent if you would could me about other programs such as Mail which would suffer releated issues.
    I really don't know, and don't know if there's a list anywhere of Mac apps.  Mail seems to change with every release (and even some "point" updates).  I think Calendar is one, too.
    This list of 3rd-party apps is unofficial, but seems pretty reliable as far as what will run where: http://roaringapps.com/apps:table
    As you'll see, it's mostly geared towards Lion vs. Mountain Lion (and in a few months, will be Mountain Lion and Mavericks).
    You'll probably have to use some trial-and-error, and/or contact the makers of the apps you use.
    I am not familiar with using any kind of software as a Virtual Machine how would this work?
    I'm not very familiar with it, but you install 3rd-party software that lets you run one OS within a different one, rather than having to boot into one or the other.  Basically, it puts a Virtual Machine folder containing one whole OS installation on the disk of another;  it runs concurrently with the other OS, in a separate window (or multiple windows for different apps, I think).  There are some downsides, especially performance, but a lot of folks do it, usually to run Windows, but some to run Snow Leopard on Lion or Mountain Lion.  There may be some restrictions on the Snow Leopard license, too -- Apple didn't allow that for OSX at all for a long time, except for the Server product.  I don't know what the rules are now.
    Parallels and VMware are two I see mentioned often.  I seem to recall reading about a free one, but as it's pretty complex software, I'm a bit skeptical. 
    I don't know where else to point you, but that should get you started on research.  Look for those apps and/or Virtualization Software to find more.
    Good luck!

  • [~SOLVED] 1 min hang during boot while mounting xfs partitions (LVM)

    Hi all,
    After the upgrade I did yesterday (which included linux-3.12.8-1 and lvm2), the boot time has increased by 1 minute as the system hangs while mounting two partitions formatted as xfs and residing on logical volumes.
    $ systemd-analyze blame
    1min 13.676s home-VDP76-videos.mount
    1min 13.111s home-VDP76-VBox_VMs.mount
    2.980s [email protected]
    I have the fsck hook as second-to-last entry in my mkinitcpio.conf, but the fstab entries for these partitions include
    ... xfs defaults 0 0
    so, as far as I undertstand, the partitions should not be checked, am I missing something!?
    I have googled for similar issues but I did not find anything useful, any suggestion would be greatly appreciated.
    Thanks
    edit: I blame the check disk because of what reported on the system journal (note the time stamps):
    Jan 23 00:10:37 ArchTP kernel: psmouse serio5: alps: Unknown ALPS touchpad: E7=10 00 64, EC=10 00 64
    Jan 23 00:10:39 ArchTP kernel: psmouse serio5: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3
    Jan 23 00:10:40 ArchTP kernel: input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio4/serio5/input/input25
    Jan 23 00:11:47 ArchTP systemd[1]: Mounted /home/VDP76/VBox_VMs.
    Jan 23 00:11:47 ArchTP kernel: XFS (dm-4): Ending clean mount
    Jan 23 00:11:47 ArchTP kernel: XFS (dm-3): Ending clean mount
    Jan 23 00:11:47 ArchTP systemd[1]: Mounted /home/VDP76/videos.
    Jan 23 00:11:47 ArchTP systemd[1]: Starting Local File Systems.
    Jan 23 00:11:47 ArchTP systemd[1]: Reached target Local File Systems.
    I should also add that the involved partitions are ~20 Gb each and quite full...
    edit2: I have freed up almost all space on the video partition and the time for mounting those partitions has now decreased to 8 sec...I will mark the thread as solved, but I still would appreciate an input on the reasons why the partitions are checked regardless of the fstab setting, for example, is this pertinent!?
    dumpe2fs -h /dev/mapper/waldorf-video | grep -i 'mount count'
    dumpe2fs 1.42.8 (20-Jun-2013)
    dumpe2fs: Bad magic number in super-block while trying to open /dev/mapper/waldorf-video
    Last edited by VDP76 (2014-01-22 23:38:25)

    WonderWoofy wrote:I don't think that the fsck.xfs is really a fsck at all.  It is there for compatibility purposes, and a real check can be done with xfs_check and xfs_repair.  So the fsck.xfs will just always give an exit status of zero.
    exactly..in fact the man page says
    fsck.xfs(8) wrote:fsck.xfs - do nothing, successfully
    so fsck.xfs simply exits with a zero exit status.
    running xfs_check gives
    xfs_check is deprecated and scheduled for removal in June 2014.
    Please use xfs_repair -n <dev> instead.
    and xfs_repair does not find errors on both partitions.
    Still, I do not understand how nothing being done can take up so much time.
    By the way, a short S.M.A.R.T. self-test did not report errors...
    In the meanwhile, there has been another kernel upgrade and the timing issue persists, so I am assuming it has something to do with the last lvm2 upgrade.

  • Mounting FAT partitions on Solaris 8

    Does Solaris 8 support mounting Windows FAT 16/32 partitions
    from IDE drives on an Intel platform. The PCFS type seems
    to be reserved for dos floppies.

    mount -F pcfs /dev/dsk/cXdXpX /mnt should work.
    Where c = 0 or 1 (0 for primary , 1 for secondary ide)
    d = 0 or 1 (0 for master , 1 for slave )
    p = 0 .. 4 (number of the partition)
    You can find more info in the Solaris x86 FAQ
    There used to be an issue where you couldnt mount a partition that was formated under WinNT but I dont think that is still an issue under Solaris 8 x86

Maybe you are looking for