I have had a dual boot system for 2+ years: suse and windows 7.
I have had no problem booting into it during those 2 years.
Today however while logged into Windows 7, the machine shut down suddenly and from then on
Grub is unable to boot into either suse or windows 7.
The grub menu comes up but when I select windows I get
rootnoverify(hdo,0)
chainloader +1
Error 13: Invalid or unsupported executable format
(rootnoverify(hdo,0)
chainloader +1
is the last entry in menu.lst that boots windows, this was last changed in 2011)
When I run ‘fdisk -l’ I get
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 1 0 0 Empty
Partition 1 does not end on cylinder boundary
/dev/sdb2 1 28046 225279463+ 7 HPFS/NTFS
/dev/sdb3 28047 83357 444280832 7 HPFS/NTFS
/dev/sdb4 * 83358 121601 307194930 f W95 Ext’d (LBA)
/dev/sdb5 83358 84788 11494476 82 Linux swap/Solaris
/dev/sdb6 84789 121599 295684326 83 Linux
Normally, there should be a /dev/sda too, did you edit that out? If so, please don’t, we love complete output, incl. command line.
And, please post output between CODE tags, the # in the editor.
On 2013-03-05, deb2121 <deb2121@no-mx.forums.opensuse.org> wrote:
>
> Hi,
>
> I have had a dual boot system for 2+ years: suse and windows 7.
> I have had no problem booting into it during those 2 years.
> Today however while logged into Windows 7, the machine shut down
> suddenly and from then on
> Grub is unable to boot into either suse or windows 7.
> The grub menu comes up but when I select windows I get
/SNIP/
Hi debbie! I know we’re all asking questions instead of answering yours, but when you say you cannot boot into openSUSE
(as well as Windows) - what do you see? (you only showed us the Windows output) Can you boot into failsafe?
If you really didn’t change the software in any way (why should you?),
then to me this sounds like a hardware problem.
Power-off your PC.
Unplug and re-plug all cables connecting the different devices to the motherboard, like the cables of the hard disk drives.
Does the PC run again thereafter?
A note to others: I presume that the “fdisk” output was generated while booting some sort of live media.
On at least one of my computers, if I boot to USB with a live image, and if what I am booting is either Fedora or Mint, then the USB drive comes up as “/dev/sda” and my hard drive comes up as “/dev/sdb”. There’s a good chance that is what Debbie is seeing.
Sorry. I forgot to mention that I have 2 physically different drives in this machine.
One is on sda and is working fine (i.e. I can boot into the linux that is there).
The other is on sdb and it is the one that has windows 7, and opensuse
No it gives me lots of errors when I pick opensuse to boot. Then near the end it shows
Error reading block 8912914 (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps.
/dev/sdb6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
fsck failed. Mounting root device read-only
System boot control: Running /etc/init.d/boot
Mounting sysfs at /sys
Mounting debugfs at /sys/kernel/debug
Remounting tmpfs at /dev
Initializing /dev
Mounting devpts at /dev/pts
ok
fsck failed. Please repair manually and reboot. The root filesystem is currently mpounted read-only. To remount it read-write do:
That is my suspicion also. You are right I didnt do any changes to the software, was doing something in Windows 7
when it suddenly told me it was shutting down. It went down and now cant boot.
And since I can boot the other physical drive it appears some corruption in one of this drive’s sectors.
I should also add that after mounting opensuse in read-only mode it lets me login as root and
logs me in into
(repair filesystem) #
I am able then to mount the system in read/write mode
On 2013-03-06, deb2121 <deb2121@no-mx.forums.opensuse.org> wrote:
>
> I should also add that after mounting opensuse in read-only mode it lets
> me login as root and
> logs me in into
> (repair filesystem) #
> I am able then to mount the system in read/write mode
Thanks for the additional information. I’m beginning to agree with the growing concensus it’s a hardware problem. The
final `nail’ in the coffin of the hypothesis that the fault is being caused by a grub problem (somehow spontaneously
occurring) is to show you cannot rescue Windows using the recovery disk that you never made :).
I remember seeing this kind of problem before with a similar dualboot system. The problem resulted from a loose cable
to a SATA hard drive and was fixed just by properly plugging it in (as anika suggested). This may not work for you, but
I think it’s a potential solution to exclude sooner rather than later.
>
>Hi Vazhavandan,
>
>Sorry. I forgot to mention that I have 2 physically different drives in
>this machine.
>One is on sda and is working fine (i.e. I can boot into the linux that
>is there).
>The other is on sdb and it is the one that has windows 7, and opensuse
>
>Thanks
>
>debbie
>
>vazhavandan;2532095 Wrote:
>> As far as i know openSUSE installer partitions the hardisks as sdas and
>> flash/pen/thumb drives as sdbs
>> Example :-
>> ‘[image: http://i.imgur.com/1IbUz00l.png]’ (http://imgur.com/1IbUz00)
Accurate and complete reports of commands and responses in code blocks
really helps. It is in the advanced editor, access with the # button i
think. I am from nntp land so i don’t really know.
Maybe. Certainly the very next thing to do is BACKUP all of the
partitions on that drive RIGHT NOW.
Then we can experiment with recovery. I think is a file damage kind of
thing that hit the boot sector. But that is a very touchy thing to mess
with. I think it is fixable though.
>
>Hi NRickert,
>
>The output was generated by running fdsk from my other drive (running
>linux).
>I did unplug all the cables and back but same thing
>
>Thanks
>
>debbie
>
This is consistent with my expectations/guesses. BACKUP NOW. If the disk
is headed south do it while you still have time. It may have been a wild
write though, run FSCK from a bootable CD or Memory stick. Not kidding.
>nrickert;2532283 Wrote:
>> That would be my guess, also.
>>
>> A note to others: I presume that the “fdisk” output was generated
>> while booting some sort of live media.
>>
>> On at least one of my computers, if I boot to USB with a live image,
>> and if what I am booting is either Fedora or Mint, then the USB drive
>> comes up as “/dev/sda” and my hard drive comes up as “/dev/sdb”.
>> There’s a good chance that is what Debbie is seeing.
