is there a command which will output the date that ubuntu (or any distribution) was installed?
11 Answers
You can check the installer logs and dates at:
/var/log/installer
A quick way to find the date through the command line would be by running:
ls -lt /var/log/installer
That lists in reverse chronological order so the oldest file is at the bottom of the list.
- 9,513
- 28
- 73
- 109
- 17,029
- 5
- 55
- 68
-
3This file isn't on my Lucid system. – richq Aug 07 '10 at 20:31
-
On my system, I have 7 files under /var/log/installer/ . I installed from 9.10, and later updated to 10.04. – Stefan Lasiewski Aug 10 '10 at 00:34
-
I do also have this folder on my (freshly installed) 10.04 system and the creation dates of those files give me the install date. The file /var/log/installer/media-info for example contains the information about the installation media that was used for the install. – Marcel Stimberg Aug 10 '10 at 12:29
-
1On my system that was installed originally with 7.10, `/var/log/installer/version` has a date of 2007-10-30, so this seems to be quite reliable... – JanC Oct 21 '10 at 03:02
-
13A pastable answer might be `ls -ld /var/log/installer`. – Justin Force May 29 '12 at 21:45
-
`var/log/installer` Not present in my 12.04 Desktop – Chirag Aug 21 '12 at 19:42
-
I used "nano /var/log/installer/media-info" and found the date!!! – PHP Learner Nov 11 '13 at 08:13
-
**Note:** this file is not present in a `chroot` created by `debootstrap`. – Nathan Osman Aug 04 '15 at 22:55
-
Justin Force, `ls -ld /var/log/installer` as you know prints the directory date but on my system there is a file named `casper.log` that has a timestamp that is 54 minutes previous. If it is not only the date but also the time that is sought then `ls -lt /var/log/installer` would show the files in time order, making it easy to see the oldest file. – H2ONaCl Jan 06 '17 at 22:56
-
PHP Learner: `nano /var/log/installer/media-info` does not show the installation date. It shows the date the operating system image was created at Canonical. – H2ONaCl Jan 06 '17 at 23:00
-
cool! But I am confused, there are 7 files in this directory, each of them have the same date of 3rd July 2016, but one of them (the syslog file) has the date of 15th July 2016 - I cannot remember exactly how the installation run, but I doubt it ran 12 days :D - anyone knows what this difference means? – Nicolas Oct 27 '18 at 11:07
-
@joão-pinto `ls: cannot access '/var/log/installer': No such file or directory` – SebMa Aug 17 '22 at 08:03
If you use ext2/ext3/ext4 and formatted the disk when you installed you can do this nifty trick.
sudo dumpe2fs /dev/sda1 | grep 'Filesystem created:'
You might have to change the /dev/sda1 to reflect your setup.
Example output
Filesystem created: Fri Oct 14 22:40:09 2022
Relying on the date of files, even the "creation time" (mtime) can give errors since upgrading packages might have replaced the file and made a new "creation time".
Similar tools and info might be available on other file systems as well, but I don't know of them.
- 69,223
- 56
- 216
- 327
- 14,517
- 8
- 47
- 59
-
When I do this I get the error `dumpe2fs: Bad magic number in super-block while trying to open /dev/sda1` – king_julien Apr 02 '14 at 20:28
-
@king_julien Are you sure that your /dev/sda1 is your systems root partition? It may be different on your install, in fact the filesystem type may be an other than what is supported by dumpe2fs! – LassePoulsen Apr 02 '14 at 21:36
-
Thanks, I got it now. It was `/dev/sda2`. On `/dev/sda1` I have `/boot/efi`. – king_julien Apr 03 '14 at 18:36
-
5You can use a more general but a little complicated command: sudo dumpe2fs $(mount | grep 'on / ' | awk '{print $1}') | grep 'Filesystem created:' – Aram Paronikyan Jun 08 '16 at 12:10
-
2You could use the `-h` option so you at least only get the superblock info which should be more than enough. – Alexis Wilke Sep 25 '16 at 21:43
-
`sudo dumpe2fs $(mount | grep 'on \/ ' | awk '{print $1}') | grep 'Filesystem created:'` https://unix.stackexchange.com/a/62529/177191 – Akira Yamamoto Feb 25 '21 at 04:01
-
-
Unfortunately even this answer may be misleading, for cloud services. They often have an image they created beforehand. – j riv Nov 22 '22 at 10:24
-
caveat: if you move EC2 EBS types the FS is automagically recreated and this date will reflect the EBS move and not the system creation time – Jay _silly_evarlast_ Wren Aug 28 '23 at 21:05
the only command that worked for me is -
sudo ls -alct /|tail -1|awk '{print $6, $7, $8}'
- 32,274
- 27
- 118
- 177
- 361
- 2
- 3
-
3In my system, and I believe in everyone's, this is the creation date of `/lost+found` – MestreLion May 12 '22 at 09:39
-
Wow that's an smart workaround @MestreLion (for non-boot disks too). – Sridhar Sarnobat Nov 01 '22 at 23:38
-
2@SridharSarnobat, credit for the cleverness goes to the answer, not to myself: that command prints the creation date of the oldest file/dir entry in the root directory. I simply stated that this is most likely `/lost+found`. Just notice this is for EXT4 filesystems: non-boot/root disks might be FAT/NTFS and thus have something else as the oldest entry. – MestreLion Nov 04 '22 at 21:53
-
1
-
Unfortunately even this answer may be misleading, for cloud services. They may have an image they created beforehand. – j riv Nov 22 '22 at 10:25
If the installation is recent, look at the oldest entries under /var/log, but after a few weeks the logs will have been rotated away.
Another thing to look at is the oldest ctime of a file on the root filesystem; but if the whole installation has been copied (e.g. rescued off a failing disk) at the directory tree level, this gives you the date of the copy.
If a heuristic is good enough, look at the date (mtime) of a file that was created during the installation and is unlikely to have been modified since. A good candidate is /etc/hostname; other candidates are /etc/hosts, /etc/papersize, /etc/popularity-contest.conf.
- 59,745
- 16
- 131
- 158
I also don't know of a specific command or file. I'm using some heuristics to find the installation date:
for dir in {/etc,/usr,/lib}; do
sudo find $dir -type f -exec stat -c %z {} \; | \
sed -e 's,-,,g' -e 's, .*,,' | sort | uniq -c | sort -nr -k 2 | \
grep -Ev " [0-9]?[0-9] "
done
This small script looks for files in /etc and /usr and prints out the last changed date. It does some reformatting and lists the occurrences sorted by date (newest first). Usually the oldest entry is the installation date.
This assumes that after an installation are left unchanged. This is in most cases (according to my observation) true, but in special cases it can also give wrong results.
- 18,879
- 9
- 79
- 127
-
1tried it on /etc only (faster), the date was the same as from the dumpe2fs solution, so for me it worked well! – eik3 Feb 28 '14 at 15:52
Unfortunately most answers can be misleading for cloud services because they often have an image they created beforehand.
In that case the best bet might be delving inside /var/log files and finding evidence of your own earliest boots.
Logs themselves may be from the image so you might need logs or file/dir creation dates unique to you.
- 111
- 3
For my Linux Mint system the following worked:
sudo grep 'RTC time' /var/log/installer/syslog
The problem was my syslog didn't show years in the time stamps.
- 171
- 1
The command sudo grep ubiquity /var/log/installer/syslog | less worked for me very well.
- 116,445
- 54
- 318
- 493
- 12,124
- 25
- 65
- 81
I don't think there is.
On Red Hat / CentOS there is the install.log files that is generated when you install the system, but this doesn't exist on Ubuntu.
Assuming your logs go back far enough ( mine do ) you can determine the date the base installation was done in /var/log/dpkg.log*
For example on my system the first two lines of my oldest dpkg.log file (dpkg.log.4.gz) are
2010-04-19 11:40:55 startup archives install
2010-04-19 11:40:55 install base-files <none> 5.0.0ubuntu18
So I installed this system on 19/04/2010 at 11:40:55. That is correct for this system.
There was also a brainstorm idea to add this born date.
- 29,974
- 7
- 52
- 57
-
Thank-you andol, thank-you Richard. /var/log/dpkg.log.1 on a lucid desktop system gave a correct answer where as /var/log/dpkg.log was the only file on a lucid server setup I have, so a little detective work was needed. Some further understanding of the log files will be helpful. – lxtips Aug 06 '10 at 07:05
-
The default setup of `logrotate` discards dpkg logs older than one year. – LassePoulsen Aug 10 '10 at 12:13
-
@Source Lab : Yup. My answer is not foolproof. I did not know about the /var/log/installer directory but do now. That is a better solution. – Richard Holloway Aug 10 '10 at 17:20
-
I still think that the filesystem creation time is the best pointer se [here](http://ubuntu.stackexchange.com/questions/1352/date-ubuntu-was-installed/1843#1843) – LassePoulsen Aug 10 '10 at 17:31
You can type this :
$ \ls -lact --full-time / | awk 'END {print $6,substr($7,1,8)}'
2021-09-08 18:15:47
Or if you have ext2/3/4 filesystem on the / partition, you can type this :
$ sudo tune2fs -l $(findmnt -n -o source -T /) | awk '/created:/{$1=$2="";print substr($0,3)}'
Wed Sep 8 18:15:47 2021
Or if the directory /var/log/installer still exists :
$ \ls -lact --full-time /var/log/installer | awk 'END {print $6,substr($7,1,8)}'
2020-12-27 14:38:45
- 2,081
- 3
- 28
- 38
would it be simple (i may be wrong) just to check software centre, while in there click on 'history' and scroll down to the bottom of your installed updates. Mine shows april 23 2012 first installation. Which is about right when I started using ubuntu?
- 11
- 1