A
AIS_IT
Hi, and thanks for any suggestions...
Bit of a newbie here, sorry if I mess up the BB Code in places. I'm trying to get 13.10 working with a RAID0 array on a UEFI machine. The array must mount upon boot and be available for installing & executing applications. So I thought to myself "How hard can it be to install Ubuntu onto a RAID array?" Ha.
I tried 60+ hours worth of attempts to install 13.10 onto a preconfigured RAID0 device (two disks). Man, you should see how many times I wrote down the URL for the boot-info page, ha. Dozens of blogs and forum posts to use for self-paced guidance, zero luck. It got to the point where I forgot what different things I had already tried, which sites I had already searched for assistance. Frustration.
Tools that I became sort of familiar with during those attempts include gparted, mdadm, and boot-repair.
Next I tried intalling 13.10 using a small set of partitions on just sda (EFI and / and swap plus a large unallocated section left for subsequent RAID0 configuration). Installation went well.
Next I tried creating an ext4 partition on sdb using all its space, as well as an ext4 partition on the unused space of sda. No problem.
Next I tried creating a RAID0 array combining the two large (ext4) partitions on sda and sdb. Success.
Next I sudo-created a directory under / called "WOWZA."
Next I added the following line to my fstab file:
Code:
UUID=blah-blah /WOWZA ext4 rw,auto,dev,exec,suid,user 0 2
(quite unsure about those mount options and would appreciate feedback)
Next I rebooted, and found the directory /WOWZA which appeared to have quite a large amount of available space. Getting there.
Then I realized that I couldn't write anything to the /WOWZA directory. Thought I was so close.
I tried to chmod that directory. Here's what ls -l / now says:
Code:
total 100
drwxr-xr-x 2 root root 4096 Feb 13 20:38 bin
drwxr-xr-x 4 root root 4096 Feb 13 20:41 boot
drwxr-xr-x 2 root root 4096 Feb 13 20:10 cdrom
drwxr-xr-x 18 root root 4320 Feb 13 22:10 dev
drwxr-xr-x 132 root root 12288 Feb 13 22:06 etc
drwxr-xr-x 3 root root 4096 Feb 13 20:12 home
lrwxrwxrwx 1 root root 33 Feb 13 20:16 initrd.img -> boot/initrd.img-3.11.0-12-generic
lrwxrwxrwx 1 root root 34 Feb 13 20:15 initrd.img.old -> /boot/initrd.img-3.11.0-15-generic
drwxr-xr-x 23 root root 4096 Feb 13 20:18 lib
drwxr-xr-x 2 root root 4096 Oct 16 11:58 lib64
drwx------ 2 root root 16384 Feb 13 20:08 lost+found
drwxr-xr-x 3 root root 4096 Feb 13 20:51 media
drwxr-xr-x 2 root root 4096 Oct 13 13:41 mnt
drwxr-xr-x 2 root root 4096 Oct 16 11:58 opt
dr-xr-xr-x 276 root root 0 Feb 13 22:05 proc
drwx------ 3 root root 4096 Feb 13 20:20 root
drwxr-xr-x 22 root root 720 Feb 14 07:55 run
drwxr-xr-x 2 root root 12288 Feb 13 20:37 sbin
drwxr-xr-x 2 root root 4096 Oct 16 11:58 srv
dr-xr-xr-x 13 root root 0 Feb 13 22:05 sys
drwxrwxrwt 8 root root 4096 Feb 14 11:37 tmp
drwxr-xr-x 10 root root 4096 Oct 16 11:58 usr
drwxr-xr-x 13 root root 4096 Oct 16 12:05 var
lrwxrwxrwx 1 root root 30 Feb 13 20:16 vmlinuz -> boot/vmlinuz-3.11.0-12-generic
drwxr-xr-x 3 root root 4096 Feb 13 21:04 WOWZA
Here is what sudo fdisk -l returns:
Code:
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 1 976773167 488386583+ ee GPT
Partition 1 does not start on physical sector boundary.
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 976773167 488386583+ ee GPT
Partition 1 does not start on physical sector boundary.
Disk /dev/md127: 948.1 GB, 948146536448 bytes
255 heads, 63 sectors/track, 115272 cylinders, total 1851848704 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/md127p1 1 1851848703 925924351+ ee GPT
Partition 1 does not start on physical sector boundary.
Here is what df -hT returns:
Code:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda2 ext4 20G 3.8G 15G 21% /
none tmpfs 4.0K 0 4.0K 0% /sys/fs/cgroup
udev devtmpfs 7.4G 8.0K 7.4G 1% /dev
tmpfs tmpfs 1.5G 1.2M 1.5G 1% /run
none tmpfs 5.0M 0 5.0M 0% /run/lock
none tmpfs 7.4G 228K 7.4G 1% /run/shm
none tmpfs 100M 108K 100M 1% /run/user
/dev/sda1 vfat 500M 3.3M 496M 1% /boot/efi
/dev/md127p1 ext4 870G 72M 825G 1% /WOWZA
none tmpfs 7.4G 1.5M 7.4G 1% /tmp/guest-xHXsmb
Here is what mount | column -t returns:
Code:
/dev/sda2 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
none on /sys/firmware/efi/efivars type efivarfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
none on /sys/fs/pstore type pstore (rw)
/dev/sda1 on /boot/efi type vfat (rw)
/dev/md127p1 on /WOWZA type ext4 (rw,noexec,nosuid,nodev)
systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd)
none on /tmp/guest-xHXsmb type tmpfs (rw,mode=700)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=it-admin)
gvfsd-fuse on /home/it-admin/.gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev)
After that last command I noticed that my /dev/md127p1 partition is mounted on /WOWZA as noexec, although I specified "exec" as part of my fstab entry. Is that entry in fstab doing anything at all for me?
That's not the question, though, that I came here to ask. My real question is: how the heck do I get this working the way I want? Please inform me of other screen outputs that might provide useful information, and thanks for any offered help. Here's the link to the latest boot-info output:
ubuntu dot com slash 6934120
Continue reading...
Bit of a newbie here, sorry if I mess up the BB Code in places. I'm trying to get 13.10 working with a RAID0 array on a UEFI machine. The array must mount upon boot and be available for installing & executing applications. So I thought to myself "How hard can it be to install Ubuntu onto a RAID array?" Ha.
I tried 60+ hours worth of attempts to install 13.10 onto a preconfigured RAID0 device (two disks). Man, you should see how many times I wrote down the URL for the boot-info page, ha. Dozens of blogs and forum posts to use for self-paced guidance, zero luck. It got to the point where I forgot what different things I had already tried, which sites I had already searched for assistance. Frustration.
Tools that I became sort of familiar with during those attempts include gparted, mdadm, and boot-repair.
Next I tried intalling 13.10 using a small set of partitions on just sda (EFI and / and swap plus a large unallocated section left for subsequent RAID0 configuration). Installation went well.
Next I tried creating an ext4 partition on sdb using all its space, as well as an ext4 partition on the unused space of sda. No problem.
Next I tried creating a RAID0 array combining the two large (ext4) partitions on sda and sdb. Success.
Next I sudo-created a directory under / called "WOWZA."
Next I added the following line to my fstab file:
Code:
UUID=blah-blah /WOWZA ext4 rw,auto,dev,exec,suid,user 0 2
(quite unsure about those mount options and would appreciate feedback)
Next I rebooted, and found the directory /WOWZA which appeared to have quite a large amount of available space. Getting there.
Then I realized that I couldn't write anything to the /WOWZA directory. Thought I was so close.
I tried to chmod that directory. Here's what ls -l / now says:
Code:
total 100
drwxr-xr-x 2 root root 4096 Feb 13 20:38 bin
drwxr-xr-x 4 root root 4096 Feb 13 20:41 boot
drwxr-xr-x 2 root root 4096 Feb 13 20:10 cdrom
drwxr-xr-x 18 root root 4320 Feb 13 22:10 dev
drwxr-xr-x 132 root root 12288 Feb 13 22:06 etc
drwxr-xr-x 3 root root 4096 Feb 13 20:12 home
lrwxrwxrwx 1 root root 33 Feb 13 20:16 initrd.img -> boot/initrd.img-3.11.0-12-generic
lrwxrwxrwx 1 root root 34 Feb 13 20:15 initrd.img.old -> /boot/initrd.img-3.11.0-15-generic
drwxr-xr-x 23 root root 4096 Feb 13 20:18 lib
drwxr-xr-x 2 root root 4096 Oct 16 11:58 lib64
drwx------ 2 root root 16384 Feb 13 20:08 lost+found
drwxr-xr-x 3 root root 4096 Feb 13 20:51 media
drwxr-xr-x 2 root root 4096 Oct 13 13:41 mnt
drwxr-xr-x 2 root root 4096 Oct 16 11:58 opt
dr-xr-xr-x 276 root root 0 Feb 13 22:05 proc
drwx------ 3 root root 4096 Feb 13 20:20 root
drwxr-xr-x 22 root root 720 Feb 14 07:55 run
drwxr-xr-x 2 root root 12288 Feb 13 20:37 sbin
drwxr-xr-x 2 root root 4096 Oct 16 11:58 srv
dr-xr-xr-x 13 root root 0 Feb 13 22:05 sys
drwxrwxrwt 8 root root 4096 Feb 14 11:37 tmp
drwxr-xr-x 10 root root 4096 Oct 16 11:58 usr
drwxr-xr-x 13 root root 4096 Oct 16 12:05 var
lrwxrwxrwx 1 root root 30 Feb 13 20:16 vmlinuz -> boot/vmlinuz-3.11.0-12-generic
drwxr-xr-x 3 root root 4096 Feb 13 21:04 WOWZA
Here is what sudo fdisk -l returns:
Code:
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 1 976773167 488386583+ ee GPT
Partition 1 does not start on physical sector boundary.
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 976773167 488386583+ ee GPT
Partition 1 does not start on physical sector boundary.
Disk /dev/md127: 948.1 GB, 948146536448 bytes
255 heads, 63 sectors/track, 115272 cylinders, total 1851848704 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/md127p1 1 1851848703 925924351+ ee GPT
Partition 1 does not start on physical sector boundary.
Here is what df -hT returns:
Code:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda2 ext4 20G 3.8G 15G 21% /
none tmpfs 4.0K 0 4.0K 0% /sys/fs/cgroup
udev devtmpfs 7.4G 8.0K 7.4G 1% /dev
tmpfs tmpfs 1.5G 1.2M 1.5G 1% /run
none tmpfs 5.0M 0 5.0M 0% /run/lock
none tmpfs 7.4G 228K 7.4G 1% /run/shm
none tmpfs 100M 108K 100M 1% /run/user
/dev/sda1 vfat 500M 3.3M 496M 1% /boot/efi
/dev/md127p1 ext4 870G 72M 825G 1% /WOWZA
none tmpfs 7.4G 1.5M 7.4G 1% /tmp/guest-xHXsmb
Here is what mount | column -t returns:
Code:
/dev/sda2 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
none on /sys/firmware/efi/efivars type efivarfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
none on /sys/fs/pstore type pstore (rw)
/dev/sda1 on /boot/efi type vfat (rw)
/dev/md127p1 on /WOWZA type ext4 (rw,noexec,nosuid,nodev)
systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd)
none on /tmp/guest-xHXsmb type tmpfs (rw,mode=700)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=it-admin)
gvfsd-fuse on /home/it-admin/.gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev)
After that last command I noticed that my /dev/md127p1 partition is mounted on /WOWZA as noexec, although I specified "exec" as part of my fstab entry. Is that entry in fstab doing anything at all for me?
That's not the question, though, that I came here to ask. My real question is: how the heck do I get this working the way I want? Please inform me of other screen outputs that might provide useful information, and thanks for any offered help. Here's the link to the latest boot-info output:
ubuntu dot com slash 6934120
Continue reading...
