Quantcast
Channel: Hortonworks » All Replies
Viewing all articles
Browse latest Browse all 3435

Install failures due to efi permissions

$
0
0

I have been encountering multiple installation failures related to failed attempts to chmod or chown files in the /boot/efi file system.

I’m a little confused here: I’ve read that the efi file system is always FAT, which I didn’t think was POSIX-compliant, meaning I didn’t think you could do things like chmod or chown on files in a FAT file system.

This is how /boot/efi is mounted on my system:

[root@compute000 ~]# ssh compute005 ‘grep “/boot/efi” /etc/mtab’
/dev/sda1 /boot/efi vfat rw,uid=0,gid=0,umask=0077,shortname=winnt 0 0
[root@compute000 ~]# ssh compute005 ‘fdisk -l /dev/sda’

Disk /dev/sda: 300.0 GB, 300000000000 bytes
255 heads, 63 sectors/track, 36472 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sda1 1 36473 292968749+ ee GPT

WARNING: GPT (GUID Partition Table) detected on ‘/dev/sda’! The util fdisk doesn’t support GPT. Use GNU Parted.

[root@compute000 ~]# ssh compute005 ‘parted /dev/sda print’
Model: IBM-ESXS AL13SEB300 (scsi)
Disk /dev/sda: 300GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 1049kB 53.5MB 52.4MB fat16 boot
2 53.5MB 322MB 268MB ext3
3 322MB 34.1GB 33.8GB linux-swap(v1)
4 34.1GB 300GB 266GB ext4

Take Falcon for example. The output from the Falcon install shows:

2015-03-05 11:03:30,463 – Changing permission for /boot/efi/hadoop/falcon/data/lineage/graphdb from 700 to 775
2015-03-05 11:03:30,463 – Changing owner for /boot/efi/hadoop/falcon/data/lineage/graphdb from 0 to falcon

But those commands won’t work on this /boot/efi file system:

[root@compute000 ~]# ssh compute005 ‘ls -la /boot/efi/hadoop/falcon’
total 6
drwx—— 3 root root 2048 Mar 5 10:56 .
drwx—— 3 root root 2048 Mar 5 10:56 ..
drwx—— 3 root root 2048 Mar 5 10:56 data
[root@compute000 ~]# ssh compute005 ‘chmod 775 /boot/efi/hadoop/falcon’
[root@compute000 ~]# ssh compute005 ‘ls -la /boot/efi/hadoop/falcon’
total 6
drwx—— 3 root root 2048 Mar 5 10:56 .
drwx—— 3 root root 2048 Mar 5 10:56 ..
drwx—— 3 root root 2048 Mar 5 10:56 data
[root@compute000 ~]# ssh compute005 ‘chown falcon /boot/efi/hadoop/falcon’
chown: changing ownership of `/boot/efi/hadoop/falcon': Operation not permitted

I guess there are 2 possible solutions for this, right?

1) HDP needs to use a different file system because it can’t work with /boot/efi on my cluster the way it expects to.
2) I need to install my nodes differently in a way that permissions in the /boot/efi file system can be modified with commands like chmod and chown.

I’m not sure which is more work for me, but I’m open to suggestions for either approach.

Or an option #3 if anyone has one…

Thanks,

Nate


Viewing all articles
Browse latest Browse all 3435

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>