Tool/Procedure To Determine OS Binary Present On External Disk Partition(s)
Any ideas on how to go about determining the OS Binary Present On External Disk Partitions; other than mounting a partition, and comparing actually file sizes between various files resting on comparison file systems? The partition table of disk where I've got partitions that I'm curious about, each hosts a different a different OS version, and is buggered; thus can't be booted. They are mountable, from the disk from which I am currently booted, however.
Douglas Randall
(odoncaoa@yahoo.com)
partitioning mount disk versions binary
asked 8 hours ago
odoncaoaodoncaoa
293
|
show 1 more comment
Any ideas on how to go about determining the OS Binary Present On External Disk Partitions; other than mounting a partition, and comparing actually file sizes between various files resting on comparison file systems? The partition table of disk where I've got partitions that I'm curious about, each hosts a different a different OS version, and is buggered; thus can't be booted. They are mountable, from the disk from which I am currently booted, however.
Douglas Randall
(odoncaoa@yahoo.com)
partitioning mount disk versions binary
asked 8 hours ago
odoncaoaodoncaoa
293
If partitions can be mounted & read, Boot-Repair is a good tool to see what is where. May be best to see details, use ppa version with your live installer or any working install, not older Boot-Repair ISO: Please copy & paste link to the Boot-info summary report ( do not post report), the auto fix sometimes can create more issues. help.ubuntu.com/community/Boot-Repair
– oldfred
7 hours ago
1
If we're talking about Ubuntu... and we are only talking about Ubuntu here... just look in the /boot directory, and note what file has the highest version number in its name. Regarding your current problem, have you run fsck on the Linux partitions?
– heynnema
7 hours ago
Exactly, the required data which was necessary. Cheers Doug
– odoncaoa
7 hours ago
@heynnema Judging from OP's comment, your suggestion counts as a solution. Post that as a proper answer
– Sergiy Kolodyazhnyy
3 hours ago
@odoncaoa Please see my answer. Please remember to accept it by clicking the grey checkmark icon just to the left of my answer. Clicking the grey up arrow for extra points. Thanks!
– heynnema
3 hours ago
|
show 1 more comment
Any ideas on how to go about determining the OS Binary Present On External Disk Partitions; other than mounting a partition, and comparing actually file sizes between various files resting on comparison file systems? The partition table of disk where I've got partitions that I'm curious about, each hosts a different a different OS version, and is buggered; thus can't be booted. They are mountable, from the disk from which I am currently booted, however.
Douglas Randall
(odoncaoa@yahoo.com)
partitioning mount disk versions binary
asked 8 hours ago
odoncaoaodoncaoa
293
Any ideas on how to go about determining the OS Binary Present On External Disk Partitions; other than mounting a partition, and comparing actually file sizes between various files resting on comparison file systems? The partition table of disk where I've got partitions that I'm curious about, each hosts a different a different OS version, and is buggered; thus can't be booted. They are mountable, from the disk from which I am currently booted, however.
Douglas Randall
(odoncaoa@yahoo.com)
partitioning mount disk versions binary
partitioning mount disk versions binary
asked 8 hours ago
odoncaoaodoncaoa
293
asked 8 hours ago
odoncaoaodoncaoa
293
asked 8 hours ago
odoncaoaodoncaoa
293
asked 8 hours ago
odoncaoaodoncaoa
293
asked 8 hours ago
odoncaoaodoncaoa
293
293
If partitions can be mounted & read, Boot-Repair is a good tool to see what is where. May be best to see details, use ppa version with your live installer or any working install, not older Boot-Repair ISO: Please copy & paste link to the Boot-info summary report ( do not post report), the auto fix sometimes can create more issues. help.ubuntu.com/community/Boot-Repair
– oldfred
7 hours ago
1
If we're talking about Ubuntu... and we are only talking about Ubuntu here... just look in the /boot directory, and note what file has the highest version number in its name. Regarding your current problem, have you run fsck on the Linux partitions?
– heynnema
7 hours ago
Exactly, the required data which was necessary. Cheers Doug
– odoncaoa
7 hours ago
@heynnema Judging from OP's comment, your suggestion counts as a solution. Post that as a proper answer
– Sergiy Kolodyazhnyy
3 hours ago
@odoncaoa Please see my answer. Please remember to accept it by clicking the grey checkmark icon just to the left of my answer. Clicking the grey up arrow for extra points. Thanks!
– heynnema
3 hours ago
|
show 1 more comment
If partitions can be mounted & read, Boot-Repair is a good tool to see what is where. May be best to see details, use ppa version with your live installer or any working install, not older Boot-Repair ISO: Please copy & paste link to the Boot-info summary report ( do not post report), the auto fix sometimes can create more issues. help.ubuntu.com/community/Boot-Repair
– oldfred
7 hours ago
1
If we're talking about Ubuntu... and we are only talking about Ubuntu here... just look in the /boot directory, and note what file has the highest version number in its name. Regarding your current problem, have you run fsck on the Linux partitions?
– heynnema
7 hours ago
Exactly, the required data which was necessary. Cheers Doug
– odoncaoa
7 hours ago
@heynnema Judging from OP's comment, your suggestion counts as a solution. Post that as a proper answer
– Sergiy Kolodyazhnyy
3 hours ago
@odoncaoa Please see my answer. Please remember to accept it by clicking the grey checkmark icon just to the left of my answer. Clicking the grey up arrow for extra points. Thanks!
– heynnema
3 hours ago
If partitions can be mounted & read, Boot-Repair is a good tool to see what is where. May be best to see details, use ppa version with your live installer or any working install, not older Boot-Repair ISO: Please copy & paste link to the Boot-info summary report ( do not post report), the auto fix sometimes can create more issues. help.ubuntu.com/community/Boot-Repair
– oldfred
7 hours ago
If partitions can be mounted & read, Boot-Repair is a good tool to see what is where. May be best to see details, use ppa version with your live installer or any working install, not older Boot-Repair ISO: Please copy & paste link to the Boot-info summary report ( do not post report), the auto fix sometimes can create more issues. help.ubuntu.com/community/Boot-Repair
– oldfred
7 hours ago
1
1
If we're talking about Ubuntu... and we are only talking about Ubuntu here... just look in the /boot directory, and note what file has the highest version number in its name. Regarding your current problem, have you run fsck on the Linux partitions?
– heynnema
7 hours ago
If we're talking about Ubuntu... and we are only talking about Ubuntu here... just look in the /boot directory, and note what file has the highest version number in its name. Regarding your current problem, have you run fsck on the Linux partitions?
– heynnema
7 hours ago
Exactly, the required data which was necessary. Cheers Doug
– odoncaoa
7 hours ago
Exactly, the required data which was necessary. Cheers Doug
– odoncaoa
7 hours ago
@heynnema Judging from OP's comment, your suggestion counts as a solution. Post that as a proper answer
– Sergiy Kolodyazhnyy
3 hours ago
@heynnema Judging from OP's comment, your suggestion counts as a solution. Post that as a proper answer
– Sergiy Kolodyazhnyy
3 hours ago
@odoncaoa Please see my answer. Please remember to accept it by clicking the grey checkmark icon just to the left of my answer. Clicking the grey up arrow for extra points. Thanks!
– heynnema
3 hours ago
@odoncaoa Please see my answer. Please remember to accept it by clicking the grey checkmark icon just to the left of my answer. Clicking the grey up arrow for extra points. Thanks!
– heynnema
3 hours ago
|
show 1 more comment
1 Answer
1
active
oldest
votes
From the comments...
For Ubuntu, if you look into the /boot directory in each partition, you'll find files encoded with the version information in the filename. Like so...
$ ls /boot
config-4.18.0-14-generic memtest86+.bin
config-4.18.0-15-generic memtest86+.elf
efi memtest86+_multiboot.bin
grub System.map-4.18.0-14-generic
initrd.img-4.18.0-14-generic System.map-4.18.0-15-generic
initrd.img-4.18.0-14-generic.old-dkms vmlinuz-4.18.0-14-generic
initrd.img-4.18.0-15-generic vmlinuz-4.18.0-15-generic
In this example, 4.18.0-15-generic is the most recent OS binary installed on this partition.
Extra credit...
To fix potentially messed up Linux partitions...
- boot to a Ubuntu Live DVD/USB
- open a
terminalwindow - type
sudo fdisk -l
- identify the /dev/XXXX device name for your "Linux Filesystem"
- type
sudo fsck -f /dev/XXXX# replacing XXXX with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered 3 hours ago
heynnemaheynnema
19.9k22158
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1122809%2ftool-procedure-to-determine-os-binary-present-on-external-disk-partitions%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
From the comments...
For Ubuntu, if you look into the /boot directory in each partition, you'll find files encoded with the version information in the filename. Like so...
$ ls /boot
config-4.18.0-14-generic memtest86+.bin
config-4.18.0-15-generic memtest86+.elf
efi memtest86+_multiboot.bin
grub System.map-4.18.0-14-generic
initrd.img-4.18.0-14-generic System.map-4.18.0-15-generic
initrd.img-4.18.0-14-generic.old-dkms vmlinuz-4.18.0-14-generic
initrd.img-4.18.0-15-generic vmlinuz-4.18.0-15-generic
In this example, 4.18.0-15-generic is the most recent OS binary installed on this partition.
Extra credit...
To fix potentially messed up Linux partitions...
- boot to a Ubuntu Live DVD/USB
- open a
terminalwindow - type
sudo fdisk -l
- identify the /dev/XXXX device name for your "Linux Filesystem"
- type
sudo fsck -f /dev/XXXX# replacing XXXX with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered 3 hours ago
heynnemaheynnema
19.9k22158
add a comment |
From the comments...
For Ubuntu, if you look into the /boot directory in each partition, you'll find files encoded with the version information in the filename. Like so...
$ ls /boot
config-4.18.0-14-generic memtest86+.bin
config-4.18.0-15-generic memtest86+.elf
efi memtest86+_multiboot.bin
grub System.map-4.18.0-14-generic
initrd.img-4.18.0-14-generic System.map-4.18.0-15-generic
initrd.img-4.18.0-14-generic.old-dkms vmlinuz-4.18.0-14-generic
initrd.img-4.18.0-15-generic vmlinuz-4.18.0-15-generic
In this example, 4.18.0-15-generic is the most recent OS binary installed on this partition.
Extra credit...
To fix potentially messed up Linux partitions...
- boot to a Ubuntu Live DVD/USB
- open a
terminalwindow - type
sudo fdisk -l
- identify the /dev/XXXX device name for your "Linux Filesystem"
- type
sudo fsck -f /dev/XXXX# replacing XXXX with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered 3 hours ago
heynnemaheynnema
19.9k22158
add a comment |
From the comments...
For Ubuntu, if you look into the /boot directory in each partition, you'll find files encoded with the version information in the filename. Like so...
$ ls /boot
config-4.18.0-14-generic memtest86+.bin
config-4.18.0-15-generic memtest86+.elf
efi memtest86+_multiboot.bin
grub System.map-4.18.0-14-generic
initrd.img-4.18.0-14-generic System.map-4.18.0-15-generic
initrd.img-4.18.0-14-generic.old-dkms vmlinuz-4.18.0-14-generic
initrd.img-4.18.0-15-generic vmlinuz-4.18.0-15-generic
In this example, 4.18.0-15-generic is the most recent OS binary installed on this partition.
Extra credit...
To fix potentially messed up Linux partitions...
- boot to a Ubuntu Live DVD/USB
- open a
terminalwindow - type
sudo fdisk -l
- identify the /dev/XXXX device name for your "Linux Filesystem"
- type
sudo fsck -f /dev/XXXX# replacing XXXX with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered 3 hours ago
heynnemaheynnema
19.9k22158
From the comments...
For Ubuntu, if you look into the /boot directory in each partition, you'll find files encoded with the version information in the filename. Like so...
$ ls /boot
config-4.18.0-14-generic memtest86+.bin
config-4.18.0-15-generic memtest86+.elf
efi memtest86+_multiboot.bin
grub System.map-4.18.0-14-generic
initrd.img-4.18.0-14-generic System.map-4.18.0-15-generic
initrd.img-4.18.0-14-generic.old-dkms vmlinuz-4.18.0-14-generic
initrd.img-4.18.0-15-generic vmlinuz-4.18.0-15-generic
In this example, 4.18.0-15-generic is the most recent OS binary installed on this partition.
Extra credit...
To fix potentially messed up Linux partitions...
- boot to a Ubuntu Live DVD/USB
- open a
terminalwindow - type
sudo fdisk -l
- identify the /dev/XXXX device name for your "Linux Filesystem"
- type
sudo fsck -f /dev/XXXX# replacing XXXX with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered 3 hours ago
heynnemaheynnema
19.9k22158
edited 3 hours ago
answered 3 hours ago
heynnemaheynnema
19.9k22158
answered 3 hours ago
heynnemaheynnema
19.9k22158
answered 3 hours ago
heynnemaheynnema
19.9k22158
19.9k22158
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1122809%2ftool-procedure-to-determine-os-binary-present-on-external-disk-partitions%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
If partitions can be mounted & read, Boot-Repair is a good tool to see what is where. May be best to see details, use ppa version with your live installer or any working install, not older Boot-Repair ISO: Please copy & paste link to the Boot-info summary report ( do not post report), the auto fix sometimes can create more issues. help.ubuntu.com/community/Boot-Repair
– oldfred
7 hours ago
1
If we're talking about Ubuntu... and we are only talking about Ubuntu here... just look in the /boot directory, and note what file has the highest version number in its name. Regarding your current problem, have you run fsck on the Linux partitions?
– heynnema
7 hours ago
Exactly, the required data which was necessary. Cheers Doug
– odoncaoa
7 hours ago
@heynnema Judging from OP's comment, your suggestion counts as a solution. Post that as a proper answer
– Sergiy Kolodyazhnyy
3 hours ago
@odoncaoa Please see my answer. Please remember to accept it by clicking the grey checkmark icon just to the left of my answer. Clicking the grey up arrow for extra points. Thanks!
– heynnema
3 hours ago