Re: hard disk failure

not really. there are tools to recover data, but only 2 copies of the file table. On Fri, Feb 24, 2012 at 8:46 AM, Michael Havens wrote: > well, I hard-rebooted before this malfunction and (while I don't think it > was) it might have been writing something to disk. No we all know the > importance

Re: hard disk failure

well, I hard-rebooted before this malfunction and (while I don't think it was) it might have been writing something to disk. No we all know the importance of a proper shutdown! Does windows have something similar with their hardware or if this were to happen with them would you be up the creek w/o

Re: hard disk failure

Not always. I have used refurbished disks before without issue. Could also have been a brown out. On Feb 23, 2012 10:01 PM, "Michael Havens" wrote: > that's what I get for buying a refurbished disk eh? > > On Thu, Feb 23, 2012 at 9:49 PM, James Mcphee wrote: > >> Usually happens on a bad sh

Re: hard disk failure

usually when a superblock goes bad, it is because the drive was turned off in the middle of some write operations. since there more than one copy of the primary superblock, the filesystem should be recoverable. some orphaned files will be written to Lost & Found for you to look at. If more than

Re: hard disk failure

that's what I get for buying a refurbished disk eh? On Thu, Feb 23, 2012 at 9:49 PM, James Mcphee wrote: > Usually happens on a bad shutdown. Or dying disk. But more often a bad > shutdown. > > On Thu, Feb 23, 2012 at 8:53 PM, Michael Havens wrote: > >> Please, Speculate as to why my supe

Re: hard disk failure

Usually happens on a bad shutdown. Or dying disk. But more often a bad shutdown. On Thu, Feb 23, 2012 at 8:53 PM, Michael Havens wrote: > Please, Speculate as to why my superblock went bad. > > --- > PLUG-discuss mailing list - PLUG-discuss@lists

Re: hard disk failure

Please, Speculate as to why my superblock went bad. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

Re: hard disk failure

From: Michael Havens > If e2fs is saying that the first backup superblock is at 32768, why do > you multiply it by 4 to get the real superblock backup location? Because ext23 filesystems can have block sizes other than 4K. In the old days, when disks and files were smaller, there were some advan

Re: hard disk failure

Yipee it worked! Now I don't have to set the network up again! -- :-)~MIKE~(-: --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailm

Re: hard disk failure

if e2fs is saying that the first backup superblock is at 32768 why do you multiply it by 4 to get the 'real super block backup location? Why doesn't e2fs do the multiplication to give the 'real' location? Is that a bug? If so I think that can be easily fixed. Not by me ( don't have the know-how) bu

Re: hard disk failure

From: Michael Havens > "sudo e2fsck -b block_number /dev/xxx" > The first backup superblock was at 131072. Are other > backup blocks located every 131072? No. dumpe2fs /dev/mapper/vg-usr32 | grep 'Backup super' Backup superblock at 32768 Backup superblock at 98304 Backup superblock at 16

Re: hard disk failure

How do you copy a backup superblock to the primary position? Or how so you tell the computer to look at a backup superblock?. there it is! (here) "sudo e2fsck -b block_number /dev/ xxx" I have a question

Re: hard disk failure

okay I ran fsck /dev/sda1 but it comes back with fsck.ext2: unable to set superblock flags on ubuntu ext 2? that's not right. I think it is ext 4 maybe 3 so I sat here and thought I would try fsck.ext4 and it is a program. hm so it says that some group ddescriptors are wong and

Re: hard disk failure

ah, yeah that one too. there are so many test tools these days. :) -eric On Feb 18, 2012, at 10:28 AM, Matt Graham wrote: >> technomage.ha...@gmail.com> wrote: >>> now I remember what the other tool was: hdparm. that tool will tell >>> you what the SMART status is on the HDD. > From: Michael H

Re: hard disk failure

st immediately if there are any problems). I know there is another > >> command line tool that can test drive throughput and read the SMART tables > >> on the controller. I can't remember its name off hand, but it is a good > >> one to test the drive electroni

Re: hard disk failure

yipee! 'mount -o sb=131072 /dev/sda1 /mnt/sda1' mounted the drive and I can now browse the folders. So, how do I copy the backup superblock to the primary superblock? Time to google this... so while trying to fix it I found out what the problem really is with debugfs There is a bad magic number in

Re: hard disk failure

> technomage.ha...@gmail.com> wrote: >> now I remember what the other tool was: hdparm. that tool will tell >> you what the SMART status is on the HDD. From: Michael Havens > It seems to me everything is good. > hdparm /dev/sda1 hdparm won't tell you about the SMART status on a disk. I think yo

Re: hard disk failure

throughput and read the SMART tables on the controller. I can't remember its name off hand, but it is a good one to test the drive electronics. -eric On Feb 17, 2012, at 10:05 AM, Michael Havens wrote: Yep I think I had a hard disk failure. I res

Re: hard disk failure

>> to test the drive electronics. >> >> -eric >> >> On Feb 17, 2012, at 10:05 AM, Michael Havens wrote: >> >> Yep I think I had a hard disk failure. I restarted my computer and >>> was presented with: >>> >>> error: u

Re: hard disk failure

throughput and read the SMART tables > on the controller. I can't remember its name off hand, but it is a good one > to test the drive electronics. > >> > >> -eric > >> > >> On Feb 17, 2012, at 10:05 AM, Michael Havens wrote: > >> > >&

Re: hard disk failure

off hand, but it is a good one to test >> the drive electronics. >> >> -eric >> >> On Feb 17, 2012, at 10:05 AM, Michael Havens wrote: >> >>> Yep I think I had a hard disk failure. I restarted my computer and was >>> presented with: >>>

Re: hard disk failure

n the controller. I can't remember its name off hand, but it is a good one to test the drive electronics. -eric On Feb 17, 2012, at 10:05 AM, Michael Havens wrote: Yep I think I had a hard disk failure. I restarted my computer and was presented with: error: unknown filesystem.

Re: hard disk failure

off hand, but it is a good one > to test the drive electronics. > > -eric > > On Feb 17, 2012, at 10:I don't think 05 AM, Michael Havens wrote: > > > Yep I think I had a hard disk failure. I restarted my computer and > was presented with: > > > >

Re: hard disk failure

controller. I can't remember its name off hand, but it is a good one to test the drive electronics. -eric On Feb 17, 2012, at 10:05 AM, Michael Havens wrote: > Yep I think I had a hard disk failure. I restarted my computer and was > presented with: > > error: u

Re: hard disk failure

I just ran gparted on /dev/sda and it lists sda1 as an unknown filesystem. It is 27Gigs /dev/sda3 is about 10 gigs and then the swap is 1 gig. On Fri, Feb 17, 2012 at 1:58 PM, Michael Havens wrote: > tune2fs -l /dev/sda1 says Bad magic number in super-block while trying to > open /dev/sda1 > out

Re: hard disk failure

tune2fs -l /dev/sda1 says Bad magic number in super-block while trying to open /dev/sda1 out of curiosity I decided to run this with my other partitions and all of them returned the bad magic number error except sda3 (that is my clones drive. sda2 is swap. And I ran this command: dd if=/dev/

Re: hard disk failure

sorry to offend anyone I meant no offense. I have no desire for what I said to actually take place. It was an off-handed comment meant for humour. Again I do appologize for offending anyone. On Fri, Feb 17, 2012 at 1:31 PM, Nathan England wrote: > ** > > > > It greatly saddens me, Michael

Re: hard disk failure

It greatly saddens me, Michael, that you feel so familiar with the members of the Phoenix Linux Users Group public email list that you are comfortable making such a disgusting comment. I joined this public mailing list to learn about linux many years ago, to contribute to the group as a membe

Re: hard disk failure

That's right ET! I am very bad! I need to be punished. NOt by you though. Find me a cute Asian chick to o... I need to get my mind out of the gutter! Anyways: tune2fs -l /dev/sda1 says Bad magic number in super-block while trying to open /dev/sda1 out of curiosity I decided to run this wit

Re: hard disk failure

which means bad disk. Right? Wrong... It means "Bad operator", don't blame the tools... :) What does: tune2fs -l /dev/sdaN says? ET Michael Havens writes: 30 gigs is what it was that might be bad. I ran it against one partition rather than the whole disk so it should be smaller..

Re: hard disk failure

30 gigs is what it was that might be bad. I ran it against one partition rather than the whole disk so it should be smaller... shouldn't it be? another thing I tried to mount sda1 abd it tells me that I need to specify the file type so I try with ext4, 3, and 2 but they all returned with t

Re: hard disk failure

is this a 30GB disk? if so... This looks perfect. Otherwise, I hope your block size was something other than the default 512 bytes. Kevin On Fri, 2012-02-17 at 11:07 -0700, Michael Havens wrote: > On Fri, Feb 17, 2012 at 10:17 AM, kitepi...@kitepilot.com > wrote: > Another (NON destruc

Re: hard disk failure

So far so good. Make sure you ran dd against the WHOLE drive: dd if=/dev/sdX of=/dev/null ET Michael Havens writes: On Fri, Feb 17, 2012 at 10:17 AM, kitepi...@kitepilot.com < kitepi...@kitepilot.com> wrote: Another (NON destructive) check you may to do: as root: dd if=/dev/{your partiti

Re: hard disk failure

; (6 differant partitions) and then '!!!Cannot find a valid root filesystem' I'm running your dd command right now and it has been running like 2 minutes. On Fri, Feb 17, 2012 at 10:05 AM, Michael Havens wrote: Yep I think I had a hard disk failure. I rest

Re: hard disk failure

On Fri, Feb 17, 2012 at 10:17 AM, kitepi...@kitepilot.com < kitepi...@kitepilot.com> wrote: > Another (NON destructive) check you may to do: > as root: > dd if=/dev/{your partition} of=/dev/null > Your HD will (most likely) be OK if it finishes without other error than > "read beyond EOF" (or some

Re: hard disk failure

do: > as root: > dd if=/dev/{your partition} of=/dev/null > Your HD will (most likely) be OK if it finishes without other error than > "read beyond EOF" (or something like that) > ET > > > Michael Havens writes: > >> Yep I think I had a hard disk fa

Re: hard disk failure

' I'm running your dd command right now and it has been running like 2 minutes. On Fri, Feb 17, 2012 at 10:05 AM, Michael Havens wrote: > Yep I think I had a hard disk failure. I restarted my computer and was > presented with: > > error: unknown filesystem. >

Re: hard disk failure

Another (NON destructive) check you may to do: as root: dd if=/dev/{your partition} of=/dev/null Your HD will (most likely) be OK if it finishes without other error than "read beyond EOF" (or something like that) ET Michael Havens writes: Yep I think I had a hard disk

Re: hard disk failure

all goes well, then again: mount -t{your filesystem type} /dev/{my partition} /mnt chroot /mnt grub-install /dev/{my partition} (elevate a prayer...) exit reboot Best of luck... ET Michael Havens writes: Yep I think I had a hard disk failure. I restarted my computer and was presented