I wonder if your boot files are actually on another drive, like hd1, but
grub is incorrectly looking for grubenv on the non existing hd0?
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1553687
I forgot to mention, BIOS is updated to the latest version CDCN53WW.
** Tags removed: latest-bios-outdated-cdcn35ww
** Tags added: latest-bios-cdcn53ww
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags removed: kernel-bug-exists-upstream latest-bios-cdcn30ww
** Tags added: latest-bios-outdated-cdcn35ww needs-upstream-testing
** Tags added: yakkety zesty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Yesterday I experimented installing Ubuntu 16.04.1, 16.10, 17.04 and Fedora 25.
I have again the same annoying error with all Ubuntu versions. What a nice
surprise: everything ok with Fedora 25.
--
You received this bug notification because you are a member of Kernel
Packages, which is
I'm certainly not an expert, so here's some interesting Google results:
'failure writing to sector'
This bug was fixed in the package grub2 - 1.99-21ubuntu3.15
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1253443
aljosa wrote: "I installed Xenial for the first time at the beginning of
I finally got down to do some debugging. I downloaded the grub source
via apt and made some changes to the source code. Specifically, near
line 567 of grub-core/disk/efi/efidisk.c, adding the status code to the
error message:
"failure writing sector 0x%llx to `%s' [status %lx]" with variable
Hi Jeb,
does your subwoofer and rear speakers works?
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685
Could you please check if your dmesg output contains identical/similar
problematic lines:
[ 0.858435] [Firmware Bug]: No valid trip found
[ 0.861605] [Firmware Bug]: No valid
I am experiencing the same issue on the related Lenovo Y700-15ISK (same
machine, 15" version) with Xubuntu 16.04.
This seems to be an issue in grub, not related to the kernel. The error
message string is from grub-core/disk/i386/pc/biosdisk.c in GRUB2. As
far as I can understand the code, the
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
aljosa, as it is written for anyone with or without prior knowledge,
could you please advise which part you are stuck on?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1553687
Title:
I'm afraid that this is far above my tech level.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1553687
Title:
Lenovo Y700-17ISK Boot Error: Failure writing sector 0x21c8800 to
'hd0'
aljosa, the next step is to fully commit bisect from kernel 4.4.0-1 to
4.4.0-10 in order to identify the last good kernel commit, followed
immediately by the first bad one. This will allow for a more expedited
analysis of the root cause of your issue. Could you please do this
following
Sorry...
To clarify everything:
- I installed 'Xenial' for the first time at the beginning of February
(don't remember the exact kernel version, but for sure it was one from
the '4.4 series'). Initially I didn't have this error, it appeared later
after some updates. Then one day I received a
aljosa, to further clarify, the original kernel that came with Xenial
when you first installed it wasn't 4.4.0-11. It would have been an
earlier version.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I have already uninstalled kernel 4.5-rc7 and am booting only with the
original kernel (4.4.0-11-generic) - yes, the problem is still here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
aljosa, to clarify, if you boot into the original kernel that came with
Xenial, does this issue go away?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.5-rc7
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
aljosa, in order to allow additional upstream developers to examine the issue,
at your earliest convenience, could you please test the latest upstream kernel
available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please
keep in mind the following:
1) The one to test is at the
Hi,
the answer is no, it doesn't prevent the system from booting. Both if I press
and if I don't press any key - system continue to boot up, but showing some
other error messages before the background appears when it asks me for username
and password.
I didn't have this error when I installed
Does this bug prevent the system from booting?
When answered, please set this report status back to "confirmed". Thank
you.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is
21 matches
Mail list logo
