=== Lcawte is now known as Lcawte|Away === zz_DenBeiren is now known as DenBeiren === peter is now known as Guest65138 === markthomas is now known as markthomas|away === Guest58311 is now known as Locke2002 === Lcawte|Away is now known as Lcawte [11:07] The russians are abusing my postfix server [11:11] YES! I win! [11:11] postqueue -p [11:11] Mail queue is empty [11:12] Down from 23430424 emails [11:12] lol [11:24] LOL [11:24] GJ === Lcawte is now known as Lcawte|Away === kickinz1|afk is now known as kickinz1 === kickinz1 is now known as kickinz1|afk === kickinz1|afk is now known as kickinz1 === kickinz1 is now known as kickinz1|afk === chmurifree is now known as chmuri [16:28] hmm [16:29] if I make an image of a drive will it do just the used space or the entire drive partition size [16:29] imaging takes an exact bit copy of everything, including free space [16:29] imaging is rarely if ever required and usually not the best choice [16:30] k ty === markthomas|away is now known as markthomas === markthomas is now known as markthomas|away [16:58] qman__: I got a windows laptop here thats got a failing hard drive [16:59] still readable data [16:59] takes half hour to boot to windows so I was thinking of taking a copy of the hd before going further [17:00] Valduare: you should use gnu ddrescue [17:00] Valduare, stop booting. it's failing with each read/write. get thee to a backup solution immediately [17:00] get a new hard drive to copy it to, or take an image if you have to, but use gnu ddrescue to make a recovery image [17:00] im booted into ubuntu live cd atm [17:00] havnt heard of gnu ddrescue [17:00] looking it up now [17:01] is it a direct 1to1 solution [17:01] ie I need to have the new hd available [17:01] the short of it: ddrescue -f -n /dev/sda /dev/sdb /tmp/rescue.log [17:01] you should, that's the best way to do it [17:01] but you don't have to, you can do to a file if required [17:02] it won't be compressed though [17:02] and it will be an exact 1:1 copy of everything it was capable of recoverin [17:03] just the used space right? [17:03] all the space, total size of the disk [17:03] prob with these huge 1 terabyte hds lol [17:03] damn [17:04] so what if im wanting to go from a 1 terabyte platter drive to a 256 ssd [17:04] can't do it [17:04] there’s only 71 gigs used space on the 1 terabyte drive [17:04] qman__, as you're clearly better informed than I ... I buy a new computer. I'm going to do some experimental things. I want to image the drive in case I need to restore it to virginal status. How to proceed? does the backup include the empty space on the drive? [17:04] the recovery drive must be as large or larger than the failing drive [17:04] once you have recoered the data, you can then move it to a smaller drive [17:05] the recovery tools are filesystem agnostic, because they have to be [17:05] so they cannot recognize what matters and what doesn't [17:06] you should turn off the system with the failing drive and wait until you can get a same size or larger drive to recover to === Lcawte|Away is now known as Lcawte [17:07] cfhowlett: imaging is not a good backup solution, file backups are more space efficient, faster to take, faster to recover, and avoid fragmentation [17:07] its fine to have it booted up into ubuntu live cd [17:07] hd isnt accessed [17:07] no, it isn't [17:08] as long as that drive is spinning, it could die completely [17:08] shut down, unplug the drive [17:08] we’re not completely sure “what kind of dieing” the hd is [17:08] Valduare, yep. this ^^^ [17:08] it doesn't matter what kind [17:08] cut power until you can recover [17:08] that's the safest bet, always [17:08] Valduare, assume the worst kind, assume the worst time and proceed from there. === bilde2910 is now known as bilde2910|away [17:11] cfhowlett: imaging is best for forensics, and as you see here, recovering from a failing hard drive [17:12] qman__, fair enough. I'll research more. my goal was to restore "reset" to pre-me mucking about status. [17:12] cfhowlett: an image will be a 100% bit-for-bit copy, including fragemntation, noise in your free space, your empty free space, and all [17:12] read error rate 136 [17:13] Valduare: stop messing with it, shut down, and unplug the disk until such time as you have another 1TB or larger disk to recover to; every second you spend with it spinning increases chances of total failure [17:13] its doing a compressed backup to an external hd atm [17:17] cfhowlett: if it has to be _exactly_ the same, an image is the way to go, but be aware of the downsides; most of the time, things don't actually need to be exactly the same [17:17] qman__, thank you much. [17:31] looks like 1 terabyte platter drive 85 at best buy [17:31] guess i’ll go that route instead of the ssd for their laptop heh [17:44] gnu ddrescue rocks [17:44] I once got a drive from a user that couldn't be mounted on any OS i tried it on [17:45] it took gnu ddrescue a little less than a week to recover 99,8% of the data [17:47] RoyK, 24 x 7 for a week? hardcore! [17:47] 500GB [17:48] 24x5.5 or thereabouts [17:48] (24x7 for a week doesn't make sense - a week for a week :P) === Xbert is now known as Guest1097 [17:52] yeah, I had one that kept turning off [17:52] but if I power cycled it, it would spin back up [17:52] repeated that for about a week and a half, got well over 99% of the data, enough to recover [17:53] less than a megabyte was lost === DenBeiren is now known as zz_DenBeiren === markthomas|away is now known as markthomas === bilde2910|away is now known as bilde2910 === bilde2910 is now known as bilde2910|away [21:15] I have just restarted a server remotely after a firmware update, but the network is not coming up. I have no terminal unfortunately.... the only thing I can see is the network interfaces are actually coming up at post, but they are shut down at some point while ubuntu is booting === esde is now known as Guest18963 [21:16] you need some terminal or console access to investigate that issue. === Guest18963 is now known as esde [21:18] bekks: that's probably true, but some hypothesis on what could have caused this would be nice... before I'll be on my way. [21:18] bekks: I think maybe the issue is caused by renamed interfaces after the fw update [21:19] i think NIC interface names might not be persistent if some enumeration has changed, is that right? [21:29] blaaa: the interface names are based on MAC address [21:30] blaaa: a boot failure is much more likely - by default, if it fails to boot once, grub will wait indefinitely the second time around [21:30] blaaa: an fsck or failure to mount something could also be at issue [21:39] qman__: thanks, i'll have to go and see I suppose. After the firmware update the computer booted fine (but I had not tested the network, not even attached it....) and it did a clean acpi shutdown after a complete boot [21:43] qman__: do you know how to configure grub to stop that nonesense? [21:44] nonsense, even [21:44] RoyK: there is some option in the config [21:44] RoyK: don;t remember what it is right now though [21:45] had looked it up when setting up the server... [21:46] RoyK: I have, I looked it up before [21:46] It was causing me issues with some ebayed supermicro servers that rarely boot the first time [21:46] http://askubuntu.com/questions/178091/how-to-disable-grubs-menu-from-showing-up-after-failed-boot [21:46] was it GRUB_RECORDFAIL_TIMEOUT ? [21:47] yes [21:47] yes, apparently [21:47] qman__: thanks [22:16] lucky the server is not far away... [22:17] apparently the interface name had changed [22:17] from p1p2 to eth0 [22:17] p2p1... [22:18] but I have no idea why, except for a fw update and reboot-cycle nothing had changed [22:18] and I believed the point of the new naming scheme was to have persistent names... === bilde2910|away is now known as bilde2910 [22:32] i've got a question about grub: i'm running 14.04 in a VM, and i modify /boot/grub/menu.lst to add a virtual serial port so that i can console in with virsh, and whenever there's a new kernel installed it likes to update menu.lst and overwrite my 2 lines - any way i can avoid this? [22:32] these are simply the 2 lines that i put in: [22:32] furkan: sre [22:32] serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1 [22:33] terminal --timeout=10 serial console [22:33] sure [22:33] JanC: i'm all ears :) [22:34] i noticed the /etc/grub.d/40_custom file but wasn't sure if that was the right place to put it since it said custom menu entries [22:34] it's explained in the manual AFAIK, but you need to put it in a script in /etc/grub.d/ [22:35] those scripts get run as part of update-grub [22:36] so when i run update-grub is it supposed to get copied into menu.lst? [22:36] since i just tried putting it there and it doesn't seem to do that [22:36] the output of those scripts gets copied to menu.lst [22:37] so yes, you need to run update-grub [22:38] man i'm confused, on my desktop 14.04 i've got grub2 but i guess the server version is still using the old one [22:38] oh [22:38] you sure? [22:38] Amazon? [22:38] no well this used to be a 12.04 VM [22:38] and then i upgraded to 14.04 [22:38] is grub2 default in ubuntu server 14.04? [22:39] grub2 was the default in 10.04 and before [22:39] hmm maybe because i used vmbuilder === bilde2910 is now known as bilde2910|away [22:40] but IIRC there is/was some issue with Amazon cloud images not working with that (never needed that) [22:40] ya this is on our own server, not amazon [22:41] we've got a bare metal running 14.04 + a few 14.04 VMs running some services [22:41] it's still possible that it is/was used in cloud images though? [22:42] i built the image with vmbuilder for 12.04... so whatever that does by default i guess [22:43] but yeah i guess this is sort of odd since /etc/grub.d seems to be for grub2 only [22:43] that's right [22:44] i wonder if anything will break if i upgrade [22:47] so for grub2 it looks like the right place to put the serial console stuff is in /etc/default/grub [22:47] unless that's the same thing as just putting it in the custom file [22:49] not the same thing [22:49] the variables you set in /etc/default/grub are used by the scripts in /etc/grub.d/ [22:50] ah i see, interesting [22:50] thanks for the info :) [22:53] it's interesting to read those scripts in /etc/grub.d/ some time :) === markthomas is now known as markthomas|away === bilde2910|away is now known as bilde2910 === bilde2910 is now known as bilde2910|away === Lcawte is now known as Lcawte|Away