Updating grub showing “error: invalid volume”
up vote
0
down vote
favorite
Googling this issue does not yield any substantial results
Here is output :
Generating grub configuration file ...
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
Found background image: /usr/share/images/desktop-base/desktop-grub.png
error: invalid volume.
error: invalid volume.
error: invalid volume.
Found linux image: /boot/vmlinuz-4.18.0-kali3-amd64
Found initrd image: /boot/initrd.img-4.18.0-kali3-amd64
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
Found linux image: /boot/vmlinuz-4.18.0-kali2-amd64
Found initrd image: /boot/initrd.img-4.18.0-kali2-amd64
error: invalid volume.
error: invalid volume.
error: invalid volume.
Adding boot menu entry for EFI firmware configuration
done
Is this only a warning or an error?
Output from syslog:
Dec 5 18:24:18 aaryan kernel: [12988.488622] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.646927] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.654266] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.661322] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.668585] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.675714] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.682871] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.690006] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.697203] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.704432] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.689944] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.691422] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.698404] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.705126] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.712298] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.718988] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.725978] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.733222] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.740400] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.747543] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.754798] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.761991] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.769336] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Output of fdisk -l
Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 965DA599-6893-47CD-9987-68718345E645
Device Start End Sectors Size Type
/dev/sda1 2048 923647 921600 450M Windows recovery environment
/dev/sda2 923648 1128447 204800 100M EFI System
/dev/sda3 1128448 1161215 32768 16M Microsoft reserved
/dev/sda4 1161216 250068991 248907776 118.7G Microsoft basic data
Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 76A9E023-31F8-4EAB-A41E-1C4673DCEA31
Device Start End Sectors Size Type
/dev/sdb1 34 1441523711 1441523678 687.4G Microsoft LDM data
/dev/sdb2 1441523712 1442574335 1050624 513M EFI System
/dev/sdb3 1953262991 1953265038 2048 1M Microsoft LDM metadata
/dev/sdb4 1953265039 1953525134 260096 127M Microsoft reserved
/dev/sdb5 1442574336 1936959487 494385152 235.8G Linux filesystem
/dev/sdb6 1936959488 1953261567 16302080 7.8G Linux swap
Partition 1 does not start on physical sector boundary.
Partition 3 does not start on physical sector boundary.
Partition 4 does not start on physical sector boundary.
linux grub software-updates
asked Dec 5 at 11:52
Aaryan BHAGAT
11
add a comment |
up vote
0
down vote
favorite
Googling this issue does not yield any substantial results
Here is output :
Generating grub configuration file ...
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
Found background image: /usr/share/images/desktop-base/desktop-grub.png
error: invalid volume.
error: invalid volume.
error: invalid volume.
Found linux image: /boot/vmlinuz-4.18.0-kali3-amd64
Found initrd image: /boot/initrd.img-4.18.0-kali3-amd64
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
Found linux image: /boot/vmlinuz-4.18.0-kali2-amd64
Found initrd image: /boot/initrd.img-4.18.0-kali2-amd64
error: invalid volume.
error: invalid volume.
error: invalid volume.
Adding boot menu entry for EFI firmware configuration
done
Is this only a warning or an error?
Output from syslog:
Dec 5 18:24:18 aaryan kernel: [12988.488622] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.646927] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.654266] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.661322] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.668585] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.675714] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.682871] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.690006] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.697203] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.704432] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.689944] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.691422] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.698404] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.705126] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.712298] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.718988] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.725978] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.733222] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.740400] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.747543] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.754798] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.761991] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.769336] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Output of fdisk -l
Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 965DA599-6893-47CD-9987-68718345E645
Device Start End Sectors Size Type
/dev/sda1 2048 923647 921600 450M Windows recovery environment
/dev/sda2 923648 1128447 204800 100M EFI System
/dev/sda3 1128448 1161215 32768 16M Microsoft reserved
/dev/sda4 1161216 250068991 248907776 118.7G Microsoft basic data
Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 76A9E023-31F8-4EAB-A41E-1C4673DCEA31
Device Start End Sectors Size Type
/dev/sdb1 34 1441523711 1441523678 687.4G Microsoft LDM data
/dev/sdb2 1441523712 1442574335 1050624 513M EFI System
/dev/sdb3 1953262991 1953265038 2048 1M Microsoft LDM metadata
/dev/sdb4 1953265039 1953525134 260096 127M Microsoft reserved
/dev/sdb5 1442574336 1936959487 494385152 235.8G Linux filesystem
/dev/sdb6 1936959488 1953261567 16302080 7.8G Linux swap
Partition 1 does not start on physical sector boundary.
Partition 3 does not start on physical sector boundary.
Partition 4 does not start on physical sector boundary.
linux grub software-updates
asked Dec 5 at 11:52
Aaryan BHAGAT
11
Is this an installation of Kali Linux? Kali is not a general-purpose distribution, so please read this first: unix.stackexchange.com/q/399626/173368
– Haxiel
Dec 5 at 13:46
I have read this and acknowledge this. The error I have posted above is after exhausting all the resources I can find elsewhere. Most of the problems in kali are basic linux problems having same solutions as Ubuntu or Fedora but this is something peculiar
– Aaryan BHAGAT
Dec 5 at 14:03
Okay. For the device to which you are trying to install GRUB to, can you runfdisk -lorgdisk -las appropriate and add the output to the question?
– Haxiel
Dec 6 at 15:46
I have changed the question with what you demanded
– Aaryan BHAGAT
Dec 8 at 5:24
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Googling this issue does not yield any substantial results
Here is output :
Generating grub configuration file ...
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
Found background image: /usr/share/images/desktop-base/desktop-grub.png
error: invalid volume.
error: invalid volume.
error: invalid volume.
Found linux image: /boot/vmlinuz-4.18.0-kali3-amd64
Found initrd image: /boot/initrd.img-4.18.0-kali3-amd64
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
Found linux image: /boot/vmlinuz-4.18.0-kali2-amd64
Found initrd image: /boot/initrd.img-4.18.0-kali2-amd64
error: invalid volume.
error: invalid volume.
error: invalid volume.
Adding boot menu entry for EFI firmware configuration
done
Is this only a warning or an error?
Output from syslog:
Dec 5 18:24:18 aaryan kernel: [12988.488622] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.646927] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.654266] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.661322] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.668585] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.675714] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.682871] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.690006] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.697203] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.704432] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.689944] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.691422] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.698404] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.705126] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.712298] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.718988] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.725978] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.733222] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.740400] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.747543] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.754798] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.761991] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.769336] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Output of fdisk -l
Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 965DA599-6893-47CD-9987-68718345E645
Device Start End Sectors Size Type
/dev/sda1 2048 923647 921600 450M Windows recovery environment
/dev/sda2 923648 1128447 204800 100M EFI System
/dev/sda3 1128448 1161215 32768 16M Microsoft reserved
/dev/sda4 1161216 250068991 248907776 118.7G Microsoft basic data
Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 76A9E023-31F8-4EAB-A41E-1C4673DCEA31
Device Start End Sectors Size Type
/dev/sdb1 34 1441523711 1441523678 687.4G Microsoft LDM data
/dev/sdb2 1441523712 1442574335 1050624 513M EFI System
/dev/sdb3 1953262991 1953265038 2048 1M Microsoft LDM metadata
/dev/sdb4 1953265039 1953525134 260096 127M Microsoft reserved
/dev/sdb5 1442574336 1936959487 494385152 235.8G Linux filesystem
/dev/sdb6 1936959488 1953261567 16302080 7.8G Linux swap
Partition 1 does not start on physical sector boundary.
Partition 3 does not start on physical sector boundary.
Partition 4 does not start on physical sector boundary.
linux grub software-updates
asked Dec 5 at 11:52
Aaryan BHAGAT
11
Googling this issue does not yield any substantial results
Here is output :
Generating grub configuration file ...
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
Found background image: /usr/share/images/desktop-base/desktop-grub.png
error: invalid volume.
error: invalid volume.
error: invalid volume.
Found linux image: /boot/vmlinuz-4.18.0-kali3-amd64
Found initrd image: /boot/initrd.img-4.18.0-kali3-amd64
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
Found linux image: /boot/vmlinuz-4.18.0-kali2-amd64
Found initrd image: /boot/initrd.img-4.18.0-kali2-amd64
error: invalid volume.
error: invalid volume.
error: invalid volume.
Adding boot menu entry for EFI firmware configuration
done
Is this only a warning or an error?
Output from syslog:
Dec 5 18:24:18 aaryan kernel: [12988.488622] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.646927] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.654266] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.661322] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.668585] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.675714] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.682871] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.690006] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.697203] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:19 aaryan kernel: [12988.704432] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.689944] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.691422] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.698404] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.705126] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.712298] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.718988] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.725978] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.733222] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.740400] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.747543] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.754798] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.761991] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Dec 5 18:24:21 aaryan kernel: [12990.769336] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
Output of fdisk -l
Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 965DA599-6893-47CD-9987-68718345E645
Device Start End Sectors Size Type
/dev/sda1 2048 923647 921600 450M Windows recovery environment
/dev/sda2 923648 1128447 204800 100M EFI System
/dev/sda3 1128448 1161215 32768 16M Microsoft reserved
/dev/sda4 1161216 250068991 248907776 118.7G Microsoft basic data
Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 76A9E023-31F8-4EAB-A41E-1C4673DCEA31
Device Start End Sectors Size Type
/dev/sdb1 34 1441523711 1441523678 687.4G Microsoft LDM data
/dev/sdb2 1441523712 1442574335 1050624 513M EFI System
/dev/sdb3 1953262991 1953265038 2048 1M Microsoft LDM metadata
/dev/sdb4 1953265039 1953525134 260096 127M Microsoft reserved
/dev/sdb5 1442574336 1936959487 494385152 235.8G Linux filesystem
/dev/sdb6 1936959488 1953261567 16302080 7.8G Linux swap
Partition 1 does not start on physical sector boundary.
Partition 3 does not start on physical sector boundary.
Partition 4 does not start on physical sector boundary.
linux grub software-updates
linux grub software-updates
asked Dec 5 at 11:52
Aaryan BHAGAT
11
asked Dec 5 at 11:52
Aaryan BHAGAT
11
edited Dec 6 at 17:58
asked Dec 5 at 11:52
Aaryan BHAGAT
11
asked Dec 5 at 11:52
Aaryan BHAGAT
11
asked Dec 5 at 11:52
Aaryan BHAGAT
11
11
Is this an installation of Kali Linux? Kali is not a general-purpose distribution, so please read this first: unix.stackexchange.com/q/399626/173368
– Haxiel
Dec 5 at 13:46
I have read this and acknowledge this. The error I have posted above is after exhausting all the resources I can find elsewhere. Most of the problems in kali are basic linux problems having same solutions as Ubuntu or Fedora but this is something peculiar
– Aaryan BHAGAT
Dec 5 at 14:03
Okay. For the device to which you are trying to install GRUB to, can you runfdisk -lorgdisk -las appropriate and add the output to the question?
– Haxiel
Dec 6 at 15:46
I have changed the question with what you demanded
– Aaryan BHAGAT
Dec 8 at 5:24
add a comment |
Is this an installation of Kali Linux? Kali is not a general-purpose distribution, so please read this first: unix.stackexchange.com/q/399626/173368
– Haxiel
Dec 5 at 13:46
I have read this and acknowledge this. The error I have posted above is after exhausting all the resources I can find elsewhere. Most of the problems in kali are basic linux problems having same solutions as Ubuntu or Fedora but this is something peculiar
– Aaryan BHAGAT
Dec 5 at 14:03
Okay. For the device to which you are trying to install GRUB to, can you runfdisk -lorgdisk -las appropriate and add the output to the question?
– Haxiel
Dec 6 at 15:46
I have changed the question with what you demanded
– Aaryan BHAGAT
Dec 8 at 5:24
Is this an installation of Kali Linux? Kali is not a general-purpose distribution, so please read this first: unix.stackexchange.com/q/399626/173368
– Haxiel
Dec 5 at 13:46
Is this an installation of Kali Linux? Kali is not a general-purpose distribution, so please read this first: unix.stackexchange.com/q/399626/173368
– Haxiel
Dec 5 at 13:46
I have read this and acknowledge this. The error I have posted above is after exhausting all the resources I can find elsewhere. Most of the problems in kali are basic linux problems having same solutions as Ubuntu or Fedora but this is something peculiar
– Aaryan BHAGAT
Dec 5 at 14:03
I have read this and acknowledge this. The error I have posted above is after exhausting all the resources I can find elsewhere. Most of the problems in kali are basic linux problems having same solutions as Ubuntu or Fedora but this is something peculiar
– Aaryan BHAGAT
Dec 5 at 14:03
Okay. For the device to which you are trying to install GRUB to, can you run
fdisk -l or gdisk -l as appropriate and add the output to the question?– Haxiel
Dec 6 at 15:46
Okay. For the device to which you are trying to install GRUB to, can you run
fdisk -l or gdisk -l as appropriate and add the output to the question?– Haxiel
Dec 6 at 15:46
I have changed the question with what you demanded
– Aaryan BHAGAT
Dec 8 at 5:24
I have changed the question with what you demanded
– Aaryan BHAGAT
Dec 8 at 5:24
add a comment |
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
});
}
});
draft saved
draft discarded
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%2funix.stackexchange.com%2fquestions%2f486135%2fupdating-grub-showing-error-invalid-volume%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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.
draft saved
draft discarded
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%2funix.stackexchange.com%2fquestions%2f486135%2fupdating-grub-showing-error-invalid-volume%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
Is this an installation of Kali Linux? Kali is not a general-purpose distribution, so please read this first: unix.stackexchange.com/q/399626/173368
– Haxiel
Dec 5 at 13:46
I have read this and acknowledge this. The error I have posted above is after exhausting all the resources I can find elsewhere. Most of the problems in kali are basic linux problems having same solutions as Ubuntu or Fedora but this is something peculiar
– Aaryan BHAGAT
Dec 5 at 14:03
Okay. For the device to which you are trying to install GRUB to, can you run
fdisk -lorgdisk -las appropriate and add the output to the question?– Haxiel
Dec 6 at 15:46
I have changed the question with what you demanded
– Aaryan BHAGAT
Dec 8 at 5:24