Bug#601721: installation-reports: Build w/ /boot partition succeeds, but re-boot fails in fsck 445148
Hi Miguel, Miguel Figueiredo wrote: > i would like to see this tested in with daily images, expert mode > using sid to see if the updated grub makes any difference. > Can you test it and give feedback? What change was made in grub? If it is one that directly addressed the problem described here (partition containing fsck.ext2 being marked in fstab with pass '2' instead of '0'?), that could provide additional motivation for people who experienced this bug to try it. Curious, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#601721: installation-reports: Build w/ /boot partition succeeds, but re-boot fails in fsck 445148
Hi, i would like to see this tested in with daily images, expert mode using sid to see if the updated grub makes any difference. Can you test it and give feedback? -- Melhores cumprimentos/Best regards, Miguel Figueiredo http://www.DebianPT.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#601721: installation-reports: Build w/ /boot partition succeeds, but re-boot fails in fsck 445148
On Fri, Oct 29, 2010 at 12:01 PM, Lennart Sorensen
wrote:
> On Fri, Oct 29, 2010 at 11:08:59AM -0500, Lukasz Szybalski wrote:
>> It seems like Grub.cfg is also using proper drive by UUID.
>>
>> menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian
>> --class gnu-linux --class gnu --class os {
>> insmod part_msdos
>> insmod ext2
>> set root='(hd0,msdos5)'
>> search --no-floppy --fs-uuid --set
>> dec79ed9-b96a-47e4-81f0-7e32735b5057
>> echo 'Loading Linux 2.6.32-5-amd64 ...'
>> linux /vmlinuz-2.6.32-5-amd64 root=/dev/mapper/-root ro
>> quiet
>> echo 'Loading initial ramdisk ...'
>> initrd /initrd.img-2.6.32-5-amd64
>>
>> But somewhere in a boot process system shows:
>>
>> FSCK from Util-Linux-ng 2.17.2
>> unable to resolve UUID=".5b5057
>>
>> (I'm not sure which log after start it would be in :)
>>
>> It seems as the "after system is starting to load" the UUID is not
>> resolved and /dev/sda and /dev/sdb get loaded incorrectly ?
>
> fsck uses /etc/fstab. Now my fstab has entries of UUID=xxx-xxx-xxx
> (no quotes). Perhaps that is the problem. It appears yours has quotes.
>
It does not. That was my typo, sorry:
/etc/fstab
/boot was on /dev/sda5 during installation
UUID=dec79ed9-b96a-47e4-81f0-7e32735b5057 /boot ext2
defaults0 2
# /boot2 was on /dev/sdb1 during installation
UUID=bb0512c5-6de6-4164-a7af-4312a4718ce3 /boot2 ext2
defaults0 2
The temporary solution right now is to change the option (pass) from 2
to 0. Not sure what that does other then checks the FS for corruption
at boot. This will make sure server starts and loads all the services.
UUID=dec79ed9-b96a-47e4-81f0-7e32735b5057 /boot ext2
defaults0 0
Thanks,
Lucas
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#601721: installation-reports: Build w/ /boot partition succeeds, but re-boot fails in fsck 445148
On Fri, Oct 29, 2010 at 11:08:59AM -0500, Lukasz Szybalski wrote:
> It seems like Grub.cfg is also using proper drive by UUID.
>
> menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian
> --class gnu-linux --class gnu --class os {
> insmod part_msdos
> insmod ext2
> set root='(hd0,msdos5)'
> search --no-floppy --fs-uuid --set
> dec79ed9-b96a-47e4-81f0-7e32735b5057
> echo'Loading Linux 2.6.32-5-amd64 ...'
> linux /vmlinuz-2.6.32-5-amd64 root=/dev/mapper/-root ro
> quiet
> echo'Loading initial ramdisk ...'
> initrd /initrd.img-2.6.32-5-amd64
>
> But somewhere in a boot process system shows:
>
> FSCK from Util-Linux-ng 2.17.2
> unable to resolve UUID=".5b5057
>
> (I'm not sure which log after start it would be in :)
>
> It seems as the "after system is starting to load" the UUID is not
> resolved and /dev/sda and /dev/sdb get loaded incorrectly ?
fsck uses /etc/fstab. Now my fstab has entries of UUID=xxx-xxx-xxx
(no quotes). Perhaps that is the problem. It appears yours has quotes.
--
Len Sorensen
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#601721: installation-reports: Build w/ /boot partition succeeds, but re-boot fails in fsck 445148
It seems like Grub.cfg is also using proper drive by UUID.
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian
--class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set dec79ed9-b96a-47e4-81f0-7e32735b5057
echo'Loading Linux 2.6.32-5-amd64 ...'
linux /vmlinuz-2.6.32-5-amd64 root=/dev/mapper/-root ro quiet
echo'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-5-amd64
But somewhere in a boot process system shows:
FSCK from Util-Linux-ng 2.17.2
unable to resolve UUID=".5b5057
(I'm not sure which log after start it would be in :)
It seems as the "after system is starting to load" the UUID is not
resolved and /dev/sda and /dev/sdb get loaded incorrectly ?
Thanks,
Lucas
On Fri, Oct 29, 2010 at 10:10 AM, Lukasz Szybalski wrote:
> What I don't understand is that in squezze the fstab shows:
>
> /etc/fstab
>
> # /boot was on /dev/sda5 during installation
> UUID=dec79ed9-b96a-47e4-81f0-7e32735b5057 /boot ext2
> defaults 0 2
> # /boot2 was on /dev/sdb1 during installation
> UUID=bb0512c5-6de6-4164-a7af-4312a4718ce3 /boot2 ext2
> defaults 0 2
>
> Which means system figured out that the sda and sdb swapped, and used
> the UUID to mount the folders, but why am I still getting the "fsck"
> failed? Is that happening during boot, and fstab is not involved. If
> that's the case which file needs to be modified? I would figure that
> the same process that updated fstab would update the other file? (Is
> the other file a grub file or?)
>
> Thanks,
> Lucas
>
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#601721: installation-reports: Build w/ /boot partition succeeds, but re-boot fails in fsck 445148
What I don't understand is that in squezze the fstab shows: /etc/fstab # /boot was on /dev/sda5 during installation UUID=dec79ed9-b96a-47e4-81f0-7e32735b5057 /boot ext2 defaults0 2 # /boot2 was on /dev/sdb1 during installation UUID=bb0512c5-6de6-4164-a7af-4312a4718ce3 /boot2 ext2 defaults0 2 Which means system figured out that the sda and sdb swapped, and used the UUID to mount the folders, but why am I still getting the "fsck" failed? Is that happening during boot, and fstab is not involved. If that's the case which file needs to be modified? I would figure that the same process that updated fstab would update the other file? (Is the other file a grub file or?) Thanks, Lucas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#601721: installation-reports: Build w/ /boot partition succeeds, but re-boot fails in fsck 445148
On Thu, Oct 28, 2010 at 7:41 PM, Samuel Thibault wrote: > Lukasz Szybalski, le Thu 28 Oct 2010 19:31:51 -0500, a écrit : >> There was no changes to the bios system. The system was installed then >> rebooted. > > Ok. > It may just be a difference between the order in which modules get > loaded from initrd at reboot and modules get loaded by d-i. But in > principle fstab should be filled with UUIDs by default instead of > explicit device names. You have mounted them by hand in partman, right? > I guess what's missing here is to use UUIDs in that case too. > I've mounted /boot partition manually on a sba during installation process, but after reboot /boot partition seem to be on sdb based on what fdisk -l /dev/sdb says. I guess that's what you mean by: "mounted them by hand in partman" The final result is that "server does not boot all the way". It waits for user input. ctrl + D or enter administrative password. Thanks, Lucas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#601721: installation-reports: Build w/ /boot partition succeeds, but re-boot fails in fsck 445148
Lukasz Szybalski, le Thu 28 Oct 2010 19:31:51 -0500, a écrit : > There was no changes to the bios system. The system was installed then > rebooted. Ok. It may just be a difference between the order in which modules get loaded from initrd at reboot and modules get loaded by d-i. But in principle fstab should be filled with UUIDs by default instead of explicit device names. You have mounted them by hand in partman, right? I guess what's missing here is to use UUIDs in that case too. Samuel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#601721: installation-reports: Build w/ /boot partition succeeds, but re-boot fails in fsck 445148
Lukasz Szybalski, le Thu 28 Oct 2010 17:39:59 -0500, a écrit : > 3. Can someone explain why installer mounts sda as my 1GB and sdb as > 1.7TB, but after re-boot system swaps them and uses 1.7TB as /sda and > 1Gb as sdb? It looks like a hardware detection order issue. Do you modify a bios parameter to boot on the installed system instead of the debian installer? You should probably post the output of dmesg. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101028230818.gq4...@const.famille.thibault.fr -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
