[02:34] rcy (~rcy@209.90.176.121) joined #fai. [04:38] jair_ (~jair@adsl-67-36-185-84.dsl.chcgil.ameritech.net) joined #fai. [04:42] jair (~jair@adsl-67-36-182-169.dsl.chcgil.ameritech.net) left irc: Ping timeout: 480 seconds [05:21] MT (~MT@dove.informatik.tu-muenchen.de) joined #fai. [05:37] MT (~MT@dove.informatik.tu-muenchen.de) left irc: Ping timeout: 480 seconds [06:14] MT (~MT@dove.informatik.tu-muenchen.de) joined #fai. [06:29] sep (~sep@40.211.jostedal.no) joined #fai. [07:14] ErKa (keryell@m5.wifi.enstb.org) joined #fai. [08:04] serieus (~serieus@office.nedstat.nl) joined #fai. [08:04] I want help with the problem described on the following url: https://lists.uni-koeln.de/pipermail/linux-fai/2007-August/005283.html [08:05] Does anybody know the solution for this problem ? The author of this thread won't respond, and i'm out of possible options :-) [08:07] so what exactly is your problem? [08:08] My problem is that i'm getting the same error, but can't figure out which parameter in the fai.conf is causing or will solve this [08:08] The log files come up with an error that it can't find the package linux-image-486 [08:08] please paste your fai.conf to paste.debian.net [08:08] one moment [08:10] http://paste.debian.net/39174 [08:11] It's pretty standard [08:22] which architecture are you using? [08:23] amd64 [08:23] On both, the install server and the client [08:30] hmm, then probably there is no such package as linux-image-486 [08:31] (just a blind guess) [08:31] is this http://faiwiki.informatik.uni-koeln.de/index.php/Setup_harddisks_2 about the best docs ill find for setup_harddisk2 ? [08:34] MT (~MT@dove.informatik.tu-muenchen.de) left irc: Remote host closed the connection [08:34] MT (~MT@dove.informatik.tu-muenchen.de) joined #fai. [08:34] sep, yes, actually it is [08:34] and probably this channel :-) [08:35] MT the examples in the svn helped a lot :) [08:40] Mrfai (~lange@suenner.informatik.uni-koeln.de) joined #fai. [08:44] Bokeh (~blaat@berchem.lorentz.leidenuniv.nl) joined #fai. [08:45] morning [08:46] just in case someone's awake at this early hour, but i'm having the following problem with fai: when i try to install ubuntu gutsy, the /var/lib/fai/config/class nfs mount won't work. [08:46] i already installed nfs-common in the nfsroot, solving the first problem [08:46] however, now nfsmount requires me to either mount with -o nolock or start rpc.statd [08:46] which FAI version are you using? [08:47] 1 sec [08:47] 3.2.1 [08:47] is there a simple solution, is it a known bug or will i have to hack the -o nolock option into the nfsroot's init.d [08:49] Have a look at http://faiwiki.informatik.uni-koeln.de/index.php/UbuntuTeam [08:49] There's a ubuntu version of 3.2.1 [08:49] a gutsy ppa package [08:50] cool [08:50] let me see how that works out [08:51] hmm..... that's the development tree though, do you know anything about how stable it is? [08:52] it's the stable version for gutsy [09:00] MT: sollte es möglich sein auch lvm volumen als unveränderlich zu markieren? [09:02] meinst mit preserve? [09:12] cheers [09:13] the packages from launchpad worked [09:41] MT: ja, preserve [09:41] da sollte das dann halt einfach nur "preserve" heißen [09:42] also auch dort statt der size [09:42] MT: ich frage weil das auswirkungen auf die darunterliegenden platten hat [09:43] warum das? [09:43] MT: ein "preserve" auf ein raid oder lvm würde auch "preserv" für alle beteiligten partitionen und ev. platten bedeuten. [09:44] hmm, ja [09:44] ansonsten finde ich dein teil dass du da gebaut hast ziemlich beeindruckend [09:44] MT (~MT@dove.informatik.tu-muenchen.de) left irc: Read error: Connection reset by peer [09:44] schade... :-) [09:45] MT (~MT@dove.informatik.tu-muenchen.de) joined #fai. [09:49] umm when i use vg vg_system sda2 in order to make a lvm it fail, but vg system sda2 works. is it prohibited to use vg_ in a volumegroup name ? vg_system is the default vg name in a debian-edu installation [09:51] MT: wie kann man denn lösen dass die bootreihenfolge der devices sich ändert? [09:51] also i use disk_config disk1 in order to partition the first disk. is there any way i can omit using sda2 to specify the pv's hda2 | sda2 | c0d0p2 [09:51] also sda sdb sdc sdd das nächste mal nicht in dieser reihenfolge erkannt werden muss [09:57] does anyone know where Michael Tautschnig prefers comments or bugs on setup_harddrive2 ? [09:58] sep: you work on that one too? [09:58] sep: me too [09:58] stockholm, i only try to use it [09:58] sep: and how are you doing? [09:58] what kind of issue do you see? [09:58] i think i notice a oddity [09:58] Action: stockholm noticed several :-) [10:01] sep, comments either via ICQ or probably better via the mailing list [10:01] sorry, meant IRC instead of ICQ [10:02] meandtheshell (~markus@85.127.118.147) joined #fai. [10:05] MT: weisst du wie man disk-ids in das system reinbekommen könnte om eine reproduzierbare bootreihenfolge zu garantieren? [10:05] in das - welches - system? [10:06] später, booten? [10:06] oder in setup_harddisks? [10:07] stockholm, that i can not start the volumegroup name with vg_[name] [10:07] oh, does that confuse the parser? [10:08] i tried vg_system, and it said in the fai.log Volume group _system allready exsist. [10:08] MT: setup Hardsist muss das ja ermöglichen und einrichten! [10:08] using only system or any other name that dont start with vg is ok [10:09] also das sollte es schon können [10:09] stockholm: das muss man noch mit nem hook machen [10:09] geht derzeit so noch nicht [10:09] im neuen schon [10:09] o gott, echt? [10:09] mach mal disk_config disk1 fstabkey:uuid [10:09] dann muss ich ja meine config ändern! ;) [10:09] also setup_harddisks_2 kann es... [10:10] nur die grub-config dürfte noch ein Problem sein [10:10] hook. [10:10] da muss man AFAIK auch root=UUID=... haben [10:10] hook und initrd [10:10] ich hab da einfach ein preinst bei menu.lst dabei [10:11] aber die fstab sollte setup_harddisks_2 schon richtig mit UUIDs erzeugen [10:15] also http://faiwiki.informatik.uni-koeln.de/index.php/Setup_harddisks_2 might mention that you need dm_mod personally i added a modprobe in partition. but i'm sure there are more corerct ways [10:16] stockholm, other then that it seams to work for me atm [10:16] sep, could you change line 451 in shdd2-parser [10:17] to volume: /^vg\s+/ name devices [10:17] this should do the trick [10:17] MT sure, let me try [10:17] in fact, it would be cool if you could test whether this then works with vg_system [10:18] test is in progress [10:18] thanks, sep [10:18] I also updated the wiki page [10:19] added the modprobe dm_mod to the hook [10:19] very nice [10:21] from my previous test i notice that my lvm swap is correcty craeted as a lv swap , but no fstab entry is written. ? i use vg_system-swap - 512 swap - [10:21] hmm, probably a bug :-) [10:22] a bug! a bug! :) [10:23] ErKa (keryell@m5.wifi.enstb.org) left irc: Ping timeout: 480 seconds [10:23] MT, test failed i used vg vg_system sda2 [10:23] (CMD) vgdisplay -s 1> /tmp/zGDqmuYLjB 2> /tmp/f6mJjzOwY4 [10:23] Unexpected vgdisplay output "system" 11.76 GB [10.93 GB used / 848.00 MB free] [10:26] ok, well :-) [10:26] it seems to accept your name vg_system, which is the good news [10:26] but the parser of vgdisplay output is broken [10:27] let me see whether I can fix that [10:27] mom ... [10:28] ok, sep, about the swap <-> fstab problem [10:32] its a bug in sshd2-fstab [10:32] it silently skips all partitions without a mountpoint [10:32] thus including swaps [10:32] I won't be able to fix this right now, I'll look into it this evening [10:33] so, let's go for the vgdisplay thing [10:34] sure [10:35] ok, its about the MB/GB [10:35] I was only expecting GB [10:35] not 848.00 MB [10:35] MT, what about TB ? [10:35] no idea whether lvm displays this [10:36] actually I had no idea whether vgdisplay was using GB only or MB, TB [10:37] ok, could you please change line 379 of shdd2-volumes [10:37] ( $line =~ /^\s*"(\S+)"\s+\d+\.\d+ [MGT]B\s+\[\d+\.\d+ [MGT]B\s+used \/ \d+\.\d+ [MGT]B\s+free\]$/ ) [10:38] hmm, shall I paste it to paste.debian.net? [10:39] I've committed the bugfixes to the SVN [10:40] MT is not not tricky to try to guess the output all the time ? vgdisplay -s --units m would make it more predictable [10:41] oh, cool [10:41] didn't know about that one [10:43] I'll do the respective changes this evening [10:48] MT, your test on line 379 is booting nowe [10:48] meaning, it did the trick? [10:48] MT, you can use whatever units you want thol [10:48] meanint i am booting the fai client now [10:48] for another install attempt? [10:49] yeah [10:50] stockholm, did you already try the fstabkey:uuid thing? [10:52] MT, it failed to add the partition into the vg vg_system becouse it was allready a member of vg system from my previous installation attempth [10:53] MT, then it failed to create lv's since vg vg_system does not exsists [10:53] hmm, could you manually remove that volume group? [10:54] yeah ill do that and try again [10:55] ill be back in 20 minutes, run to lunch before they remove the food. :) [10:56] I'll also be away for 40 minutes or so [10:57] sep, this is of course a bug, but manually removing it is the quick fix :-) [11:03] ok, i'm a bit further now. i've installed the gutsy version of fai 2.3.1 from ppa.launchpad.net and the install procedure is working, until it gets to downloading the dkpg's with aptitude [11:03] it just stops downloading at a random package [11:04] we're running a local apt mirror here, it doesn't seem to have any performance problems. Anyone who could point me into the right direction or a logfile which would show more info? [11:06] Bokeh: what does software.log say? [11:06] there must be something in the logs [11:07] the only warning software.log gives is about the fact that fai-client is untrusted (which is correct because it comes from another repository) and that it's ignoring it because Ignore-Trust-Violations is set [11:07] the last line is Get:32 http://apt.lorentz.leidenuniv.nl gutsy/main librpcsecgss3 0.14-2ubuntu4 [35.4kB] [11:08] the package name and number is usually different [11:08] MT: the fstabkey:uuid thing is a solution, but it would need to be automated in order to work [11:08] dmesg is only giving me a message about unionfs (new lower inode mtime) [11:12] status.log ends with instsoft.FAIBASE OK. in case that's interesting to know [11:13] i-R2D2 (~deed@tor-irc.dnsbl.oftc.net) left irc: Remote host closed the connection [11:16] MT (~MT@dove.informatik.tu-muenchen.de) left irc: Ping timeout: 480 seconds [11:20] i-R2D2 (~deed@tor-irc.dnsbl.oftc.net) joined #fai. [11:26] serieus (~serieus@office.nedstat.nl) left irc: Quit: My damn controlling terminal disappeared! [11:35] MT (~MT@dove.informatik.tu-muenchen.de) joined #fai. [11:37] Bokeh: try using an official mirror. OR paste the whole fai.log to paste.debian.net [11:39] yeah, was already working on seeing if it works with the regular ubuntu mirrors [11:39] still weird though, never had problems with installing from the local repo [11:40] ErKa (~keryell@keryell.pck.nerim.net) joined #fai. [11:56] nope... still hanging while getting the dpkgs [11:56] i'll put the log up in a second [11:59] http://paste.debian.net/39195 [12:00] really strange. [12:01] Log into your install client and use top and strace (maybe not installed into the nfsroot) to check what is going on. Maybe a partition is full? [12:02] top isn't really showing anything, i'll put strace in the nfsroot now [12:02] looks like aptitude is hanging for some reason [12:02] it's still in pstree but not doing anything [12:03] brb [12:29] hmmm [12:29] iostat isn't showing anything significant [12:30] and the only thing that aptitude is doing according to strace is [pid 7302] futex(0xa4d67c, FUTEX_WAIT, 1, NULL [12:31] Mmm, I never heard of this problem. Other people have success using ubuntu [12:31] could be b0rked hardware, i'll give it a try on another machine later one [12:31] on* [12:32] yeah, i also didn't have any problems with installing dapper with fai [12:32] though that was a while ago already on different machines with a different setup [12:33] it seems all processes (install_packages, aptitude, the http processes spawned by aptitude are all in a wait state [12:34] could be a messed up harddisk or ram, though it's weird dmesg doesn't show anything interesting [12:45] Action: h01ger is hit by bashism in his own script :) [12:47] ErKa (~keryell@keryell.pck.nerim.net) left irc: Ping timeout: 480 seconds [12:57] MT: gestern hast du gesagt ich solle auch die zeilen 95 und 96 in shdd2-pasrer ändern wenn ich die disk1.2 notation hinzufügen würde. [12:57] MT: aber in den zeilen ist doch garnix was damit zu tun hat, oder sehen ich das falsch? [12:58] Mrfai: http://www.zweinull.cc/spotify-neuer-musikdienst-stellt-alles-andere-in-den-schatten/ [12:58] also da sollte meines Wissens nach dieselbe regexp stehen wie im eigentlichen Code [12:58] ach, stockholm, was hast Du eigentlich vorhin gemeint mit [12:59] MT: der witz ist dass die regexp glaube ich garnicht geändert werden muss. [12:59] "it would need to be automated in order to work"? [12:59] ErKa (keryell@keryell.pck.nerim.net) joined #fai. [12:59] hmm, stimmt [13:00] das nimmt ja alles [13:00] MT: ich meinte dass shdd das uuid labeling übernehem müsse und die richtigen werte in grubs boot.menu und fstab eintragen müsste [13:00] also in fstab sollte er das ja machen [13:00] und grub muss ja auch davon wissen, damit der kernel die devices richtig ordnen kann [13:00] ok, dann muss man also nur im parser das disk\d+\.\d+ besonders behandeln [13:01] ja, grub ist schon noch ein Problem [13:01] genau [13:01] das habe ich gerade gemacht [13:01] und checke es mal eben ein [13:01] ich schreib das mit grub mal auf die wiki-Seite [13:03] MT: schau mal ob das so passt in -parser [13:03] stockholm, vielleicht ist das mit dem grub gar nicht so kompliziert [13:03] ich teste es mal geschwind... [13:03] es gibt ja die Variable ROOT_PARTITION [13:04] und die muss man einfach exortieren? [13:04] hmm, mal kurz die Skripte ansehen [13:06] ja, ich glaub schon dass das funktionieren sollte [13:06] also man muss einfach nur in ROOT_PARTITION den richtigen Wert reinschreiben [13:06] stockholm: danke. Interessanter Beitrag. Und meine FReundin ist immer noch begeistert von spotify. [13:07] stockholm, Zeile 124 in shdd2-fstab [13:09] MT: was sollte da rein, dann? [13:09] da muss man ROOT_PARTITION mit einem korrekten Wert belegen [13:09] MT: ja, das hatte ich verstanden. [13:09] im moment wird da halt /dev/sda oder so gebaut [13:10] ah [13:10] dann müsste man also die infrastruktur zum uuid-holen besorgen? [13:10] ich glaube, so ungefähr den Code ab Zeile 93 kopieren [13:10] ist eigentlich alles schon da [13:10] ohhh [13:11] MT, seams to work when the disk is clean [13:11] ok, thanks [13:11] just one thing [13:11] you had a volume group named system on disk and now have a volume group "vg_system", don't you? [13:12] stockholm, es ist noch viel einfacher [13:12] noch einfacher??? :-) [13:12] $FAI::disk_var{ "ROOT_PARTITION" } = $fstab_line[0] [13:12] well now it's called vg_system2, since i have been testing a few times. and i wanted to make sure the old one got erased and not reused, [13:13] in Zeile 124 statt dem was dort steht [13:13] das if in Zeile 125 muss bleiben [13:13] weil in fstab_line steht ja eh schon das richtige drin, muss man den device namen ja nicht nochmal bauen... [13:13] j [13:14] ja [13:14] ok, cool. [13:14] das kommitte ich dann auch noch eben. :-) [13:14] sep, ok, I just wonder why it failed to add a logical volume to vg_system which had previously existed only in system [13:14] dann sieht das im svn log danach aus als hätte ich richtig was drauf. :-) [13:15] MT, becouse when the md_mod is loaded the vg and lv's from the disks are 'valid' [13:15] so the disk is in the vg, and the vg is in use by lv's [13:16] partman in d-i have the same problem [13:16] ah, hmm, ok [13:16] this will require some further debugging/testing then [13:17] stockholm, kannst Du dann auch testen, ob das mit den UUIDs so auch wirklich klappt? [13:18] stockholm, noch eine Bitte [13:18] kannst Du TODO statt ToDo schreiben? [13:18] macht das grep einfacher :-) [13:18] MT: grep -i [13:19] sicher, aber wenn man das vergisst... [13:28] MT, you can check out dm_wipe_lvm() in partman http://svn.debian.org/wsvn/d-i/trunk/packages/partman/partman-auto/auto-shared.sh?op=file&rev=0&sc=0 [13:29] MT: ja, klar [13:29] MT: jetzt setzt er ROOT_PARTITION=/dev/my_pv/_root [13:29] was ist mit boot? [13:29] er soll ja booten von /boot [13:29] und das ist auch das was grub liest [13:30] das sollte AFAIK kein Problem sein [13:30] also in /boot liegt grub selbst [13:30] bis dahin muss das BIOS kommen [13:30] und dann muss grub nur die richtige root=bla Kommandozeile an den kernel übergeben [13:31] und da muss dann eben root=/dev/my_pv/_root stehen [13:31] das sollte dann eigentlich schon klappen [13:31] falls die grub-tools das richtig reinschreiben [13:31] -> mal die erzeugte menu.lst prüfen [13:32] ja, ich boote jetzt gerade das installierte system [13:34] grup error 17 [13:34] grub error? [13:34] ja [13:34] was findet er denn nicht? [13:34] ich mein, das hat dann ja mit root=bla noch nix zu tun ... [13:36] vielleicht ist die device.map nicht OK? [13:37] 17 : Cannot mount selected partition [13:37] This error is returned if the partition requested exists, but the filesystem type cannot be recognized by GRUB. [13:38] 17 : Cannot mount selected partition This error is returned if the partition requested exists, but the filesystem type cannot be recognized by GRUB. [13:39] stockholm, wenn Du die grub config beim booten editierst, findet er da den kernel und so? [13:39] (einfach mal tab completion probieren...) [13:39] MT, any way one can avoid hardcoding device names in the line vg vg_system sda2 ? since i use the line disk_config disk1, [13:39] gerade macht grub garnix mehr. ich probiere gleich [13:40] sep, stockholm comitted a patch for this just a few minutes ago [13:40] if you grab shdd2-parser from SVN again, you can use [13:40] MT stockholm great [13:40] disk1.2 [13:41] for partition 2 on sda, if sda is disk1 [13:44] MT: grub kommt garnicht richtig hoch, error 17 kommt "sofort" bevor ich was manuell machen kann [13:44] MT: was macht dein patch? [13:45] Du meinst, die Sache mit ROOT_PARTITION? [13:45] ja [13:45] ganz dumme frage. Kann grub denn lvm? [13:45] sollte eben eigentlich nur statt /dev/sda1 oder so evtl. eine UUID oder ein LABEL nehmen [13:45] Mrfai: das muss er nicht [13:46] Mrfai: erst bootet man /boot wo der kernel und die initrd drauf ist [13:46] Mrfai: aber ich frage mich warum die root partition dann ins spiel kommt [13:46] MT: zuerst muss doch erstmal /boot auf der richtigen hd gefunden werden. [13:47] wie funktioniert das denn wenn die festplatten in beliebiger reihenfolge auftauchen können? [13:52] stockholm, der letzte Patch sollte eigentlich nichts ändern bei Dir [13:52] weil die root partition ja sowieso im LVM liegt [13:52] hat es denn vorher funktioniert? [13:52] ah [13:53] MT: das letzte mal war das error 17 [13:53] jetzt boote ich wieder [13:55] wieder error 17 [13:55] und hier ist die fstab [13:55] # [13:55] /dev/sde1 none swap sw 0 2 [13:55] /dev/sdb1 none swap sw 0 2 [13:55] /dev/my_pv/_root / ext3 rw,errors=remount-ro 0 1 [13:55] /dev/sdc1 none swap sw 0 2 [13:55] stockholm: stimmt /boot ist wohl nicht im LVM nur /. Verstehe. [13:55] /dev/sdb2 /boot ext3 rw,notail 0 2 [13:55] /dev/my_pv/_var /var xfs rw,notail,noatime 0 2 [13:55] /dev/sdd1 none swap sw 0 2 [13:55] ich meine, hat es schon irgendwann mal mit setup_harddisks_2 geklappt? [13:55] MT: nee, vorher hatten wir ja andere probleme so dass es nie überhaupt gebootet hat [13:56] errr [13:56] ich meine: vorher ist shdd2 ja nie durchgelaufen [13:56] ja, verstehe [13:56] jetzt macht es das. [13:56] was steht denn in shell.log oder so drin? [13:56] wie markiert man die bootpartition denn? [13:57] irgendwelche errors, wenn er GRUB/10-setup ausführt? [13:57] MT: ich habe hier die fai.log, die ist fast nur shdd2 log :-) [13:57] ich schau mal [13:57] shell.log brauchst aber ... [13:57] hmm, boot partition [13:57] ja [13:58] Executing shell: GRUB/10-setup [13:58] GRUB/10-setup FAILED with exit code 1. [13:58] aber in shell.log sollte mehr drin stehen [13:58] ok [13:59] floood!!! [13:59] hmm, vielleicht brauchst du sowas [13:59] Report bugs to . [13:59] Can't open /target/boot/grub/device.map [13:59] Searching for GRUB installation directory ... found: /boot/grub [13:59] Searching for default file ... Generating /boot/grub/default file and setting the default boot entry to 0 [13:59] Searching for GRUB installation directory ... found: /boot/grub [13:59] Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst [13:59] Searching for splash image ... none found, skipping ... [13:59] Found kernel: /vmlinuz-2.6.18-5-amd64 [13:59] Found kernel: /memtest86+.bin [13:59] Updating /boot/grub/menu.lst ... done [13:59] Grub installed on on [13:59] ERROR: postinst returned code 1 [13:59] GRUB/10-setup FAILED with exit code 1. [13:59] disk_config disk1 fstabkey:uuid bootable:2 [14:00] er braucht die Variablen BOOT_PARTITION und BOOT_DEVICE [14:00] i see this error too GRUB/10-setup FAILED with exit code 1 [14:01] ok, switching to English [14:01] MT: ok, i test that [14:01] BOOT_PARTITION and BOOT_DEVICE seem not to be set [14:01] could either of you check that? [14:01] MT: i am reinstalling with that setting now [14:02] with bootable:2 ? [14:02] yes [14:02] I'd be interested in what happens if you don't have that [14:02] it should have properly set the values itself [14:02] I hope ... [14:03] paste the contents of disk_var.sh [14:03] without bootable:2 [14:04] MT fai.log and disk_var.sh state that BOOT_DEVICE and BOOT_PARTITION is set [14:04] sep, do you have a separate /boot partition? [14:04] MT i have bootable:1 btw and a primary /boot [14:04] yes [14:05] but, did your grub report error 17 as well? [14:05] when booting the client for the first time? [14:05] again, grub exited with error 1 [14:05] what about the log? [14:05] does it still say [14:06] Grub installed on on [14:06] or are there now sensible values? [14:06] after the on's [14:06] ErKa (keryell@keryell.pck.nerim.net) left irc: Ping timeout: 480 seconds [14:07] http://paste.debian.net/39209 [14:07] that is the grub part from shell.log [14:07] it looks quite unhappy [14:08] Grub installed on on [14:08] ERROR: postinst returned code 1 [14:08] GRUB/10-setup FAILED with exit code 1. [14:08] Can't open /target/boot/grub/device.map [14:08] Thomas pointed in this direction already [14:08] Action: Mrfai filed a bug report that the postinst of grub/menu.lst should check if those variables are defined [14:08] just a sec ... telephone ... [14:09] http://paste.debian.net/39211 [14:09] it's identical [14:09] the uuid is not used in BOOT_PARTITION: [14:09] # [14:09] /dev/sde1 none swap sw 0 2 [14:09] UUID=e6163ecf-98ff-41b8-ace6-a3ed7bd59ce3 none swap sw 0 2 [14:09] /dev/my_pv/_root / ext3 rw,errors=remount-ro 0 1 [14:09] /dev/sdc1 none swap sw 0 2 [14:09] UUID=c3455830-36b4-45b2-aa7a-380c4c0ca295 /boot ext3 rw,notail 0 2 [14:09] /dev/my_pv/_var /var xfs rw,notail,noatime 0 2 [14:09] /dev/sdd1 none swap sw 0 2 [14:09] SWAPLIST=/dev/sde1 /dev/sdb1 /dev/sdc1 /dev/sdd1 [14:09] BOOT_DEVICE=/dev/sdb [14:09] ROOT_PARTITION=/dev/my_pv/_root [14:09] BOOT_PARTITION=/dev/sdb2 [14:09] but it is used in the fstab [14:09]