Boot-Repair scans system indefinitely

Bug #1064323 reported by YannUbuntu

This bug report was converted into a question: question #690261: Boot-Repair scans system indefinitely, what can i do ?.

20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Boot-Repair
Invalid
Undecided
YannUbuntu

Bug Description

After launching Boot-Repair, the "Scanning system" little window appears, the pulsate bar moves, but this situation remains indefinitely.
This is probably due to the hanging of one of the tools (parted, fdisk, os-prober, mount...) used by Boot-Repair.
Example that shows it may be due to parted: http://ubuntuforums.org/showpost.php?p=12385060&postcount=7

If you meet this problem, please check possible errors in the output of the 'sudo boot-repair -d' command.

WORKAROUND:
Some users reported the problem was solved after:
- disabling the floppy drive in the BIOS
- or rebooting the PC
- or fixing the filesystem ( http://forum.ubuntu-fr.org/viewtopic.php?pid=11056641#p11056641 )

YannUbuntu (yannubuntu)
Changed in boot-repair:
status: New → Incomplete
importance: Undecided → Medium
assignee: nobody → YannUbuntu (yannubuntu)
YannUbuntu (yannubuntu)
Changed in boot-repair:
importance: Medium → Undecided
YannUbuntu (yannubuntu)
description: updated
Revision history for this message
Yamis (yamisf) wrote :

Boot-repair scanned forever at scanning os-probe so I closed it and tried opening gpparted it scanned forever too and I found this bug report:
https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/155047
Disabled the floppy drive that didn't exist in the bios started boot-repair and it worked.

Revision history for this message
YannUbuntu (yannubuntu) wrote :

Thanks a lot Yamis.
Then this issue would probably come from parted...

Yamis, on which Ubuntu version did you have this bug ?

description: updated
Revision history for this message
Rob Hills (rhills) wrote :

I've also experienced this bug today, running Ubuntu 13.04 from a Live usb stick.
Boot-repair eventually finished scanning, but it took 20 mins or so. This computer doesn't have a FDD but it does have a /dev/fd0 so I suspect it may be related to that. I'll check the BIOS when I reboot.

Revision history for this message
Rob Hills (rhills) wrote :

Oops, should have checked the terminal output before my previous post:

ubuntu@ubuntu:~$ /dev/mapper/isw_cgjfhjagba_HW_RAID_0: unrecognised disk label
/dev/sda: unrecognised disk label
/dev/sdc: unrecognised disk label

So, it appears it isn't related to /dev/fd0 at all.

YannUbuntu (yannubuntu)
Changed in boot-repair:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers