=== Lcawte is now known as Lcawte|Away [01:43] Such a dead group [02:35] zul: meh, i think my libvirt preinst/postinst bits to handle starting libvirt-guests is wrong altogether. [02:36] zul: i think it needs to drop the preinst bit ,and just unconditionally start libvirt-guests. which also has wrong name for libvirtd service. [07:36] Good morning. === athairus is now known as athairuzzz === Lcawte|Away is now known as Lcawte === moneylotion is now known as havanamint === havanamint is now known as moneylotion === marlinc is now known as marlinc_ === marlinc_ is now known as marlinc [14:15] general question: I have a computer upon which I installed Ubuntu Server 14.04.3. /etc/network/interfaces has `allow-hotplug eth0` and `iface eth0 inet dhcp` in it, but on boot it doesn't get configuration done for the network / IP. Manual execution of `dhclient` makes it negotiate correctly. [14:15] any ideas of diagnosing? [14:20] Check the logs. [14:21] which logs :P [14:21] * teward yawns [14:22] dmesg, messages, syslog, etc [14:24] mmmm [14:25] nothing informative in dmesg, syslog. except that pre-start terminated with status 1, and post-stop terminated with 100 [14:25] kernel earlier on also complains it terminated with status 1 twice [14:25] but it doesn't appear informative of any specifics :/ [14:26] Pre/post start of what? [14:26] Networking? [14:27] mhm [14:27] * teward yawns [14:27] sorry, i'm still waking up >.< [14:27] Is that a yes? [14:27] yes, it is [14:27] teward: There is your problem. [14:28] lordievader: uninformative error codes are uninformative. any idea where they're documented? [14:29] Err, no idea. [14:29] Upstart keeps logs though. [14:30] upstart's logs were helpful [14:30] apparently it said invalid option placement. [14:30] looking at the interfaces file, i had to open it in a different editor, but it found rogue ascii [14:30] that answers the problem xD [14:30] (neither nano nor vi nor vim showed the ascii. hex editor found it ;P) [14:45] teward: i usually find 'less' is good for spotting those random control codes, unless using 'less -r' [14:49] ,,, [14:49] mmm* [14:49] yeah, well, meh [14:49] found it, fixed it, problem solved :) === acrocity_ is now known as acrocity [17:03] Trying to mount a hosts directory into an lxc container using the command listed as an example when running lxc config (which is "lxc config device add container1 mntdir disk source=/share/c1 path=opt"). I get no errors on the command line, but nothing in that folder is present when I do an ls from inside the container. Is there something else that needs to [17:03] be done? [17:12] Hmm, apparently it has to be stopped to add it [18:50] zul: smb: does http://paste.ubuntu.com/12594504/ make sense to you? [19:02] hallyn: oooks ok to me [19:03] zul: does what i'm saying and doing make sense? [19:03] yeah [19:05] cool, thanks [19:05] i'll push in a bit when i feel more couragious === athairuzzz is now known as athairus [21:12] hi folks, does anyone in here know anything enough about mdraid to explain why it can't see a mirrored drive from another system? [21:14] Karunamon: Have you assembled them? [21:17] have you put the disks from the other system into this one? [21:17] the one disk, yes [21:17] the other one is toast [21:18] if i do an mdadm -E /dev/sdb1, it sees the drive as part of an array, but the problem i'm having is actually getting the cursed thing mounted [21:20] Karunamon: Probably since the other disk is not found it wont assemble it automatically, you have to do that manually. [21:20] an --assemble --scan shows me "/dev/sdb1 has wrong uuid" [21:21] Karunamon: does the current system also have md arrays? If so, does the metadata on both have the same device node name (e.g. md0) ? [21:21] TJ-,no other arrays on the system [21:25] hm, there it goes. Apparently an earlier command had dumped a line for a non existent array into mdadm.conf [21:25] cleared that, --assemble --scan, and we're good [21:25] of course now the filesystem does not want to mount [21:33] so it's XFS.. (this much I know from memory), but it can't be mounted because it's trying to read beyond the end of the disk? [21:36] 262144 (sectors? blocks?) beyond the end [21:39] Are you sure the original array was only RAID-1 ? [21:39] 100% positive. There were four drives in the old system, two RAID1 sets [21:40] Two raid1 sets or one raid10 set? [21:40] two raid1 sets (one was for the system, the other was for bulk storage) [21:40] Karunamon: OK, it could be a HPA (Host Protected Area) issue I suppose. [21:40] i'm also sure this is the case since I set it up that way because there were two 500g drives and two 250g drives :) [21:41] oh boy.. this got complicated, then [21:41] because the drive is being accessed via a raw device mapping on an esx server connected as a single disk logical device on a HP raid controller >_< [21:41] Karunamon: is the raw drive partitioned, or pure MD without a partition table? [21:42] it's partitioned, the first partition is the mdraid device [21:45] Karunamon: which metadata version is the MD using (that affects where the metadata is in the underlying partition) [21:45] 1.2 [21:47] Did the error message about reading beyond end of device come from the kernel log? Can you show the exact message (and any surrounding messages that are relevant) ? [21:49] It did come from the kernel (per syslog), but what's there is pretty scant [21:49] lemme paste it [21:51] https://gist.github.com/4052b9be877070e2a5b7 [21:52] the first one was during an attempt to mount, the second was during an xfs_repair attempt [21:54] Karunamon: "capacity change from 0 to 499837108224" matches "limit=986244352" (in 512-byte sectors). [21:55] TJ-: so it's mdadm who has the wrong idea as to the size this thing should be [21:55] Karunamon: what does "hdparm -N /dev/sdX" report about HPA? [21:56] max sectors = 0/1, HPA is enabled [21:56] Karunamon: aha, so HPA = yes, but "0/1" ... that's not right! [21:56] there could be some strangeness because of the convoluted way this drive is mounted [21:57] Karunamon: is it on a USB controller? [21:57] Worse. So this system is a VM, it's using a raw device mapping in ESXi to access the drive, itself connected to a raid controller as a single disk device [21:58] and before you ask: it's a SAS drive, and I don't have any other gear onhand to read those [22:00] so some quick searching.. this sounds like an automatic HPA unlocking thing that ubuntu had some issues with a while back? === Lcawte is now known as Lcawte|Away [22:00] Karunamon: hmmm, can you use hdparm from the host? [22:00] it was unlocked on the previous system, and not here, so the end of the drive is seemingly missing? [22:01] not on the host unfortunately [22:01] Karunamon: Yes. There's a trick many sysadmins uses to avoid this. When creating an MD device not allocating all the raw device, to allow HPA to be on/off without a problem. Not much help now of course :) [22:02] Karunamon: what does this report? "hdparm --dco-identify /dev/sdX" ? [22:12] https://gist.github.com/16e60ab28ad2f02c8663 [22:12] @TJ- [22:13] I'm thinking I could bring this drive into work if there's something to mutter at hdparm to get that hpa disabled [22:13] and get it plugged into real hardware [22:14] Karunamon: looks like ESXi is getting in the way === Lcawte|Away is now known as Lcawte