Messages during startup

Asked by passionguy

I found some messages during startup of Ubuntu stating about boot loader & its backup & also some other messages. How can i view those messages to analyse if there is any issues.

I have to post those messages bcos there may be some issues that has to be fixed.

Thanks in advance......

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu gparted Edit question
Assignee:
No assignee Edit question
Solved by:
marcobra (Marco Braida)
Solved:
Last query:
Last reply:

This question was reopened

Revision history for this message
Olaf Lenz (olenz) said :
#1

From your message I don't exactly get what kind of output you need. The configuration files of the boot loader can be found in /boot/grub. Look at the file menu.lst, which describes the boot loader.
I don't think there is a file that stores the output of the boot loader.

Otherwise, you can find many logs in /var/log. What might be interesting to you is "dmesg", which gives you all messages of the kernel.

Revision history for this message
passionguy (fayazahmedj) said :
#2

Well this is the message i noticed:

Log of fsck -C -R -A -a
Sun Feb 8 14:22:03 2009

fsck 1.40.2 (12-Jul-2007)
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
There are differences between boot sector and its backup.
Differences: (offset:original/backup)
  430:4e/52, 431:54/65, 432:4c/6d, 433:44/6f, 434:52/76, 435:20/65, 436:69/20
  , 437:73/64, 438:20/69, 439:6d/73, 440:69/6b, 442:73/20, 443:69/6f
  , 444:6e/72, 445:67/20, 446:ff/6f, 447:0d/74, 448:0a/68, 449:44/65
  , 450:69/72, 451:73/20, 452:6b/6d, 453:20/65, 454:65/64, 455:72/69
  , 456:72/61, 457:6f/2e, 458:72/ff, 459:ff/0d, 460:0d/0a, 461:0a/44
  , 462:50/69, 463:72/73, 464:65/6b, 465:73/20, 466:73/65, 467:20/72
  , 468:61/72, 469:6e/6f, 470:79/72, 471:20/ff, 472:6b/0d, 473:65/0a
  , 474:79/50, 475:20/72, 476:74/65, 477:6f/73, 478:20/73, 479:72/20
  , 480:65/61, 481:73/6e, 482:74/79, 483:61/20, 484:72/6b, 485:74/65
  , 486:0d/79, 487:0a/20, 488:00/74, 489:00/6f, 490:00/20, 491:00/72
  , 492:00/65, 493:00/73, 494:00/74, 495:00/61, 496:00/72, 497:00/74
  , 498:00/0d, 499:00/0a, 506:bf/cb, 507:cc/d8
  Not automatically fixing this.

Revision history for this message
Huygens (huygens-25) said :
#3

This whole thing means that you have a partition on a hard disk, or a hard disk with a "Windows" file system (if you know about technology, it is a FAT32 file system, used by Microsoft in its operating systems since Windows 95).
The message then says that on this "Windows" partition there are some errors that it cannot fix automatically. The best and most secure way for you to fix them is: if you have a dual boot with Windows, then boot under windows and if it does not do a "scandisk" (or perhaps it is called a "checkdisk" nowadays) automatically, open your Windows explorer (select My Computer on your desktop), and for each hard disk displayed, right click on it, select "Properties" and in the "Tools" section (if I remember the label correctly) select the first tool which should be something like "Check for errors". Windows might tell you to reboot your computer to make the check. Reboot your computer and choose one last time Windows. Once this is done, you can boot back to Ubuntu and the message you saw should not be there any longer.
If you do not have a dual boot, I cannot help you :-( I am not sure of the proper things to do then...

Revision history for this message
Tom (tom6) said :
#4

I think fsck can be run from the command line but i'm not sure how or what it's parameters are. Sounds like it has some fairly dangerous teeth so take care and use "--help" to look up how to use the command. I tlooks like it only deals with ext3 partitions and not fat32 which i find difficult to believe.

I thought gparted could do a checkdisk without wiping the partition, again i'm not sure how so take care. The ubuntu gparted can't handle ntfs but since we need it for fat32 that's nt a problem.

Good luck and regards from
Tom :)

Revision history for this message
passionguy (fayazahmedj) said :
#5

Thanks for all your reply. I think using the Windows tool is a better option.

Revision history for this message
Tom (tom6) said :
#6

Good plan. It sounds like we know more about the Windows way of fixing this at the moment and if Windows works then that seems the best way right now. Please let us know how you get on and whether that fixes the whole problem or only part of it.

Thanks and regards from
Tom :)

Revision history for this message
passionguy (fayazahmedj) said :
#7

I tried using the Windows tool but it is not fixing up those errors. It said it has replaced some bad clusters nothing else

Thanks..

Revision history for this message
passionguy (fayazahmedj) said :
#8

I can find these messages during startup & i also noticed some other things.

Where i can find these logs?

Revision history for this message
Olaf Lenz (olenz) said :
#9

As I wrote above, you can find most logs in /var/log.

Revision history for this message
Best marcobra (Marco Braida) (marcobra) said :
#10

Your issue seems like this https://answers.launchpad.net/ubuntu/+question/42383 go to the end of thread.

Hope this helps

Revision history for this message
passionguy (fayazahmedj) said :
#11

I hope the link above will solve my issue. Thanks.....

Revision history for this message
passionguy (fayazahmedj) said :
#12

Thanks marcobra, that solved my question.