Author Topic: bad magic number in superblock--system unusable.  (Read 623 times)

Offline dougmack

  • Hero Member
  • *****
  • Posts: 1001
Re: bad magic number in superblock--system unusable.
« Reply #30 on: May 23, 2013, 04:14:19 PM »
Here's the stanza:

title windows
root (hd0,0)
makeactive
chainloader +1

It looks like the system is directed to boot Windows, since what happens is the usual start of a Windows8 boot: A black screen with
a small 4-paned window icon in the middle, with (either) white or blue (I forget which) panes, as if daylight was coming in the window.
That's what I called a "cellar window," because that's what it reminds me of.  Then, while the window is still on screen, a little
bunch of white dots goes around in a circular formation for some seconds, then that and the window goes out. Then after a little while,
the black screen turns into very dark blue, and remains that way forever. What should happen, instead, is that a "wallpaper" of a
lighthouse would come up after just a few seconds, and then you have to push the "Windows" key to get a log-in prompt.
So I don't think it's a Linux problem, I think something happened to Windows while I was in never-never land.  I need to
somehow restore Windows to normal operation.
I can access the Windows partition from Konqueror super user. I see there's a directory called Recovery, and in that directory are two
subdirectories with gibberish names--some kind of encripted stuff, I guess. (These might even be the files that installed Win 8 in the first place.)
Somebody familiar with Windows and not afraid of Linux could probably fix Windows from this access point, but I don't know where
I'd find such a person.  All Windows people seem to shun Linux like it was bubonic plague!
--doug
Blessed are the peacemakers...for they shall be shot at from both sides.  A. M. Greeley

Offline Yankee

  • Hero Member
  • *****
  • Posts: 1517
  • In theory, theory=practice, in practice ???
Re: bad magic number in superblock--system unusable.
« Reply #31 on: May 23, 2013, 05:13:13 PM »
title Windows
 rootnoverify (hd0,0)
 chainloader +1

I don't have Windows on here but for Windows 8...
the above should work.    Does df from terminal
show /dev/sda1 for Windows 8   ?

Boot away then.
ASUS EeePc 900HA netbook  1.6 Ghz Atom CPU  1GB RAM
160 GB internal HD    Seagate 250 GB USB portable drive 
Intel ‎Mobile 945GSE Integrated Graphics Controller
Atheros AR242x/AR542x Wireless Network Adapter
Intel (N10/ICH7 Family) High Definition Audio
Dynex 5-Button Wired Optical Mouse
LXDE

Offline kjpetrie

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 4037
Re: bad magic number in superblock--system unusable.
« Reply #32 on: May 23, 2013, 05:49:58 PM »
Did this ever get corrected?

Quote
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Warning: invalid flag 0xffff of partition table 5 will be corrected by w(rite)

It's unlikely anything has happened to your Windows installation when it's not been used, but there's obviously something it doesn't know how to deal with and a corrupt partition table could be the sort of thing that might cause that.
-----------
KJP
-----------------------------------------------------------
PClos64 RC1 on Intel D945GCLF2 motherboard (Atom 330), 2GB DDR2 RAM, Maxtor STM325031, HL-DT-ST DVDRAM GSA-H42N, Amilo LSL 3220T monitor. Also Acer 5810TG (with custom kernel) and Asus eeePC 2G surf

Offline dougmack

  • Hero Member
  • *****
  • Posts: 1001
Re: bad magic number in superblock--system unusable.
« Reply #33 on: May 23, 2013, 06:57:47 PM »
I tried the modification suggested by Yankee, to no effect.
The complaint in fdisk no longer appears, however, Dolphin cannot access the Windows partition now, and neither can Konqueror.
Before the present reboot to try and boot Windows, I could see the Windows partition. Dolphin puts up a complaint:

An error occurred while accessing 'Windows', the system responded:
org.freedesktop.Hal.Device.Volume.UnknownFailure: The disk contains an unclean
file system (0, 0). Metadata kept in Windows cache, refused to mount. Failed to
mount '/dev/sda1': Operation not permitted The NTFS partition is in an unsafe
state. Please resume and shutdown Windows fully (no hibernation or fast
restarting), or mount the volume read-only with the 'ro' mount option.

I did see a similar message along the way since I last opened Windows, but I don't know exactly when. Obviously I don't have the option
of shutting down Windows "fully"--I thought I had done that, actually, the last time i looked at it--since i can't start it in the first place.

Tried fsck with bad result--maybe I'm not doing it right? Or maybe it can't check ntfs?

[root@linux1 doug]# fsck /dev/sda1
fsck from util-linux-ng 2.18
fsck: fsck.ntfs: not found
fsck: Error 2 while executing fsck.ntfs for /dev/sda1

Maybe I can run a Windows chkdsk from a Windows install disk? Don't know what it would do when it encounters the mbr.

I think maybe the Windows problem is independent of the problem this thread was intended to address, but of course, I
still want to get it to work, and since it's sort of constrained within a Linux environment, I guess the folks here are the ones I must
ask for assistance.  Since I certainly don't want to bork the Linux systems again!

--doug
Blessed are the peacemakers...for they shall be shot at from both sides.  A. M. Greeley

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11688
  • ----IOFLU----
Re: bad magic number in superblock--system unusable.
« Reply #34 on: May 23, 2013, 07:09:34 PM »
dougmack:

Do you have these installed?

Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline Yankee

  • Hero Member
  • *****
  • Posts: 1517
  • In theory, theory=practice, in practice ???
Re: bad magic number in superblock--system unusable.
« Reply #35 on: May 23, 2013, 07:13:36 PM »
I tried the modification suggested by Yankee, to no effect.

I want to say too !

Install testdisk from Synaptic and test that partition.
I don't know what else would test it.    Don't do anything
else to it yet.    Hopefully you have a working backup
for that if needed.      Some other ideas later.
ASUS EeePc 900HA netbook  1.6 Ghz Atom CPU  1GB RAM
160 GB internal HD    Seagate 250 GB USB portable drive 
Intel ‎Mobile 945GSE Integrated Graphics Controller
Atheros AR242x/AR542x Wireless Network Adapter
Intel (N10/ICH7 Family) High Definition Audio
Dynex 5-Button Wired Optical Mouse
LXDE

Offline dougmack

  • Hero Member
  • *****
  • Posts: 1001
Re: bad magic number in superblock--system unusable.
« Reply #36 on: May 23, 2013, 11:49:55 PM »
Time out for an apparent overheat problem. Tried to reboot the machine, and got no video at all, not
even from the BIOS on turn on.  But I took off the cover and let it cool, and now it's up in PCLOS.
Put a big table fan on the open computer, and now it boots into Windows. Sorry for the bum steer.
I've never had an overheat problem before, and it's warm but not that hot here today--maybe 80°
in the house. Time for the compressed air, I guess.

Before trying again to boot Windows, I did run testdisk /dev/sda1, but got no output that it did anything, so I don't know if it did. The man and --h pages for testdisk are about useless.

I don't have any restore disk for Win 8 as yet, but I'm going to see how to make one and do so.

Thanx for the inputs and your patience!

--doug
Blessed are the peacemakers...for they shall be shot at from both sides.  A. M. Greeley

Offline Yankee

  • Hero Member
  • *****
  • Posts: 1517
  • In theory, theory=practice, in practice ???
Re: bad magic number in superblock--system unusable.
« Reply #37 on: May 24, 2013, 07:06:11 PM »

Before trying again to boot Windows, I did run testdisk /dev/sda1, but got no output that it did anything, so I don't know if it did. The man and --h pages for testdisk are about useless.


from the root terminal it's     #testdisk /dev/sda
then enter on proceed, enter on intel, enter on analyse

Read any fatal errors there, like corrupt partition, drive
read error, etc..

The quick search is optional I'd say as it looks for partitions to restore
but hit enter, then Y, to take a look, then enter to quit.
ASUS EeePc 900HA netbook  1.6 Ghz Atom CPU  1GB RAM
160 GB internal HD    Seagate 250 GB USB portable drive 
Intel ‎Mobile 945GSE Integrated Graphics Controller
Atheros AR242x/AR542x Wireless Network Adapter
Intel (N10/ICH7 Family) High Definition Audio
Dynex 5-Button Wired Optical Mouse
LXDE