[arch-general] arch install issues with 2013.09 iso & vfat device
Dear all, this is my second arch install this month (archlinux-2013.09.01-dual.iso) on an usb key to get a live Arch. Both installs failed on a vfat formated device, when they succed on ext2. $ pacstrap /mnt base returns lot of these erros: warning: warning given when extracting usr/bin/vgrename (Can't create '/mnt/usr/bin/vgrename') ...... It seems, even in chroot, that I can't write the vfat formated device I would like to use vfat as these keys are aimed to boot Arch from windows machines and share files. I used gdisk and fdisk to partition, then mkfs.vfat to format, on clean usb keys. Is there anything I missed ? Then, there is an issue with package vi: error: could not open file /mnt/var/cache/pacman/pkg/vi-1:050325-3-x86_64.pkg.tar.xz.part: Invalid argument I first # pacman-key --init && pacman-key --populate archlinux and # pacman -Syy The only way to succed the install was : # pacstrap -i /mnt base --ignore vi I must add that earlier installs with earlier iso did not show this issue. Maybe shall I open a bug report, or is this a known issue ? Last, the above command returns : :: vi is in IgnorePkg/IgnoreGroup. Install anyway? [Y/n] It seems weird to me that default is Yes, as I specified --ignore vi. Would' nt it makes more sense to default No ? Regards.
Op 17 sep. 2013 00:06 schreef "arnaud gaboury" <arnaud.gaboury@gmail.com> het volgende:
Dear all,
this is my second arch install this month (archlinux-2013.09.01-dual.iso) on an usb key to get a live Arch. Both installs failed on a vfat formated device, when they succed on ext2.
You didn't specify, but i guess (hope) that it's the usb stick that is holding the vfat? In that case: it sounds like it developed some bitrot. Try scanning it for badblocks or use another stick. Mvg, Guus
On Tue, Sep 17, 2013 at 1:12 AM, Guus Snijders <gsnijders@gmail.com> wrote:
Op 17 sep. 2013 00:06 schreef "arnaud gaboury" <arnaud.gaboury@gmail.com> het volgende:
You didn't specify, but i guess (hope) that it's the usb stick that is holding the vfat? In that case: it sounds like it developed some bitrot. Try scanning it for badblocks or use another stick.
Mvg, Guus
# lsblk .... sdd ├─sdd1 ├─sdd2 vfat 1E42-C6EA /arch/mnt └─sdd3 ext2 563350c7-4f58-43c1-b9a2-eb74cd4b6894 # mount -t vfat /dev/sdd2 /mnt # pacstrap -i /mnt base --ignore vi Both keys were new and cleanly formated. I would say it is more a permission story, even if I can nano/mkdir...
from mkfs.vfat(8) : *mkdosfs* can not create boot-able file systems. This isn't as easy as you might think at first glance for various reasons and has been discussed a lot already. *mkdosfs* simply will not support it ;) So no interest. Back to ext2.
On 17.09.13 at 0:06, arnaud gaboury wrote:
Dear all,
this is my second arch install this month (archlinux-2013.09.01-dual.iso) on an usb key to get a live Arch. Both installs failed on a vfat formated device, when they succed on ext2. $ pacstrap /mnt base returns lot of these erros: warning: warning given when extracting usr/bin/vgrename (Can't create '/mnt/usr/bin/vgrename') ......
It seems, even in chroot, that I can't write the vfat formated device
I would like to use vfat as these keys are aimed to boot Arch from windows machines and share files. I used gdisk and fdisk to partition, then mkfs.vfat to format, on clean usb keys. Is there anything I missed ?
Then, there is an issue with package vi: error: could not open file /mnt/var/cache/pacman/pkg/vi-1:050325-3-x86_64.pkg.tar.xz.part: Invalid argument I first # pacman-key --init && pacman-key --populate archlinux and # pacman -Syy
The only way to succed the install was : # pacstrap -i /mnt base --ignore vi
I must add that earlier installs with earlier iso did not show this issue. Maybe shall I open a bug report, or is this a known issue ?
Last, the above command returns : :: vi is in IgnorePkg/IgnoreGroup. Install anyway? [Y/n]
It seems weird to me that default is Yes, as I specified --ignore vi. Would' nt it makes more sense to default No ?
Regards.
vfat has a lot of reserved characters: https://en.wikipedia.org/wiki/Filename#Comparison_of_filename_limitations Note the colon (':') in "vi-1:050325-3-x86_64.pkg.tar.xz.part", don't know why it couldn't write "/mnt/usr/bin/vgrename". Regards, Jakub Klinkovský (Lahwaacz)
On Tue, Sep 17, 2013 at 8:12 AM, Jakub Klinkovský <kuba.klinkovsky@gmail.com
wrote:
vfat has a lot of reserved characters:
https://en.wikipedia.org/wiki/Filename#Comparison_of_filename_limitations
Note the colon (':') in "vi-1:050325-3-x86_64.pkg.tar.xz.part", don't know why it couldn't write "/mnt/usr/bin/vgrename".
Regards, Jakub Klinkovský (Lahwaacz)
I had the same issue with the vi package when installing on ext2. As for vfat. I have no idea why I can't install Arch on this filesystem.
Am 17.09.2013 15:15, schrieb arnaud gaboury:
On Tue, Sep 17, 2013 at 8:12 AM, Jakub Klinkovský <kuba.klinkovsky@gmail.com
wrote: vfat has a lot of reserved characters: https://en.wikipedia.org/wiki/Filename#Comparison_of_filename_limitations
Note the colon (':') in "vi-1:050325-3-x86_64.pkg.tar.xz.part", don't know why it couldn't write "/mnt/usr/bin/vgrename".
Regards, Jakub Klinkovský (Lahwaacz)
I had the same issue with the vi package when installing on ext2. As for vfat. I have no idea why I can't install Arch on this filesystem. Do not install arch / on vfat it will not work. It's too limited.
greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
On Tue, Sep 17, 2013 at 8:12 AM, Jakub Klinkovský <kuba.klinkovsky@gmail.com
wrote:
On 17.09.13 at 0:06, arnaud gaboury wrote:
Dear all,
this is my second arch install this month (archlinux-2013.09.01-dual.iso) on an usb key to get a live Arch. Both installs failed on a vfat formated device, when they succed on ext2. $ pacstrap /mnt base returns lot of these erros: warning: warning given when extracting usr/bin/vgrename (Can't create '/mnt/usr/bin/vgrename') ......
It seems, even in chroot, that I can't write the vfat formated device
I would like to use vfat as these keys are aimed to boot Arch from windows machines and share files. I used gdisk and fdisk to partition, then mkfs.vfat to format, on clean usb keys. Is there anything I missed ?
Then, there is an issue with package vi: error: could not open file /mnt/var/cache/pacman/pkg/vi-1:050325-3-x86_64.pkg.tar.xz.part: Invalid argument I first # pacman-key --init && pacman-key --populate archlinux and # pacman -Syy
The only way to succed the install was : # pacstrap -i /mnt base --ignore vi
I must add that earlier installs with earlier iso did not show this issue. Maybe shall I open a bug report, or is this a known issue ?
Last, the above command returns : :: vi is in IgnorePkg/IgnoreGroup. Install anyway? [Y/n]
It seems weird to me that default is Yes, as I specified --ignore vi. Would' nt it makes more sense to default No ?
Regards.
vfat has a lot of reserved characters: https://en.wikipedia.org/wiki/Filename#Comparison_of_filename_limitations
Note the colon (':') in "vi-1:050325-3-x86_64.pkg.tar.xz.part", don't know why it couldn't write "/mnt/usr/bin/vgrename".
Probably because it is a symbolic link, and those are not supported in vfat. And there are far more important symbolic links out there...
participants (5)
-
arnaud gaboury
-
Guus Snijders
-
Jakub Klinkovský
-
Rodrigo Rivas
-
Tobias Powalowski