[SOLVED] Initramfs fails to properly mount luks partition

Hello All,
As I foreshadowed in my intro, I'm having trouble getting encrypted Archlinux to work on my Acer Aspire 5750. I've previously had encrypted Debian Netinst and encrypted Aptosid working on this device. The arch iso I'm using is 2011.08.19-core-i686.
https://bbs.archlinux.org/viewtopic.php?id=124415 appears similar and Tallahassee offers a workaround, but it doesn't work for me (unless I'm doing something wrong?)
I suspect there is a bug in the init scripts used by the initramfs. I would like to first of all determine whether I really should file a bug report (and if so where), and secondly whether we can find a workaround to get things up and running in the meantime.
Now for the meaty bits.
Old grub doesn't appear to support lvm or luks, so I first of all prepare for grub 2 by installing the gptfdisk package into the iso environment. I use gdisk to set up a 1 or 2 mb bios boot partition at the start of /dev/sda, followed by a 256mb partition (/dev/sda2) for /boot, with the rest of the drive given to the partition intended for the encrypted root partition (/dev/sda3).
I use cfdisk to toggle the partition type for /dev/sda3 to 8e (Linux LVM).
Run the following commands, with credits to Aptosid: Installing to a Cryptroot:
pvcreate /dev/sda3
vgcreate vg /dev/sda3
lvcreate -n crypt --extents 100%FREE vg
cryptsetup --verify-passphrase -c aes-xts-plain:sha512 luksFormat /dev/mapper/vg-crypt
cryptsetup luksOpen /dev/mapper/vg-crypt cryptroot
pvcreate /dev/mapper/cryptroot
vgcreate cryptvg /dev/mapper/cryptroot
lvcreate -n swap --size 2g cryptvg
lvcreate -n root --extents 25%FREE cryptvg
lvcreate -n home --extents 100%FREE cryptvg
/arch/setup
Go through the arch setup as normal. At the bit where you configure hard-drives, you'll find all your encrypted partitions ready waiting to be labelled and formatted. Stop after installing packages.
After installing packages, press CTL-ALT-F2 and log in. Edit /mnt/etc/rc.conf and /mnt/etc/mkinitcpio.conf. CTL-ALT-F1 and reinstall packages. Proceed with the configure step.
Don't install a boot loader; just quit after configuring everything.
Follow the steps here: Grub 2 During Archlinux Installation.
The automatically generated grub.cfg doesn't include things necessary to lvm and luks. Before running grub_bios-install, I edit the grub.cfg to insmod lvm and flag the kernel with cryptdevice=/dev/mapper/vg-crypt:cryptvg-root and rootfstype=ext4 (because that is the encrypted root's filesystem).
At this point, I would expect the system to be bootable, so reboot.
Grub2 loads up. I can verify the changes I made to grub.cfg by pressing `e'. So boot and see the messages,
Loading Linux linux ...
Loading initial ramdisk ...
A password is required to access the cryptvg-root volume:
Enter passphrase for /dev/mapper/vg-crypt:
So far so good. I enter my passphrase. The following messages ensue:
vgscan: unrecognized option '--sysinit'
Error during parsing of command line.
device-mapper: create ioctl failed: Device or resource busy
mount: mounting /dev/mapper/cryptvg-root on /new_root failed: Device or resource busy
ERROR: Failed to mount he real root device.
Bailing out, you are on your own. Good luck.
So I get dumped into the ramfs. That ain't much fun.
Does anyone have some ideas on things to try next? Should I file a bug report?
Last edited by /dev/zero (2011-10-22 00:28:52)

Not sure what you mean by difficult and buggy to work with... at this low level, if a VM is having issues replicating this sort if thing, it's not a very useful VM. Find one that doesn't suck. I tend to use KVM because it's terminal friendly via emulation of a serial console.
Anyways, I can reproduce your issue and fix it. There's 2 things you'll need to change:
1) You're naming your unlocked cryptdevice the same thing as your root. That's creating a clash with the name you've given your root logical volume. Since the name isn't really important, just change your cryptdevice declare to "cryptdevice=/dev/mapper/vg-crypt:root"
2) Since you're doing the xzibit thing and nesting lvm inside of the crypt device (i still think its really bizzare to do this, but it looks like mkinitcpio supports it anyways), you'll need to add the lvm2 hook a second time to HOOKS in /etc/mkinitcpio.conf after the encrypt hook.
Last edited by falconindy (2011-10-22 00:19:10)

Similar Messages

[Solved] How to resize an encrypted luks partition?

Edit: This worked: http://www.enigmacurry.com/2007/04/28/r … ilesystem/
I have some empty space on my harddrive, and wish to fill it up, with my existing partition.
This is my harddrive setup in gparted:
And fdisk respectively:
[ricky@archlinux ~]$ sudo fdisk /dev/sda -l
Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x58bd1192
Device Boot Start End Blocks Id System
/dev/sda1 * 63 289169 144553+ 83 Linux
/dev/sda2 289170 195607439 97659135 83 Linux
/dev/sda2 (the crypted luks partition) contains an lvm group.
I am trying to enlarge the luks partition, to fill all of the empty space, soi can give some more space to the lvm's inside the encrypted partition.
I did come across an interesting page here: http://www.enigmacurry.com/2007/04/28/r … ilesystem/
Is this the correct approach, by deleting the WHOLE partition (not the data), and then simply creating a new partition, with the same start-sector, and the higher end-sector?
Will that allow me to then resize my lvm's inside of the luks partition?
I am sorry if this is confusing.
Last edited by xdemo (2011-03-18 07:53:35)

jakobm wrote:Please be sure to use the bbs search: Defragment a NTFS partition from LINUX
That thread has absolutely no information other than a list of motivations to use Windows to defrag it... and a link to a buggy Python defragger.
Here's the only bulletproof way to defrag NTFS under Linux:
Make a new partition of the same size (or bigger), and format it to NTFS and mount it at /defragged
Mount your fragged partition at /fragged
rsync -av /fragged /defragged
Wha-la. /defragged is now your fragged partition, defragged. Reformat /fragged and rsync it back if you really must.
Drives get fragmented if you do multiple copies at the same time, so don't do anything else on the drive while it's syninc.
Last edited by dagelf (2014-08-28 07:21:54)

[Solved] Kernel failed to re-read the partition for Udisk

re-produce procedure
* plug a udisk
* use `fidsk` to partition the disk `fdisk /dev/sdb`
* save the partition. Error will raise.
Here is the error raised by fdisk
Disk /dev/sdb: 3.7 GiB, 3974103040 bytes, 7761920 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x2dfbdb2a
Command (m for help): n
Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1):
First sector (2048-7761919, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-7761919, default 7761919):
Created a new partition 1 of type 'Linux' and of size 3.7 GiB.
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Re-reading the partition table failed.: Success
The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8).
Syncing disks.
When use the kpartx to re-read the partition, it still raise error
# sudo kpartx -a -s /dev/sdb
device-mapper: reload ioctl on sdb1 failed: Invalid argument
create/reload failed on sdb1
following is the error message when run strace
# sudo strace kpartx -a -s /dev/sdb
open("/etc/udev/udev.conf", O_RDONLY|O_CLOEXEC) = 4
fstat(4, {st_mode=S_IFREG|0644, st_size=49, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f2f5cff0000
read(4, "# see udev.conf(5) for details\n\n"..., 4096) = 49
read(4, "", 4096) = 0
close(4) = 0
munmap(0x7f2f5cff0000, 4096) = 0
access("/run/udev/control", F_OK) = 0
open("/dev/urandom", O_RDONLY) = 4
read(4, "\v~", 2) = 2
semget(0xd4d7e0b, 1, IPC_CREAT|IPC_EXCL|0600) = 1179649
semctl(1179649, 0, SETVAL, 0x1) = 0
semctl(1179649, 0, GETVAL, 0xffffffffffffffff) = 1
close(4) = 0
semop(1179649, {{0, 1, 0}}, 1) = 0
semctl(1179649, 0, GETVAL, 0xffffffffffffffff) = 2
ioctl(3, DM_DEV_CREATE, 0xf4ff30) = 0
ioctl(3, DM_TABLE_LOAD, 0xf4ff10) = -1 EINVAL (Invalid argument)
write(2, "device-mapper: reload ioctl on s"..., 60device-mapper: reload ioctl on sdb1 failed: Invalid argument) = 60
write(2, "\n", 1
But if you unplug the disk and plug the disk again. The partition is re-read and I can see the sdb1.
My system is the latest ( 2015-4-14 ).
Did anybody meet this error and tell me how to fix it ? Thanks a lot.
Last edited by Jeffrey4l (2015-04-30 02:01:35)

alphaniner wrote:
Jeffrey4l wrote:
Actually, I first meet this issue by following step.
* qemu-img create disk 10G
* qemu-nbd -c /dev/nbd0 disk
* fdisk /dev/nbd0
write the partition table and raise the above error.
I don't get any error when writing the table to an nbd.
It's probably not relevant, but I load the nbd module manually with "modprobe nbd nbds_max=2 max_part=4"
I really load that module.
I also tried losetup file, it also raised error when write the partition info.
So i think whether i forget some module or service which is used by hot re-partition.

[Solved] Problem booting root in LVM, which spans two LUKS partitions

Hello,
I recently switched to Arch from OpenSuse, and I'm having a bit of trouble getting my encrypted disks to boot properly. I have two disks, the first is a 4 TB drive set up like this:
MBR partition table
Partition 1 - Windows 7, 200GB
Partition 2 - Linux boot, 200MB
Partition 3 - Luks partition, 1.7TB
Partition 4 - Luks partition, 1.7TB
Within partition 3 and 4 is an LVM volume which spans the two partitions. The reason for that is just that I can't have a 3.4TB partition on an MBR formatted drive (as I understand it). I have the root volume and swap, etc within this LVM. The second hard drive is simply a data drive, also encrypted. My problem is that I don't know how to tell the system to open both of these encrypted partitions at boot, in order to boot the root volume. This worked fine under OpenSuse and I only needed to enter the Luks password once (it is the same for both partitions).
As it is right now, my boot parameters in /etc/default/grub look like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset cryptdevice=/dev/sda3:sda3_crypt root=/dev/mapper/vg_arch-root"
Currently the system boots, asks for the password to /dev/sda3, hangs for roughly 20 seconds and then kicks me into a root prompt. I can manually open /dev/sda4 at this point using cryptsetup and the system will continue booting normally... but I would like to have it set up properly, so I don't need to do that. Considering OpenSuse does this out of the box I figured it should be possible under Arch. Any help would be appreciated.
Thanks
Last edited by keitolainen (2015-06-09 21:56:08)

As a quick update in case anyone is reading this, I cleaned up the script a bit and hopefully made it something closer to a "proper" fix.
Rather than editing /usr/lib/initcpio/hooks/encrypt directly, I did the following:
cp /usr/lib/initcpio/hooks/encrypt /etc/initcpio/hooks/
then changed the following section of /etc/initcpio/hooks/encrypt from:
# Ask for a passphrase
if [ ${dopassphrase} -gt 0 ]; then
echo ""
echo "A password is required to access the ${cryptname} volume:"
#loop until we get a real password
while ! eval cryptsetup open --type luks ${resolved} ${cryptname} ${cryptargs} ${CSQUIET}; do
sleep 2;
done
fi
to:
# Ask for a passphrase
if [ ${dopassphrase} -gt 0 ]; then
echo ""
while true ; do
echo -n "A password is required to access the ${cryptname} volume: "
read -sr password
echo $password | cryptsetup open --type luks ${resolved} ${cryptname} ${cryptargs} ${CSQUIET}
if [ $? = 0 ] ; then
break
fi
done
echo $password | cryptsetup open --type luks /dev/sda4 sda4_crypt
echo ""
fi
then edited /etc/mkinitcpio.conf and changed:
FILES=""
to:
FILES="/etc/initcpio/hooks/encrypt"
and ran
mkinitcpio
This is working well for me and I think it's a little cleaner than the solution I posted earlier. Sorry for the awkward bash, if anyone has a more elegant solution please let me know.

[~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.

[Solved] unable to mount harddisk partition or flash drive

After recent updates to gnome 3.4.2,i am unable to mount harddisk partition or flash drive .I have 2 year old arch installation with gnome.
When i click on partitions in nautilus,it says "Unable to mount program files \n Not authorized to perform operation"
Problem is not only while mounting partitions.
Wherever we need authorization .Like changing date and time ,changing user accounts using gnome UI etc.The unlock button is greyed out permanently.
even i am not able to shutdown using gnome menus. it just log me out only ,do not restart or shutdown.Though i can shutdown using shutdown command on commandline.
i run gnome using daemon method. not through xinitrc .
https://bugs.archlinux.org/task/25031?p … ekit#close
I found a similar discussion in this bug. But since, i do not use xinitrc, it is unlikely they will help me.
Can someone be kind enough to help me on this?
Thanks in advance.
Last edited by piyushbhatt (2012-09-11 05:48:57)

maybe changes in udev or any other package
you have polkit polkit-gnome
and you user is in optical, disks and wheel groups?
for me those above work in every sitation

Can't mount LUKS volume after recent update

Booted up today to kernel error message involving the crypto parameter not being set and there not being a valid LUKS volume. Right I think, massive amounts of cock are about to ensue in a typical Linux update with half the system breaking, but nothing we haven't seen before.
So I boot from a recovery CD, get into the encrypted volumes and update to see if anything b0rked was hotfixed by the devs. Hmm, nothing. It would appear that the cryptsetup params have changed once again, as they are wont to do every few years. We now have a new parameter that must be specified, crypto=:::: by default. Default doesn't work for me since I must have been in a highly delusional paranoid state when I created my partitions I think I used AES when I created it, with TripleDES/Blowfish/Serpent or something along those lines.
I can't seem to find any documentation about the parameter either, the cryptsetup website looks like monkeys with hammers got to it before the devs could fend them off and now the devs are lying on the floor in puddles of monkey semen while their SVN is being pillaged
Does anyone have a quick hint of what needs to be specified to get back into my encrypted root? I don't feel like dredging through half the Internets again, last time it took me a half a day to find out I needed to add the cryptdevice parameter

It would seem the cryptsetup in the initrd image is borked. When it fails to unlock the root partition, it dumps me into the recovery terminal. When I try and run cryptsetup manually from there, it segfaults with the message that it is missing libpopt.so.
I tried with the crypto=ripemd160:"aes-cbc-essiv:sha256":128:1032: parameter (which has to be specified after the cryptdevice= but before the root= parameters - thanks for documenting that ). These parameters are correct for my partition and should unlock it, but fails because cryptsetup is linked against libpopt.so. WTF is that? You'd want a statically linked cryptsetup for your initrd. Who was smoking crack when they wrote the mkinitcpio script? I'm not even sure I need the crypto flag if cryptsetup runs properly.

Can't Mount Windows Partition in OSX After Upgrading to 10.5 and BC 2.0

I just installed Leopard today, using the upgrade option (as opposed to a clean install). I was happy to see that I could boot into Windows still, and installed all of the Boot Camp 2.0 drivers while booted into Vista. However, I can no longer mount my Windows partition in OSX. While using Tiger, I did use MacFuse and ntfs-3g to get read-write support, but in Leopard, I can't even read. When I try to mount the Windows volume in Disk Utility, I get an error stating that it cannot be mounted. I also do not have the option to perform "First Aid" or "Repair" on the volume.
I realize that the latest version of ntfs-3g isn't proven to work with Leopard, but I would at least like read access in OSX. Is it possible that some settings were left over from my Tiger configuration that would not allow Leopard to mount the partition? Any ideas?
Thank you.

Ok. I'm in the club with the same problem...
Strange things:
* For the first days after Leopard's install, my BootCamp disk0s3 partition (I'll name it "BillGates") was mounted correctly. Then, after a few days (but BEFORE upgrading to 10.5.1), it disappeared.
* If I launch DiskUtility "BillGates" is shown, but (in the right device navigation bar) it's named "-n BillGates". If I click the Erase menu, it's named "-nBillGates" (without the space between "-n" and "BillGates"). If I launch SystemProfiler it's named "-n BillGates", but the mount point is "/Volumes/billgates". Can't understand where this "-n" thing is coming from!
* If I try to mount "-n BillGates" from DiskUtility it doesn't work and the log says "Mount of -n BillGates failed".
* In the FSTAB there were no instructions: it was empty.
Now, I tried the MacFUSE-solution: no results (meaning BillGates was not mounted on startup).
I tried the modify-the-FSTAB-solution: no results (with "BillGates", "-n BillGates" nor "-nBillGates".
I tried the chkdsk-solution: all tests were ok, but nothing happened.
The only trick that worked was mounting the partition with Terminal's commands (thanks rtracy!!). It made appear "BillGates" on the desktop (without the "-n thing", that is still present in DiskUtility).
Problem is at the first reboot, the Boot Camp partition disappears again. Any ideas for a permanent fix?!
Giangiacomo.
ADDENDUM: I've tried to move a file from desktop to an unlocked folder in BillGates and System did not copy them. "The item could not be moved because "BillGates" cannot be modified" !!!!!!!!
Message was edited by: Giangiacomo Castelfranchi1

KDE's Dolphin can't mount NTFS partitions after upgrade to systemd

Hi, I just finished to migrate my system to a pure systemd setup. Everithing seems to work fine, except that Dolphin can't mount NTFS partitions anymore, as it was able to do before. I'm not 100% sure that systemd is the culprit, but nevertheless it is a big change in my system so I assume that it may be the problem.
Trying to mount with Dolphin I get this error message:
An error occurred while accessing 'sATA-a', the system responded: The requested operation has failed.: Error mounting: mount exited with exit code 1: helper failed with:
Error opening '/dev/sdb1': Permesso negato
Failed to mount '/dev/sdb1': Permesso negato
Please check '/dev/sdb1' and the ntfs-3g binary permissions,
and the mounting user ID. More explanation is provided at
http://tuxera.com/community/ntfs-3g-faq/#unprivileged
I used to get this kind of error aeons ago when trying to mount from CL; puzzling enough, mounting from CL now works:
$ mount /media/disks/sATA-a
$ ls /media/disks/sATA-a
Documenti Download $RECYCLE.BIN RECYCLER sATA-b System Volume Information Temp Video
This is the relevant entry in my fstab (I don't know if Dolphin cares about it...):
#sATA-a
UUID=D6789B21789B0003 /media/disks/sATA-a ntfs-3g noauto,users 0 0
And finally:
$ ll `which ntfs-3g`
-rwsr-xr-x 1 root root 125K 21 apr 12.13 /bin/ntfs-3g
Can anybody give me a hint? Thanks.

OK, the mess is growing up. Today I switched my laptop to systemd, and the mount problem has appeared on this system as well. So I am confident that this is a systemd-related issue, and maybe some stock Arch config file is broken. I have this entry on my /etc/fstab for the ntfs-3g drive:
UUID=88705BA9705B9D2E /media/vista ntfs-3g noauto,users,exec 0 0
I compiled ntfs-3g with internal fuse support and did the setuid trick:
$ ls -l `which ntfs-3g`
-rwsr-xr-x 1 root root 125K 16 apr 2012 /bin/ntfs-3g
I can mount the disk using the command:
$ mount /media/vista/
$
It works flawlessly, so ntfs-3g works. If I try to mount it with udisks I get:
$ /usr/bin/udisks --mount /dev/sda2 --mount-options users,exec
Mount failed: Error mounting: mount exited with exit code 1: helper failed with:
Error opening '/dev/sda2': Permesso negato
Failed to mount '/dev/sda2': Permesso negato
Please check '/dev/sda2' and the ntfs-3g binary permissions,
and the mounting user ID. More explanation is provided at
http://tuxera.com/community/ntfs-3g-faq/#unprivileged
It sounds to me that udisks is trying to mount the disk as a different user, but I'm not an expert so I might be wrong. If I remove the entry in /etc/fstab then udisks will ask for the password. Repeating the same steps but for an ext3 partition, I am able to mount with udisks when there is a proper fstab entry, and I'm asked for a password when that entry is commented out.
Based on these findings, I strongly suspect that there is some problem with logind configuration in my system. I have been going round and round for hours, serching the web and the wiki (which BTW is in a very bad shape, containing outdated or no informations about mount policies in the polkit and udev sections), and now I feel I need some help to go through it... thanks.

Puzzling problem mounting some partitions from drive connected via airport

I have an external drive with three partitions connected to my airport. Under Tiger, the mounting process for all those partitions was seamless and never failed. As soon as I upgraded to Leopard, however, everything fell apart. Now I can't mount two of the three partitions at all.
When the external drive is connected directly to my MacBook Pro, each partition mounts routinely. When I connect it via my Airport Extreme, the finder window shows that I am connected; but when I attempt to access the partitions on the drive, I get this error message: 'The operation cannot be completed because the original item cannot be found.' I get the same error message for each of the first two partitions on the drive and can mount only the last partition.
When I attempt to mount the partitions manually via the Go menu in the finder, I get essentially the same result: error messages for the first two partitions saying that they cannot be mounted and a normal mounting of the third partition.
Any ideas or clues as to what is actually happening here would be most appreciated. It's very frustrating to have lost access to my backup drive purely by upgrading to Leopard and not find any obvious way to regain it.

Thanks, but I have no problem accessing the drive. All I have to do is plug it directly into my laptop using either USD or Firewire. The problem is with accessing it via Airport so I can run my normal backup routine as I did under Tiger without first a lot of fiddling with cables. After all, the result of installing Leopard shouldn't have been to decrease functionality, should it?
With a direct connection, everything functions normally. With an Airport connection, nothing functions. None of the partitions show up on the desk top, none show up when I run disk utility, and -- as explained before -- I cannot even mount two of the three partitions manually. I've also noticed now that, when I do mount the one partition that will mount, it freezes the finder when I try to unmount it. After that I have to relaunch the finder in order to regain functionality.
It seems pretty obvious that the whole mess is a function of Leopard and Airport somehow, but I'm just at a loss to narrow the problem down any further.

How do I mount a partition at a specific mount point.

How do I mount a partition at a specific mount point? For example I see a Vol01 disk image, which is a partition of one of my hard drives, sitting on my desktop. Under the disk utility it says that its mount point is /Volumes/Vol01. How do I mount this partition as a file system at /Users?
Thanks, much appreciated.

why do you want to do this? it sounds like you want to keep your home directory on an external drive. this can be done without changing the mount point of the external. copy the home directory to the external. then in system preferences preferences->accounts, unlock the lock at the bottom, control-click on your user and select "advanced options." In the resulting popup change the location of the home directory to the external.
in general to change the default mount point of a drive see this link
http://beta.jamesstroud.com/jamess-miscellaneous-how-tos/os-x-admin/os-x-firewir e-mount-point

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).

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

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.

Mount other partitions or hdd

Hello, I'm new in Solaris 8 x86 world and I have a lot of questions.
The most important one right now would be: Can I mount a Windows partition or Linux partition on Solaris 8 x86 and how? How Solaris sees other hdd (partitions and slices)? Ex: I have 2 hdd; I've installed Solaris 8 on Secondary Master (c1d0, I think) and Win98 on Primary Master (c0d0). Now I want to mount Win partition (hdd) in Solaris 8 OS because I'm having some docs & applications there. Any answer or comment is welcome!

R00KIE wrote:You might want to run /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1 which is probably launched by xfce when it starts. polkit-gnome-authentication-agent-1 is provided by polkit-gnome, if you have that installed then that is probably the problem, if you don't have it installed then the problem is something else.
Wow,, Thank u Very much ROOKIE
now i can use my partition again.
Sorry i'm late to reply

[SOLVED] Initramfs fails to properly mount luks partition

Similar Messages

Maybe you are looking for