=== Sveta_ is now known as svetlana === svetlana is now known as sveta [05:49] hi found this on my server, [05:49] is this attacker script http://termbin.com/x3iy [05:49] ? [06:16] That shell script makes my eyes hurt. [06:59] Good morning [07:13] Good morning, I have a https://docs.djangoproject.com/en/2.2/howto/deployment/wsgi/modwsgi/#basic-configuration for my django server. But with this config server doesn't even start [07:44] Hey guys [07:45] I need help [07:45] I already installed ubuntu server on my nuc and want to know what the end result looks like so i know it is already fully booted up [07:48] How do you mean? [07:48] What you see on the screen? [07:49] technoob: and what kind of NUC is it exactly? [07:49] Nuc5cpyh [07:50] technoob: did you update bios firmware to latest version? [07:50] YES [07:51] technoob: explain whats happening please as lordievader asked [07:51] I see a command prompt [07:51] But nothing else [07:51] I see just text [07:51] No username input prompt [07:52] Last line of text is "reached target cloud-init target" [07:58] lordievader [08:02] The command prompt is all you get on a server install. A server shouldn't need more [08:12] lordievader yes but what should i all booted up server look like [08:13] I hooked up my nuc on my tv [08:13] What should i be seeing there [08:22] On the screen you'll only see an tty login-prompt. [08:22] If you want to know if all the services started correctly you can issue `sudo systemctl status`. [08:27] I didnt see any tty login prompt [08:27] Should i reboit? [08:27] lordievader [08:27] Could you maybe share a screenshot? [08:28] Kinda hard im on mobile [08:28] Photo? [08:34] Do we have a way to attach photo to this irc? [08:34] technoob: imgur.com [08:36] riot.im - takes some work to get set up, but then you have a nice way to irc from your phone [08:37] Ok in a minute [08:37] I rebooted my machine [08:37] Ill see if the problem still persist [08:37] Im running a celeron processor btw [08:38] So it might be slow [08:40] Also i just wanna ask [08:41] Can i run kodi in a ubuntu server? [08:41] Ubuntu server is like ubuntu desktop without gui right? [08:43] ubuntu server is a linux install without gui. You can technically install a gui on top of it, but if you want a gui, you'll have an easier time using the desktop flavor [08:43] I see [08:44] Can i run nextcloud server and other server apps on the same machine [08:44] sure [08:45] Essentially, you can run whatever you want on the machine 😉 [08:45] generally people use docker to keep things nicely separated [08:46] It's not strictly necessary, but it keep things clean [08:49] I cant seem to launch kodi [08:49] It says that it cant find kodi.services [08:50] Should www-data have access to any folder apache2 wants to access? [08:50] Systemctl start kodi. Thats the command i use [08:50] technoob: Kodi is installed? And that is the correct service name? [08:50] I guess [08:51] I was following a instruction [08:51] In the net [08:51] Check it then, investigate 😉 [08:52] .. [08:52] Sadface [08:53] Hmm might as well just use ubuntu desktop. Will be easier i guess [08:53] I only have like 4 gb ram though [09:16] If you don't open too many browser tabs that is fine 😉 [10:34] Does anyone have experience setting up an l2tp vpn client on a command line lxd container? I tried following https://github.com/hwdsl2/setup-ipsec-vpn/blob/master/docs/clients.md#configure-linux-vpn-clients-using-the-command-line but it fails with "device not found" when looking or ppp0 === jelly-home is now known as jelly [11:30] rbasak: I have to update pmdk, which, when it was created, didn't exist in debian, so its version is of the 0ubuntuN style [11:30] rbasak: now debian has one [11:30] rbasak: but git-ubuntu can't find a common ancestor to start a merge, which is expected I guess [11:30] rbasak: any particular way I should handle this? [11:30] ahasenack: I guess you have a choice. Do you want to converge with Debian? [11:31] what does that mean? sync? [11:31] sync and then reapply our changes, if any remain? [11:31] Do you want the new Ubuntu package to be based on the Debian one, plus a delta? [11:31] yes [11:31] no reason not to [11:31] Depends on the delta I guess :) [11:31] unless the delta is huge, I guess [11:31] ok, let's say I want to [11:32] I don't think there's any easy way of handling this. Fundamentally the "rebase" workflow doesn't work because we don't have a patchset to begin with. [11:32] the pmdk story has "no easy way" written all over it :) [11:32] You could try taking the entire diff between Debian and Ubuntu currently, placing it in the working tree, and see if you can break that up into a logical delta with "git add -p". [11:33] Probably limited to just the debian/ directory. [11:37] rbasak: that's ok, but what will make it have a common ancestor from now on, for future merges? [11:39] any idea why Kerberos is ignoring my logging settings from krb5.conf ? [13:12] anyone knows if server got unattended upgrades enabled by default now? [13:13] it doesn't [13:17] which is a good thing [13:18] definitely. [13:40] I don't think it's such a bad thing nowadays. Server users should take _some_ action to ensure security updates. Taking no action is really bad. So if that action is to change the default to some other mechanism, or enable unattended-upgrades, what's the difference? [13:41] I don't think it's such a bad thing nowadays. Server users should take _some_ action [as/if necessary] to ensure security updates. Taking no action is really bad. So if that action is to change the default to some other mechanism, or enable unattended-upgrades, what's the difference? [13:46] If you ask the average SMB boss what they're more worried about, production breaking due to broken patches, or software getting outdated but generally working (until things get exploited, but even exploits try not to break production), they'll surely answer the first. [13:48] maybe this culture will change a little to the better in the coming years when we get better laws, but it can take a good while longer. [13:52] not sure what laws have to do with it, but having a server automated upgrade and break shit is not good [13:53] changing the default right now will cause those organizations' admins' taking the blame for production breaking due to bugs such as 1813873 (a regression unfixed in bionic after 1.5 weeks) or 1814555, and cause a backslash, making them even more worried about patching, if they are given time to care about that at all. [13:53] I have set patch times, test first and then prod [13:54] Ussat: laws to impose fines on companies whose infrastructure is exploited, data stolen. so far the loss is mostly to users privacy, somewhat to companies' brands, but its still soemwhat cheap to them. [13:55] but those are politics, OT here - sorry. [13:55] um...I am 100% against those laws. Can you gaurentee me as an admin you catch EVERYTHING ? [13:55] all the time [13:55] negligence sure....... [13:58] tomreyn: that's a fair point. [13:59] OTOH, although a large number of users deliberately don't want security updates, AIUI a large majority of those actually end up doing nothing else to get security updates. [14:00] auto updates on desktops are one thing, servers no....thats a recipie for problems [14:00] why not just auto update from 16 --> 18 then ? [14:00] Ussat: my point is that auto updates are better on servers than no security updates at all. That's also a recipe for problems. [14:00] If you want to do something special, then you can do that special thing and disable automatic updates while you're there. [14:01] I disagree, not your job. [14:01] If you're making some special provision anyway, then disabling automatic updates while you're there is hardly onerous. [14:01] Again, why not auto update from 16 --> 18 then [14:02] 16 -> 18 deliberately changes behaviour. Clearly that's unacceptable to do automatically. [14:02] rbasak: problem with unattended upgrades is that it only does half the job, sometimes breaks stuff, and.... only does half the job but people think it does everything. [14:02] ^^^ [14:02] blackflow: in what way does it only do half the job? [14:02] Is there a bug on that? [14:03] you need to restart services, sometimes reboot [14:03] well for starters it doesn't reboot for new kernels. second, it doesn't restart properly when systemd or dbus is upgraded. third, not all updates are solved by systemctl restart, and not all services have post inst steps to restart. [14:03] there's no bug. it just can't be done. reboots and all. needs human intervention. [14:03] yup [14:03] It does tell you human intervention is required though, with the reboot-required flag and in the motd. I hope. [14:04] But regardless I don't think that's a justification for not turning it on by default. [14:04] only if a reboot is required [14:04] who's "you"? it's unattended, remember? [14:04] It's clearly better than the current situation. [14:04] (in terms of landing updates) [14:04] Perfect is the enemy of the good, etc. [14:04] no. halfa job is worse than no job at all (so users know they have to run updates). way bettewr would be to have apticron installed so root is mailed/nagged with updates. [14:05] That's fine to say in theory. In practice most users don't run updates at all. [14:05] that's their problem. [14:05] I disagree.......most SERVER users do [14:05] The users who do and don't want automatic updates are competent enough to know and turn it off. [14:05] Desktop is one thing, servers are a whole different ball game [14:06] So, how woudl you schedule these updates, random times ? how would you determine they do not interfear with what is happening on the server [14:06] I just checked. Cloud images do have unattended-upgrades enabled by default AFAICT. [14:07] btw, when ext4 begets case insensitive filenames, will that be flipped on by default, to appease the windows migrants? [14:07] Ussat: there is a default. If you don't like the default, you can change your configuration. Just like everything else. [14:07] blackflow: how is that relevant? [14:07] Yes, they default should be off [14:07] Look, I understand your opinion. [14:08] If you want to just keep restating it instead of actually providing some reasonable rational justfication, then what's the point of continuing this discussion? [14:08] I am in state of panic [14:08] I have provided several [14:08] rbasak: well like I said, nagging via apticron or something, is WAY better than shoving updates by default. [14:08] I accidentally deleted public_html foleder of a server [14:09] How do you schedule the updates ? How would you determine when they happen [14:09] AIUI, unattended-upgrades _are_ now enabled by default. [14:09] Is there any way I can restore it? [14:09] and they should _not_ be [14:09] restore backup [14:09] siavoshkc: yes, from backups. [14:09] If you want to change the default, take it up with Ubuntu developers using our normal governance structure. [14:09] yeah, windmills :) [14:10] blackflow: can you please lead me on where to start? [14:11] siavoshkc: well, you do have backups, no? [14:11] blackflow: I dont know [14:11] then you don't [14:11] rbasak: i enjoy this discussion, and actually i'm really on your side there, increasing the overall security by more secure defaults is a good thing. i'm just not sure whether the world is ready for it, yet, or whether it'd just backfire. if unattended security patching is really active on cloud images and this hasn't backfired, yet, this is probably a good indicator. [14:12] Thanks :) [14:12] siavoshkc: sorry for your loss. but hey, consider it a great learning experience: always have backups. consider also a filesystem like btrfs or zfs where you can snapshot data before any potentially breaking intervention is done ;) [14:12] (cloud folks are usually more forgiving and prepared for things breaking suddenly, though) [14:13] blackflow: The problem is that it wasnt my system. I entered a path to delete that wasnt my bussiness. I am worrid about the owner of the site [14:13] the site was up and I just deleted it [14:14] sudo apt-get -y remove unattended-upgrades solvs it anyway [14:15] Ussat: fwiw, the scheduling, and many more knobs to tweak, are available in the config file in /etc/apt/apt.conf.d/ [14:15] I think it's 50unattended-upgrades [14:15] ahasenack, Oh I know [14:15] blackflow: I remember there was an automated snapshot mechanism [14:15] can it be used to restore data? [14:15] siavoshkc: perhaps you can use some undelete tool to try and salvage data, but that would require you to bring down the server, or pull out a disk from mirror, as every second the disk is in use reduces the chance for data recovery. [14:15] but if you remove that, its done deal [14:15] sure [14:15] siavoshkc: there's no such thing unless you're running ZFS or btrfs (and even then I don't know bout "automated" unless you've set something up [14:16] You there are data recovery tools/services, BUT you need to ensure the data is not overwritten asap [14:17] and its crap shoot [14:17] and not cheap as for the services [14:19] yeah, and there are tools you can try. It depends if you can take the machine offline, remove the hd, and mount it elsewhere where you can poke at it [14:21] offline and/or remove the hdd [14:22] mount it RO....and again, needs to be done asap to avoid overwriting it [14:26] If by any chance there is an automated backup. where may I find backups? [14:28] Could be anywhere depending on how its done/software etc [14:28] OUr backups are done nightly to a SAN then we have tape taken offsite [14:29] so ya...could be anywhere [14:29] btw, side question. I have an enterprisey SSD here, supposedly sata3.1 @ 6Gbps, but a dd test shows only 420 tps and ~250MB/s in iostat.... sounds.... inadequate. [14:30] blackflow: did you try the hdparm speedtest? [14:31] hdparm -tT /dev/sda something like this [14:32] that's next, I'm clearing out the SSD before I blkdiscard it [14:32] blackflow: firmware to latest can also improve stuff [14:33] depending wich brand [14:34] Samsung Evo 840 something something [14:34] siavoshkc: maybe the machine owner has backups you could ask to be restored [14:34] evo 840 needs firmware improvement patch blackflow [14:34] there's a known speed problem on it [14:39] Ussat: check your cron jobs for anything which looks like it coud do backups, see if you have a process running which sounds liek a backup systems' agent. [14:40] blackflow: evo is consumer, also [14:40] it's already latest firmware [14:41] tomaw, ? think you meant that for siavoshkc [14:41] tomreyn: technically, it's MZ7GE240HMGR but any info I managed to find on it is that it's a rebranded 840 evo [14:41] Ussat: you're right, thanks / sorry. [14:41] siavoshkc: check your cron jobs for anything which looks like it coud do backups, see if you have a process running which sounds liek a backup systems' agent. [14:42] tomaw, NP [14:42] tomreyn: 845DC EVO [14:43] blackflow: probably some slight firmware changes, maybe some extra spare cells. [14:47] does fstrim -v report changes if you run it twice? [14:48] the 840ies can get really slow if you dont trim. [14:48] (or not successfully) [14:51] I blkdiscarded the entire drive before testing [14:52] i see [15:22] I have a python app, test-logger.py, that I've written to write a test log message to syslog. For only that type of message, I'd like to save the log message in a file, and send the same log message out to a log aggregator (loggly) -- I'm having trouble identifying what to filter the message on based on the journalctl output. https://pastebin.com/hGip2Zz2 [15:23] I think this can be done by creating two filters, one to save the log entry to a file, and a duplicate target to forward the messages to loggly. [15:24] blackflow, is that enough detail? [15:25] cognitiaclaeves: not quite, it's not clear what exactly you're talking about. "save the log message in a file", "what to filter"..... are you talking about rsyslog rules? [15:25] and how are you sending to loggly? [15:25] Yes, rsyslog [15:25] Loggly has a page for that. If I can figure out how to filter the rule to a file, I think I can take it from there. [15:26] ( for reference: https://www.loggly.com/docs/systemd-logs/ ) [15:27] ( Although, now that I look at it, it looks like that will forward all logs to loggly, not just the ones I want to target. ) [15:27] what's your rule like? [15:28] That's what I'm trying to figure out. [15:28] The documentation for rsyslog seems to refer to app_name and programme_name (I think), which I don't see in the journalctl output. [15:28] what do you want to filter by? [15:28] forget journalctl [15:29] look at syslog itself and what it's logging [15:30] blackflow, you lost me, sorry. It's a standard ubuntu system in aws. [15:31] journald is forwarding to rsyslog and you want to write rsyslog rules, correct? [15:31] Rules specific to the app, yes. [15:31] ( Don't know if journald is forwarding to rsyslog yet .. it may not be. ) [15:31] right, so don't look at journalctl, but look at what is rsyslog writing. by default it has *.*;... /var/log/syslog, so take a look at that [15:32] it is by default [15:32] Ah, that makes sense. [15:33] also look at the selectors documentation https://www.rsyslog.com/doc/v8-stable/configuration/filters.html [15:33] for program name I think you'll need an if-clause, but it's definitely doable [15:34] I had planned to use a property filter for that. [15:35] https://www.rsyslog.com/doc/v8-stable/configuration/properties.html It shows up in the property list. [15:35] And now that I'm looking at /var/log/syslog, I can identify programname. [15:36] yeah [15:36] Ok, this might be enough to move forward with. Thanks! [15:36] cognitiaclaeves: also keep in mind that journald by default does rate limiting. you'll have to remove it if you want _all_ messages forwarded to syslog and elsewhere [15:37] I just want a particular kind of message. I'll look into that. Will I also need to increase the open files setting for the OS? [15:38] I don't see how open files are related here. you mean for rate limiting? for that, no. Only RateLimit* entries of journald.conf(5) [15:40] Ok, thanks. [16:52] <_Trullo> ok, so I tried subnet: 255.255.255.0/24 .. didn't work, aparently it should be 192.168.1.0/24 to work properly, I have no idea how/why.. [16:52] <_Trullo> pihole works perfect after like 20 reinstalls :) [16:54] _Trullo: you typically won't use 255.* for anything. [16:54] _Trullo: private IPv4 ranges that actually ARE private ranges are 192.168.0.0-192.168.255.255, 172.16.0.0-172.31.255.255, and 10.0.0.0-10.255.255.255 - only use Private IPv4 address space [16:54] and NOT 255.* because that's a reserved range [17:43] _Trullo: look up RFC 1918 for more info [17:59] _Trullo: /24 is just another way of saying 255.255.255.0 as a mask [17:59] 255.255.255.0/24 doesnt really make sense [18:02] I just had a systemd service (keepalived) restart without any apparent reason. Any tips for tracing what called the restart? [18:13] lordcirth_: check the logs and turn on debugging if necessary [18:14] lordcirth_: check dmesg too - perhaps it crashed - if so, it should show there with a SIGSEGV being signalled to the process [18:14] RoyK, nothing in the logs except it restarting [18:15] lordcirth_: has this happened before? [18:15] RoyK, not that I recall [18:15] It's probably not a big deal, just weird [18:16] I haven't seen keepalived just restart - anything in dmesg? [18:17] run dmesg -T to get somewhat proper readable timestamps [18:21] RoyK, thanks, didn't know about -T [18:21] Yeah, nothing in dmesg for 2 days [18:22] hm - and no cron job or something in systemd doing something funny? === svetlana is now known as sveta [18:38] RoyK, nope [18:39] it's just funny it restarted without anything in the logs - if it crashed and systemd restarted it, something should show up in dmesg [18:39] Yeah, I can't see any evidence of a crash [18:40] do you have any monitoring of the system? sysstat/munin/zabbix/something? [18:41] RoyK, nagios, and keepalived emails me on all events, which is why I noticed ("Entering BACKUP state" on start) [18:45] lordcirth_: maybe a colleague of yours restarted it? or an config automation tool (puppet/chef/etc)? [18:46] sdeziel, yeah, I'm looking into that now [18:47] Oh, duh. I issued a dist_upgrade this morning. [19:07] lordcirth_: oh - nagios - is that still alive? [19:09] RoyK, yes, although our install is way out of date. We are planning to upgrade to latest stable soon [19:09] RoyK, what do you use? [19:11] lordcirth_: I used to use nagios some years back, but we're moving everything to zabbix now [19:11] well - not everything - we'll be using NAV as well, https://nav.uninett.no/ [19:12] because it has a few things that we can't find in other tools [19:12] RoyK, thanks, I will look at both. We have a custom inventory system with a lot of Nagios integration, etc, so we probably won't be moving [19:12] nagios -> zabbix, so out of the frying pan into the fire? [19:13] I talked to the guys at uio.no - they have quite a few servers and have moved to zabbix, from nagios. [19:13] zabbix has a steep learning curve, but once you understand the architecture, it's rather neat [19:14] RoyK, what key things does NAV have that Zabbix doesn't? [19:14] Ah, it's more of a network thing? [19:14] stuff like switch configuration, like VLAN setup of ports, if the switch supports snmp rw [19:14] it is [19:14] so it's like "why not both?" [19:15] Very cool. We have a custom (argh) tool for that, which if it was open-sourced decades ago, might still be relevant. === smoser1 is now known as smoser [19:17] lordcirth_: take a look - with a lot of hosts, you may want to use SSDs for the storage - *lots* of things getting updated for graphite (IIRC) so it requires quite a bit of IOPS [19:17] RoyK, thanks. Our servers generally have mdraid1 SSDs for / [19:17] should do [19:19] althoguh I'd hate to have those things on the rootfs - I like to use separate storage or at least separate LVs for root and data [19:27] tomreyn: Thank you. Unfortunately there was no backup and its a real disaster. Tomorrow our host will try to recover the wordpress files. I hope they recover something useful. I just shutdown the server to prevent moe loss. [19:28] I deleted a big running wordpress site in a blinl [19:28] backups are for cowards :D [19:28] blink* [19:28] ow [19:28] RoyK: I cannot digest how there is no backup AT ALL for such a long running website [19:28] an acquaintance [19:29] an acquaintance of mine just found out the hard way that having a home server with 40TiB or so of storage and no backup is a bad idea - RAID6 isn't backup - bad, cheap controllers - oops [19:29] siavoshkc: sorry to hear this, good luck. [19:30] The only good thing is that wordpress keeps many of its data in db [19:30] siavoshkc: usually, there's chances of recovery, at least if the data resides on a RAID [19:31] siavoshkc: the text is in the db, the images etc are on the filesystem [19:31] RoyK, yet another reason I use ZFS, not hardware raid [19:32] RoyK: Yes so many things are lost [19:33] lordcirth_: the only reason I don't have zfs on my home server, is the lack of flexibility - I've worked with rather large zfs systems for some years - they just work [19:33] RoyK, yeah, btrfs's ability to add disks and bodge storage together is very nice. LVM and such are good too. [19:33] lordcirth_: but then - if you have a home server and want to toss in a new drive to expand things a bit, zfs won't do (for now) [19:34] lordcirth_: I don't trust btrfs (yet) [19:34] I'm actually running / on ZFS raidz at home. 3 480GB SSDs. It's great [19:34] lordcirth_: it's been 10 years or so with btrfs and it's still not stable [19:35] Yeah, turns out writing 5th gen filesystems is hard. Who knew? :P [19:35] but extending VDEVs on zfs is coming - I think it's in fbsd already [19:38] Oh, cool. I'm looking forward to 0.8's encryption and faster scrubs [19:38] We have a major dataset at work that takes nearly a week to do a weekly scrub [19:38] then don't scrub weekly :þ [19:39] seems we're tossing out a server soon with 48x4TB disks - with a bit of luck, I could perhaps take it [19:40] I'm looking forward to encryption and the 'special' vdev support [19:40] @RoyK: send me a few of the disks lol? xD [19:40] :P [19:40] always in need of disk expansion on my array of disks lol [19:40] that supermicro mobo would be nice as well as the controllers [19:41] what's rplacing that beast? :) [19:41] dell compellent [19:42] well, that is, dell equallogic, old stuff - just used for CCTV cameras [19:42] but some people at the IT dept think that ZFS and mdraid and such things are black magic and would rather sell their soul to something with a nice gui [19:43] okay, it *would* take like five minutes to type out the zpool create command with 48 devices.. [19:44] yeah - it's pretty hard - and dark magic - and checksums the data and all, whcih equallogic certainly doesn't (nor does compellent) [19:45] but Dell Provides Support, meaning they tell us they need a crapload of logs and then blame us for doing something stupid [19:45] or just say "we don't know yet" [19:47] like when that blade centre went down during the holiday - it's powered via a UPS and one direct line - six PSUs - the UPS had some dead fans and had serious issues, but the power from the direct line was stable, but still, the blade centre just powered itself off and too all its VMs with it [19:50] owwwwwww [19:50] six PSUs, and one failure brought it down? [19:51] Or, half of the PSUs were on the UPS? [19:51] half on UPS half on direct [19:51] but it should be able to run on two PSUs [19:52] Its documentation says 2/6 is enough? [19:52] yes [19:52] and 3/6 should at least be sufficient [19:53] but for some reason, it just powered itself off [19:53] Dell hasn't been able to give us an explaination of this [19:53] I bet they'll eventually say "oh, that's for if the power just cuts, dirty power is unsupported" [19:54] something like that, yes [19:54] 2-of-6?? wow [19:57] "you forgot to install the firmware update to the psu's" [19:58] lol [20:10] tomreyn: hehehe [20:10] tomreyn: please update firmware daily and make sure you have redundancy elsewhere [20:16] :) i've heard a couple funny excuses already. but in the end we all just try to not become the victim of the bad conditions we have to (?) work under. [21:39] hello there [21:40] anyone used to work with mdadm everydays ? [21:42] zertyuio: i'm sure there are people here who worked with mdadm before, or do so daily. but that's not your actual question. please ask your actual question. [21:42] and hello there, too ;) [21:43] here is my disk of 20Go https://pastebin.ubuntu.com/p/vfnTxgdK7g/ i would like to resize it to 950Go [21:44] how i can do so ? [21:44] without losing data [21:44] this is very easy: [21:44] you do backups. [21:46] zertyuio: about resizing, how would you do this when there is no unallocated space? [21:46] easy for you mean not easy for everyone [21:47] as you can see on my post : https://pastebin.ubuntu.com/p/vfnTxgdK7g/ [21:47] there is something above 900GB of free space to use [21:48] i would like to do so the same way that we used to do with lvm and fdisk [21:49] zertyuio, firstly, yes, do a backup. [21:49] zertyuio, then, you can follow this: https://raid.wiki.kernel.org/index.php/Growing#Expanding_existing_partitions [21:50] how you can backup system volume ? [21:50] Skipping the first few instructions that are about switching the larger disks, of course [21:50] zertyuio, the root filesystem? [21:50] !backup [21:50] There are many ways to back your system up. Here's a few: https://help.ubuntu.com/community/BackupYourSystem , https://help.ubuntu.com/community/DuplicityBackupHowto , https://wiki.ubuntu.com/HomeUserBackup , https://help.ubuntu.com/community/MondoMindi - See also !sbackup and !cloning [21:51] i would like to do so from rescue cd [21:53] are you sure about the link that you post ? [21:53] for backup ? [21:56] zertyuio: what makes you wonder about it? [21:56] which it ? [21:57] are you sure about the link that you post ? [21:58] zertyuio: these links should indeed help creating a backup [21:58] yes, for example if you take example of duplicitybackup [21:58] it ask to install a package inside the system [21:59] i m not sure that it will does some good backup [21:59] if i follow so [21:59] i m expecting something that i can boot from rescue cd [22:00] and mount the partition [22:00] and backup the whole thing [22:00] this is cloning / imaging, bare metal recovery, but not backup. [22:01] you don't want to have to stop your system every time you create a backup, right? [22:01] yeas [22:02] so i install duplicity [22:02] so you backup only data that you will want to restore. this also enables you to do smaller, incremental, backups, of just the data you actually need. if the OS storage fails or breaks and you need to reinstall, then you just do that, restore configurations from your backup, and restore other data from your backup, and you're set. [22:04] in order to so [22:04] what you had on your mind about cloning / imaging can be done with clonezilla-live, a bootable linux distribution for this single purpose. this is not a proper backup, but something you can do now if it'd make you feel better about it. [22:05] wait [22:05] in order to so [22:05] ? [22:05] i have to seperate all data need to be backup before [22:06] without mixing with system partition [22:06] that task i forgot to so [22:06] i don't have separate partition for data [22:07] maybe you should have [22:08] ideally separate disks, so you don't have OS and data fail at the same time. [22:08] i think i found the best way [22:08] i will reboot my system [22:08] with rescue cd [22:08]