Welcome
Welcome to refracta

You are currently viewing our boards as a guest, which gives you limited access to view most discussions and access our other features. By joining our free community, you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content, and access many other special features. In addition, registered members also see less advertisements. Registration is fast, simple, and absolutely free, so please, join our community today!

Fstab and UUID in refracta installer

Refracta Development, Scripts, etc.

Re: Fstab and UUID in refracta installer

Postby fsmithred » Mon May 28, 2012 1:09 pm

Seem to have fixed the problem of the blank uuid for /boot. I replaced lines like
Code: Select all
install_part="UUID=$(blkid $install_dev | awk -F"\""  '{ print $2 }')"
with this
Code: Select all
install_part="$(blkid -s UUID $install_dev | awk '{ print $2 }')"
(It works for me without the '-s UUID' but that option should eliminate any problems with fields
that move around.)

Today's changes (20120528) are in refractainstaller-test in github.
User avatar
fsmithred
 
Posts: 2101
Joined: Wed Mar 09, 2011 9:13 pm

Re: Fstab and UUID in refracta installer

Postby fsmithred » Mon May 28, 2012 1:21 pm

dzz wrote:I'm still looking at what can be done as normal user, to make a gui (p)mount script, as the xfce mount plugin is not very good.


Did this one a few months ago after you showed my your configure-mounts.sh. Maybe something in it will be useful.
https://github.com/fsmithred/scripts/bl ... rypto03.sh
User avatar
fsmithred
 
Posts: 2101
Joined: Wed Mar 09, 2011 9:13 pm

Re: Fstab and UUID in refracta installer

Postby dzz » Mon May 28, 2012 1:38 pm

Here's my blkid output. What does yours look like?



Code: Select all
# blkid
/dev/sda10: LABEL="test2" UUID="4ad37613-c48e-4d53-837c-e71d6ed4717c" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda9: LABEL="exe-test" UUID="9458410b-bb0a-4287-9cd7-96169a782399" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdc1: LABEL="hitachi-sidux" UUID="e66f2c63-12f5-4feb-b108-87919a1942c7" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdd3: LABEL="ru-data" UUID="c33f2b75-024d-48f4-93cb-d0bb57946609" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda2: LABEL="service" UUID="50daa78d-6dbf-43bc-9b8c-5bcb264c61b8" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda3: LABEL="exegnu" UUID="8bc751d9-ffca-4dcd-8fd3-8c99413ac408" TYPE="ext3"
/dev/sda12: LABEL="test3" UUID="f01f3f96-2abc-45a3-ba2f-e8794a5d83de" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb9: LABEL="hda9" UUID="fab0fb96-f4f8-469a-a915-309ae654f92d" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb10: LABEL="hda10" UUID="46553eba-e66c-4c22-8ac5-aaf725002d38" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb11: LABEL="hda11" UUID="3e84e97c-5e9e-4349-9e1f-3a4fdc4c238c" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdd2: UUID="a9f2b3f3-43e6-4bdd-b9ed-6b256fec6fa3" TYPE="crypto_LUKS"
/dev/sdc5: LABEL="swap" UUID="aaeb69bc-9238-4d63-8deb-23d6df2d3f0f" TYPE="swap"
/dev/sdc6: LABEL="hitachi-6" UUID="dc7ae551-1df8-4c3a-8f05-5523360c264e" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdc7: LABEL="hitachi-7" UUID="a8722e9d-0a8d-4da8-b5a5-cf2b346c9f84" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdc8: LABEL="hitachi-8" UUID="78cdf475-d8e4-47ac-998d-f866be5798d7" TYPE="ext4"
/dev/sda1: LABEL="xp" UUID="A0A4ED1EA4ECF824" TYPE="ntfs"
/dev/sda5: LABEL="swap" UUID="764d2c8f-7bad-4fe2-b9f3-e3b5ad0cb8be" TYPE="swap"
/dev/sda6: LABEL="refracta" UUID="704ff683-0983-416c-a22b-2f7d82eb3636" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda7: LABEL="wheezy" UUID="2cf004b0-b9dc-4dc0-bad0-7c68a34e74c8" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda8: LABEL="sid" UUID="ed4c2033-26e0-46f6-8b51-c20b1a2008fe" TYPE="ext4"
/dev/sda11: LABEL="tera" UUID="86326016-c65b-4874-a91a-0cedf20f7c16" TYPE="ext4"
/dev/sdb1: LABEL="WIND98" UUID="4220-8C9F" TYPE="vfat"
/dev/sdb5: LABEL="WIND2K" UUID="2E12-1B09" TYPE="vfat"
/dev/sdb6: LABEL="wd-xp" UUID="ECB49D96B49D643C" TYPE="ntfs"
/dev/sdb7: LABEL="WD-DATA" UUID="FF10-27CC" TYPE="vfat"
/dev/sdb8: LABEL="wd-swap" UUID="78559712-3259-4adc-a5dc-90fa0858045d" TYPE="swap"
/dev/sdd1: LABEL="ru-1" UUID="5b636931-fba0-44a2-acba-7f2d0b92e9b8" SEC_TYPE="ext2" TYPE="ext3"


See what I mean? It's true youcan't trust the tag order. Note one part is unlabelled, so uuid appears in column 2 unlike the others

BTW Thanks for the mount script, I have that already, I thought it was just for luks. I'm working on one to list and mount unencrypted parts quickly so I don't need to automount eveything, using pmount if it is not in fstab else normal mount.
Last edited by dzz on Mon May 28, 2012 2:00 pm, edited 1 time in total.
dzz
 
Posts: 647
Joined: Wed Apr 27, 2011 11:53 am
Location: Devon, England

Re: Fstab and UUID in refracta installer

Postby fsmithred » Mon May 28, 2012 1:57 pm

That's weird. Well, I think adding the -s option eliminates the problem. Hope so, anyway. Nadir and I are in IRC right now, testing the script. Join us if you can.
User avatar
fsmithred
 
Posts: 2101
Joined: Wed Mar 09, 2011 9:13 pm

Re: Fstab and UUID in refracta installer

Postby fsmithred » Wed May 30, 2012 2:31 am

Couple of quick notes:

The order of the fields in the blkid output seems to be related to whether the partition was labeled with gparted (LABEL is in second field) or with e2label (LABEL is in last field).

Can't seem to get refractainstaller to work with encryption and uuid. Boot fails with error: "cryptsetup: evms_activate is not available”" which appears to be a bug. Looks like it's mostly affecting people using encrypted lvm.

Encrypted install works fine with 9.0.2 and 9.0.3. Encrypted install with uuid in 9.0.5 completes without error, but the installed system won't boot. Encrypted install in 9.0.2 with uuids added after first boot will no longer boot. Get the same error.
User avatar
fsmithred
 
Posts: 2101
Joined: Wed Mar 09, 2011 9:13 pm

Re: Fstab and UUID in refracta installer

Postby nadir » Wed May 30, 2012 4:11 pm

fsmithred wrote: Encrypted install with uuid in 9.0.5 completes without error, but the installed system won't boot. Encrypted install in 9.0.2 with uuids added after first boot will no longer boot. Get the same error.

Same problem here, and even a bit worse.
I also run into a problem with locales:
after the boot screen i get the info
"filesystem root/fs"
is not found, not "filesystem root-fs" is not found.

chrooted into it, changed locales and then, next boot, ran into busybox.
I checked /etc/crybttab and blik and such, and all seems to be ok
I also ran "update-initramfs -u all -k" and "update-grub", but to no avail.
To be honest: no idea.
So i herd u liek mudkip?
User avatar
nadir
 
Posts: 1160
Joined: Wed Mar 09, 2011 4:18 am
Location: here

Re: Fstab and UUID in refracta installer

Postby dzz » Thu May 31, 2012 10:43 am

The order of the fields in the blkid output seems to be related to whether the partition was labeled with gparted (LABEL is in second field) or with e2label (LABEL is in last field)


I got some empty "reserved" ext3/4 partitions. They were all first created with gparted. I renamed one (using a non-Refracta squeeze system) with e2label.

Here the new label shows second in blkid output, even after deleting the cache. In both (newly-installed) Refracta and other Debian.

I don't doubt for a moment you observed it different... that's my point, blkid output column order can't be trusted. Getting it down to 2 columns using "-s" seems a good plan.
dzz
 
Posts: 647
Joined: Wed Apr 27, 2011 11:53 am
Location: Devon, England

Re: Fstab and UUID in refracta installer

Postby fsmithred » Sun Jun 03, 2012 12:48 pm

Forgot to mention that I also tried it with disk labels. Well, I got as far as attempting to put a disk label on an encrypted partition, and e2label complained about a bad superblock. I guess it needs to see the ext filesystem before it can label it.

One solution would be for the script to allow using uuids only if the partition is not encrypted. I haven't thought about how to fit that into the script, but it shouldn't be too difficult.
User avatar
fsmithred
 
Posts: 2101
Joined: Wed Mar 09, 2011 9:13 pm

Re: Fstab and UUID in refracta installer

Postby dzz » Sun Jun 03, 2012 6:04 pm

Far as I know (or thought I did) it's a filesystem rather than a partition gets labelled. If so a LUKS partition can't be labelled as it is a "container" rather than an actual filesystem itself. But of course, it has a UUID.

I can't help much with LUKS... I try to learn it more, then get defeated because I always forget the passphrase!
dzz
 
Posts: 647
Joined: Wed Apr 27, 2011 11:53 am
Location: Devon, England

Re: Fstab and UUID in refracta installer

Postby fsmithred » Tue Jun 12, 2012 5:33 pm

New version of refractainstaller-base -
http://distro.ibiblio.org/pub/linux/dis ... .4_all.deb

It allows you to use uuids in fstab only if you're not using encryption.
You can change the hostname on the installed system. (so you don't have eight hosts named 'refracta' on your local network like I do.)
Autologin is desbled for gdm, gdm3, kdm (kde3 or kde4), trinity, lightdm. (kde and trinity code lifted from exelinux-installer.) This might be needed in refracta-wheezy. Right now, I'm playing with lightdm, and I'm liking it.
User avatar
fsmithred
 
Posts: 2101
Joined: Wed Mar 09, 2011 9:13 pm

PreviousNext

Return to Discuss

Who is online

Users browsing this forum: No registered users and 0 guests

cron
suspicion-preferred