/srv/irclogs.ubuntu.com/2015/09/27/#ubuntu-server.txt

=== Lcawte is now known as Lcawte|Away
T3DYSuch a dead group01:43
hallynzul: meh, i think my libvirt preinst/postinst bits to handle starting libvirt-guests is wrong altogether.02:35
hallynzul: i think it needs to drop the preinst bit ,and just unconditionally start libvirt-guests.  which also has wrong name for libvirtd service.02:36
lordievaderGood morning.07:36
=== 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
tewardgeneral 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
tewardany ideas of diagnosing?14:15
lordievaderCheck the logs.14:20
tewardwhich logs :P14:21
* teward yawns14:21
lordievaderdmesg, messages, syslog, etc14:22
tewardmmmm14:24
tewardnothing informative in dmesg, syslog.  except that pre-start terminated with status 1, and post-stop terminated with 10014:25
tewardkernel earlier on also complains it terminated with status 1 twice14:25
tewardbut it doesn't appear informative of any specifics :/14:25
lordievaderPre/post start of what?14:26
lordievaderNetworking?14:26
tewardmhm14:27
* teward yawns14:27
tewardsorry, i'm still waking up >.<14:27
lordievaderIs that a yes?14:27
tewardyes, it is14:27
lordievaderteward: There is your problem.14:27
tewardlordievader: uninformative error codes are uninformative.  any idea where they're documented?14:28
lordievaderErr, no idea.14:29
lordievaderUpstart keeps logs though.14:29
tewardupstart's logs were helpful14:30
tewardapparently it said invalid option placement.14:30
tewardlooking at the interfaces file, i had to open it in a different editor, but it found rogue ascii14:30
tewardthat answers the problem xD14:30
teward(neither nano nor vi nor vim showed the ascii.  hex editor found it ;P)14:30
TJ-teward: i usually find 'less' is good for spotting those random control codes, unless using 'less -r'14:45
teward,,,14:49
tewardmmm*14:49
tewardyeah, well, meh14:49
tewardfound it, fixed it, problem solved :)14:49
=== acrocity_ is now known as acrocity
tgm4883Trying 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 to17:03
tgm4883be done?17:03
tgm4883Hmm, apparently it has to be stopped to add it17:12
hallynzul: smb: does http://paste.ubuntu.com/12594504/ make sense to you?18:50
zulhallyn: oooks ok to me19:02
hallynzul: does what i'm saying and doing make sense?19:03
zulyeah19:03
hallyncool, thanks19:05
hallyni'll push in a bit when i feel more couragious19:05
=== athairuzzz is now known as athairus
Karunamonhi folks, does anyone in here know anything enough about mdraid to explain why it can't see a mirrored drive from another system?21:12
lordievaderKarunamon: Have you assembled them?21:14
patdk-laphave you put the disks from the other system into this one?21:17
Karunamonthe one disk, yes21:17
Karunamonthe other one is toast21:17
Karunamonif 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 mounted21:18
lordievaderKarunamon: Probably since the other disk is not found it wont assemble it automatically, you have to do that manually.21:20
Karunamonan --assemble --scan shows me "/dev/sdb1 has wrong uuid"21:20
TJ-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
KarunamonTJ-,no other arrays on the system21:21
Karunamonhm, there it goes. Apparently an earlier command had dumped a line for a non existent array into mdadm.conf21:25
Karunamoncleared that, --assemble --scan, and we're good21:25
Karunamonof course now the filesystem does not want to mount21:25
Karunamonso 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:33
Karunamon262144 (sectors? blocks?) beyond the end21:36
TJ-Are you sure the original array was only RAID-1 ?21:39
Karunamon100% positive. There were four drives in the old system, two RAID1 sets21:39
bekksTwo raid1 sets or one raid10 set?21:40
Karunamontwo raid1 sets (one was for the system, the other was for bulk storage)21:40
TJ-Karunamon: OK, it could be a HPA (Host Protected Area) issue I suppose.21:40
Karunamoni'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:40
Karunamonoh boy.. this got complicated, then21:41
Karunamonbecause 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
TJ-Karunamon: is the raw drive partitioned, or pure MD without a partition table?21:41
Karunamonit's partitioned, the first partition is the mdraid device21:42
TJ-Karunamon: which metadata version is the MD using (that affects where the metadata is in the underlying partition)21:45
Karunamon1.221:45
TJ-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:47
KarunamonIt did come from the kernel (per syslog), but what's there is pretty scant21:49
Karunamonlemme paste it21:49
Karunamonhttps://gist.github.com/4052b9be877070e2a5b721:51
Karunamonthe first one was during an attempt to mount, the second was during an xfs_repair attempt21:52
TJ-Karunamon: "capacity change from 0 to 499837108224" matches "limit=986244352" (in 512-byte sectors).21:54
KarunamonTJ-: so it's mdadm who has the wrong idea as to the size this thing should be21:55
TJ-Karunamon: what does "hdparm -N /dev/sdX" report about HPA?21:55
Karunamon max sectors   = 0/1, HPA is enabled21:56
TJ-Karunamon: aha, so HPA = yes, but "0/1" ... that's not right!21:56
Karunamonthere could be some strangeness because of the convoluted way this drive is mounted21:56
TJ-Karunamon: is it on a USB controller?21:57
KarunamonWorse. 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 device21:57
Karunamonand before you ask: it's a SAS drive, and I don't have any other gear onhand to read those21:58
Karunamonso some quick searching.. this sounds like an automatic HPA unlocking thing that ubuntu had some issues with a while back?22:00
=== Lcawte is now known as Lcawte|Away
TJ-Karunamon: hmmm, can you use hdparm from the host?22:00
Karunamonit was unlocked on the previous system, and not here, so the end of the drive is seemingly missing?22:00
Karunamonnot on the host unfortunately22:01
TJ-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:01
TJ-Karunamon: what does this report? "hdparm --dco-identify /dev/sdX" ?22:02
Karunamonhttps://gist.github.com/16e60ab28ad2f02c866322:12
Karunamon@TJ-22:12
KarunamonI'm thinking I could bring this drive into work if there's something to mutter at hdparm to get that hpa disabled22:13
Karunamonand get it plugged into real hardware22:13
TJ-Karunamon: looks like ESXi is getting in the way22:14
=== Lcawte|Away is now known as Lcawte

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!