Hardware :: Check Hard Disk For Errors. Possible Hard Disk Failure?
Jun 21, 2011
I was using Terminal and browsing a directory in my home folder. My "home" directory is located on "/dev/sdb1". When in Terminal I typed "ls" in one of my directories and the output was garbage. The output didn't show the files in the directory. I think it said something like, "input/output error". Unfortunately, I didn't write the exact error down. Instead I rebooted.The hard disk with the problem is:
$ sudo hdparm -I /dev/sdb
[sudo] password for brian:
after installing Ubuntu on one WD 500 GB hard disk and after making mistake and pasting wrong code into Terminal:my OTHER WD 500 GB hard disk that was also in the system (I guess it was "hd1") - died.The problem must be, I guess, I typed wrong code: "hd1,1" instead of "hd0,0".)500 GB (NTFS) of data was on that other (non-Ubuntu) hard disk, and now I can not access it anymore. While booting, system gives "Hard Disk Error" warning and stops.One again: I installed Ubuntu od one hard disk and at the end of instalation I pasted wrong code for GRUB, giving address of another hard disk. Now that other hard disk has error and will not work
I have a sata 320 gb with mandriva linux 2009.1 on it.And it is what curently atached to my cpu. It is shown as 'sda' in the partition table.I also have another 40gb hard disk with windows xp installed on it.It is shown as 'hda' in the partition table . Now what i want to do is attach this 40gb hard disk to my pc and configure grub on my 320gb hard disk('sda') so as to boot windows xp(which is residing on the second hard disk,'hda')Can anyone tell me if what im doing is feasible or not? If it is feasible,can anyone suggest me how to get it working. I know i just need to add 2-3 lines to my grub.conf, but dont know what exactly i need to write.
I had a dual boot (windows 7 + debian), both of them installed in my internal hard disk, with the GRUB in it. I have recently installed a second linux distro (mint), but I put it in an external hard disk. Now the GRUB allows me to boot any of the three operating systems, but I need the external disk to do it. It seems that after the mint installation the GRUB is now working from the external disk (if the external disk is not connected, the machine does not boot.) �Is there a way to change the location of the GRUB, to the internal hard disk of my laptop?
On my FC11 installation Palimpset Disk Utility icon in the top menu bar is reporting that I have a disk failure with the caption "one or more disks is failing".When I open up the details section in Pilimpset I can see that "2 sectors are failing",I have checked this with gparted checking facility and it reports that the disk is OK.What I would like to do is to check the disk using a command like tool or ofline tool, which would then tell me where those bad sectors are on that partition so that I can resize it (using gparted) and have the bad sectors in NON ALLOCATED DISK SPACE.
I looking for advice on what is the best way for backup on opensuse in case hard disk failure .
I have opensuse as server running samba (with some share folder) and mysql and web service. for mysql backup I run cron job using automysqlbackup script that run 3 times a day (morning , lunch , evening).
in case of hard disk failure, I wish to be put every things on new hard disk in 1or 2 hours.
[System: OpenSuSE 11.0 , kernel 184.108.40.206-0.7-pae, athlon i386] I've recently begun to have problems with my Sata Hitachi disk drive; it stores all my documents and music etc. I've only begun to notice these problems when I installed the Ex2 IFS driver for Windows so I could access my data (read only) from my Windows disk. However, the problem is not exclusive to Windows; Windows blue-screens when the Sata link goes down, but SuSE attempts to re-establish a link. Here's the dmesg output (only includes output relevant to disk activity). I've also run smartcl on the disk, here's the output. Note that the output says that it's soft-resetting the link. Any clues as to what this may infer? Also, the system has sometimes failed to boot as it sees the disk as corrupted and asks me to perform a fsck, which rewrites the journal (although this may or may not have been down to the aforementioned driver possibly not playing nice with the journal, even though it is in read only mode) and restores the disk to working order.
I can have periods of days where the disk works perfectly fine on both Windows and SusE, and random events where the disk link goes down for some reason. The situation seems to be remedied by me physically pushing the Sata cable into the disk and motherboard., and returns when the computer tower is subject to a considerable vibration from a slight knock et cetera. On the other hand, this may be a power problem, some ends on a rail are faulty on my PSU and will only give power to my optical drives if they are positioned in a certain angle, although this is probably less likely as the disks don't go offline, just the link.
I am just wondering if there are any tools for checking the life of the hard disk. I had my hard disk for 4 years. And now I think it is having some problems.Is there any tools I can use to check the condition of the hard disk?
Is there any other way to check the overall size of the hard disk other than just fdisk -l? This is because the cloud server that my company has purchased is supposed to have 50GB of hard disk size,It shows that it has two SCSI drives, only both summing up to 50GBs. So what is the second SCSI drive, and why is it divided that way? dev/sda and dev/sdb???
I am running CentOS with single hard-disk (no RAID). I frequently saw people lost data because of hard-disk damage or failure.I am wondering if there is a software for monitoring the hard-disk so that we would know in advance and do the backup because thing goes wrong.
I had a set of rather unusual problems on installing a new 500Gb hard drive on my F14 system, I've solved them, but they were that unusual that I thought I should share them in case anyone else gets the same thing! I'd been experiencing intermittent faults on one of my drives, (lock ups for no reason, occasional boot ups that failed due to ' disk unreadable errors' and other odd errors). I assumed that the drive was failing, but it always showed 'Heathy' on disk utility! This was the disk with the OS on, plus my main 'data' disk had some bad sectors, so I thought I'd buy a nice big 500Gb and reinstall the whole system.
I backed up all my data to an external 'USB' drive, opened the case, (a big old under the table 'desktop', why do they still call them 'desktops'?) shoved in the new SATA drive and rebooted, intending to format the new drive to EXT4 and partitioning it before installing F14 again! OOOOOOOOOW! Major drive failure, missing OS, whole list of SDB errors! Control D, to reboot, BIOS only sees one drive; SDA (I have three, two IDE and one SATA) plus the one I just put in makes four. I go into BIOS and discover that it not only cant see any of the other drives, but my two DVD drives are missing too!
Now I've been building my own systems and mucking about with computers since before you could buy them, and Ive never seen a problem like this one! At first I thought the new drive had screwed my system, for on removal, the problem persisted! Then I noticed that the IDE connector in drive SDB, (the long 40 pin job) was just slightly out of line with the back of the drive, pushed it firmly in and what do you know, everything works! We moved recently and I think the vibration was enough to loosen the connector to give intermittent faults, and pulling the cables about to get the new drive in, pulled it out further......
after my upgrades i noticed one hard drive was acting funny i was gonna reformat the drive anyway to totally remove winblows from my system grub was installed on the boot sector of the drive that failed how can i get the next drive in line to boot if some one can get me to a howto or tell me what i need to do short there of reinstalling the operating system.
One of my SATA hard disks stopped responding in the middle of a rsync file transfer to it. I had to kill the process. After that I am unable to mount that partition. I am using Ubuntu 9.10 x86_64 version. Here are the error messages and what I have tried:
~$ sudo mount /dev/sdb1 mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so
Here I am at a loss! Is there any way to force checking of the file system and to recover the data I have in there? I have tried the solution posted in [URL], but e2fsck -b <my superblock number> /dev/sdb1 shows "Journal version not supported by this e2fsck."
I have 10.04 desktop basically running xbmc sabnzbd and as a file server. the loads aren't too large as it is just for my house. But i moved from a server install to the desktop because of sound issues and running xbmc at start was a bit of a pain... so bit of background done.
My problem is that after installing 10.04 i got the disk utility pop-up saying one of samsung spinpoint 1tb (HD103UJ) has a critical error... now i didn't panic (although in the next couple of months i am intending to get another drive) but in the meantime i am simply wondering if this is a false flag? i've been getting this error for over 6 months now... pretty much from the last time i formatted the disk, i wiped it and then used dd to copy over a smaller partition, after which i used gparted to grow the partition to the whole drive. could this have created a false flag?
The 184 error is the only one, here is all the data i can glean from my system, attached is a screen of the relevent info from the disk utility, and this it from smartctl:
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
I recently bought 320 GB Trancend external hard disk and working fine days back.Earlier i could copy from and to the hard disk with out any issue. I dont know what happened after that now i am not able to write any files in to the external hard disk. This is not NTFS formatted device. here is some of the out put from terminal.
Code: sundar@sundar-sundar:~$ fdisk -l Disk /dev/sda: 120.0 GB, 120034123776 bytes
I have two internal harddisk. Harddisk 1 has ubuntu, fedora installed and harddisk 2 has ubuntu installed. I normally connect either one, and use it. How can i always keep connect both harddisks, and at the start, select from which harddisk to boot? Or it's not possible?
is there a way to write/unpack .qcow2 hard disk image directly to real hard drive in Linux?(I know it's possible to unpack .qcow2 to .raw and then dd to drive, but I'd like to skip .raw since its large)
I created a thread about a problem a I had with my hard disk clicking whilst idle little while ago and I may now have stumbled upon a possible solution. The strange thing with the problem is that Ubuntu/Kubuntu didn't cause this problem but Opensuse 11.2 does.
I installed Fedora 13 to have a glimpse of what all the fuss was about and noticed that I had the same problem (hard disk clicking whilst idle ~ every 20 secs or so). Now there's a wiki on this subject and a few bug reports: [url]
Some ATA harddrives perform very frequent head unloads under Linux significantly shortening their lifespans. Root cause
The inactivity timer for head unload is configured too aggressively either via ATA APM (Advanced Power Management) feature or other non-standard means. Such aggressive settings are very fragile to changes in IO pattern and under Linux many such drives unload their heads only to re-load them shortly. Note that this relentless unloading/reloading cycle can also be triggered under Windows by installing programs which can alter the IO pattern (e.g. certain vaccine programs which runs in background).
Now two of the listed models with this problem are basically identical to my model (Dell Inspiron 1520) and basically share the same hardware: Dell Vostro 1500 and XPS 1520.
The workaround listed is to:
set APM to 254
Furthermore, there is a script: Storage-Fixup which can also be downloaded from opensuse software search. Indeed there is a report of this for a Vostro 1500: Gmane Loom
The report suggests looking at: Disk Power Management - openSUSE which lists a method to create a configuration file to management disk power management:
My question is whether I could download the storage-fixup rpm [url] has a description of it and it can be found: Software.openSUSE.org) and install it to (hopefully) solve the issue or should I follow the method given in: Disk Power Management - openSUSE
ran out of space in my /home dir. Have a second hard drive to install and would like to designate it as additional space for /home. I do not want to mount it as a dir inside my home I would like it to simply work as though my /home simply has more space available to it.
I'm trying to resize a partition on an IDE hard disk to use the entire disk but can not get more than a 309GB partition. I can get 295, 300, 301, 302GB, etc... fine but start getting problems with anything over 309GB. I get the following error with 310GB or more:
error: block relocator should have relocated 533 Warning: You should reinstall your boot loader before rebooting. Read section 4 of the Parted User documentation for more information. I am using Slackware 12.1, GNU parted 1.8.8, ext2 filesystem.
I had a hard disk used entirely for data archiving (no os files in there!) and it just failed, so I opened up the PC case and removed it. The problem is that I had set it to be automounted on startup (specified in /etc/fstab), and now when Fedora is loading it outputs an fsck error "cannot find/locate a superblock in /dev/sdb1" (that is the removed drive) and it throws me to a "maintenance terminal". I tried to remove the /dev/sdb1 entry from /etc/fstab, but the system wouldn't let me save the new file because the filesystem was in read-only mode.