Bad Magic Number in Superblock - Any trick for Arch or for new kernels?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Guys,

	I have a disk on a arch box that has gone south. No prior warning, no smart
errors, no nothing. Granted the drive is 5-6 years old, so a complete crater is
not out of the question.

The situation:

	On reboot - grub 22 error
	boot arch install cd 2009-08, cannot mount drive
	partition table shows 1 partition /dev/hda1 (PATA drive) (should be 3)
	(I can't put my hands on the saved 'fdisk -l' data, it's somewhere)
	gparted 0.46 (0.44 wont work) - loads, but only shows a single partition
	fsck -> Gives the bad magic number in superblock error, tries backup same error
	Booted without issue for over a year

	From the looks of it, the drive scattered. But my question is "Is there
something with all the recent kernel changes that would require troubleshooting
this drive error in a different way than usual?"

	I know there have been a lot of changes in moving modules into the kernel, but
I don't know what got moved (if anything related to drives), or how it might
affect my troubleshooting.

	Before I add the drive to the heap of drives in my 'dead drive box' are there
any other silver bullets I should try to try and resurrect the drive? (Data
isn't an issue, it's all backed up :-)

	What say the gurus?

-- 
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux