hard disk/smart errors?

Kramdra · May 10, 2009, 2:39am

Hello, Im a new user, have been using for only a few days, a little amazed at how easy opensuse has been to set up compared to the latest ubuntu and my previous attempt with slackware 8.

Anyway Ive had high number of smart errors in /var/log/messages. I dont know if this is normal but anyway heres the grep output:

/var/log/messages:May  8 00:54:36 linux smartd[3617]: Device: /dev/sda [SAT], 1 Offline uncorrectable sectors                                                                                               
/var/log/messages:May  8 01:24:36 linux smartd[3619]: Device: /dev/sda [SAT], 1 Offline uncorrectable sectors                                                                                               
/var/log/messages:May  8 02:01:22 linux-hiij smartd[6243]: Device: /dev/sda [SAT], 1 Offline uncorrectable sectors                                                                                          
/var/log/messages:May  8 10:15:25 linux-hiij smartd[2675]: Device: /dev/sda [SAT], 1 Offline uncorrectable sectors                                                                                          
/var/log/messages:May  8 10:20:49 linux-hiij smartd[2677]: Device: /dev/sda [SAT], 1 Offline uncorrectable sectors                                                                                          
/var/log/messages:May  8 10:50:49 linux-hiij smartd[2693]: Device: /dev/sda [SAT], 1 Offline uncorrectable sectors                                                                                          
/var/log/messages:May  8 10:57:00 linux-hiij smartd[2758]: Device: /dev/sda [SAT], 1 Offline uncorrectable sectors                                                                                          
/var/log/messages:May  8 11:06:13 linux-hiij smartd[2679]: Device: /dev/sda [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 11:36:13 linux-hiij smartd[2725]: Device: /dev/sda [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 11:57:45 linux-hiij smartd[2664]: Device: /dev/sda [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 12:27:45 linux-hiij smartd[2722]: Device: /dev/sda [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 12:57:45 linux-hiij smartd[2722]: Device: /dev/sda [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 13:27:45 linux-hiij smartd[2722]: Device: /dev/sda [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 13:57:45 linux-hiij smartd[2722]: Device: /dev/sda [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 14:27:45 linux-hiij smartd[2722]: Device: /dev/sda [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 14:57:45 linux-hiij smartd[2722]: Device: /dev/sda [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 15:21:45 linux-hiij smartd[2766]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 15:51:45 linux-hiij smartd[2898]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 16:34:46 linux-hiij smartd[2831]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 16:54:22 linux-hiij smartd[2950]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 17:24:22 linux-hiij smartd[2967]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 17:54:22 linux-hiij smartd[2967]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 18:24:22 linux-hiij smartd[2967]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 18:54:23 linux-hiij smartd[2967]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 19:24:22 linux-hiij smartd[2967]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 19:54:22 linux-hiij smartd[2967]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 20:24:23 linux-hiij smartd[2967]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 20:54:22 linux-hiij smartd[2967]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 21:24:22 linux-hiij smartd[2967]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 21:54:22 linux-hiij smartd[2967]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 22:24:22 linux-hiij smartd[2967]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 22:54:22 linux-hiij smartd[2967]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 23:24:23 linux-hiij smartd[2967]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  8 23:54:22 linux-hiij smartd[2967]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 00:24:22 linux-hiij smartd[2967]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 00:54:22 linux-hiij smartd[2967]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 01:24:23 linux-hiij smartd[2967]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 01:50:12 linux-hiij smartd[2987]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 01:54:53 linux-hiij smartd[2942]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 01:56:46 linux-hiij smartd[2917]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 12:33:00 linux-hiij smartd[2942]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 13:07:28 linux-hiij smartd[2936]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 13:28:57 linux-hiij smartd[2921]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 13:37:51 linux-hiij smartd[2913]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 13:50:40 linux-hiij smartd[2931]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 14:20:41 linux-hiij smartd[2951]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 14:50:40 linux-hiij smartd[2951]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 15:20:40 linux-hiij smartd[2951]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 15:50:41 linux-hiij smartd[2951]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 16:20:40 linux-hiij smartd[2951]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 18:22:57 linux-hiij smartd[2809]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 18:52:58 linux-hiij smartd[2950]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 19:22:57 linux-hiij smartd[2950]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 19:52:57 linux-hiij smartd[2950]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 20:22:58 linux-hiij smartd[2950]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 20:52:57 linux-hiij smartd[2950]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 21:22:57 linux-hiij smartd[2950]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 21:52:58 linux-hiij smartd[2950]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 22:22:57 linux-hiij smartd[2950]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 22:52:57 linux-hiij smartd[2950]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 23:22:58 linux-hiij smartd[2950]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May  9 23:52:57 linux-hiij smartd[2950]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May 10 00:22:57 linux-hiij smartd[2950]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May 10 00:52:58 linux-hiij smartd[2950]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
/var/log/messages:May 10 01:22:57 linux-hiij smartd[2950]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors

but from my limited experience of maxtor drives, the smart info means nothing, usually is random

edit: looking at the times I notice some patterns.

So the question I have is do these sectors get marked as bad by smartd? in which case I might turn it off/disable smart in bios, since I dont think it is accurate…

thanks
Mark

baskitcaise · May 10, 2009, 4:07am

Kramdra adjusted his/her AFB on Sunday 10 May 2009 01:46 to write:

>
>
> --------------------
>
>
> but from my limited experience of maxtor drives, the smart info
> means nothing, usually is random
>
> edit: looking at the times I notice some patterns.

The reason there are time patterns is due to the frequency that the log is
generated and also how often smart is checked.

>
> So the question I have is do these sectors get marked as bad by smartd?
> in which case I might turn it off/disable smart in bios, since I dont
> think it is accurate…

You could always check the disk with the maxtor test-suite and let it mark
them as bad

smart does not alter the disk at all it just checks it, if you put

man:smart

in the Konqueror location bar it is all explained ( and quite readable or a
change )

<<–snip–>>

smartd will attempt to enable SMART monitoring on ATA devices (equivalent to
smartctl -s on) and polls these and SCSI devices every 30 minutes
(configurable), logging SMART errors and changes of SMART Attributes via the
SYSLOG interface. The default location for these SYSLOG notifications and
warnings is /var/log/messages. To change this default location, please see
the ´-l´ command-line option described below.

>>–pins–<<

HTH

–
Mark

Nullus in verba
Nil illigitimi carborundum

Kramdra · May 10, 2009, 8:17pm

thanks, maybe I done something wrong but heres a couple of problems. This is my spare pc:

First try installing: grub went in the right place (begging of root partition) but windows boot sector on other drive got corrupted somehow. (displayed YoYo instead of booting)
Windows tools didnt fix it, FixNTLDR boot disk almost but said winnt\system corrupted.

I made 100mb partitions for grub (should have done this to start with), mounted at /boot.
In SUSE install grub chose to put itself on other drive (I dont remember any options about grub in the installer!) completely overwriting windows boot. grub wont boot the new installed linux, but it can boot windows 2000, so one problem is fixed

So to get linux working I will take out the windows drive and reinstall oSUSE, so grub can only go in one place, then I will have a grub on each drive.

my work pc: installed fine, but now my NTFS vista partition is corrupted? It can boot in safemode, and does chkdsk with no errors. If I try to boot normally it bluescreens at Ntfs.sys “page fault at non paged area”. I think this might of happened after turning SMART off in the bios.

Is the NTFS driver stable in linux? I am thinking I should make my windows partitions mounted read only just incase.

Also, i dont know why, but my ntfs partitions wont mount anymore… the fat32 still does.

fstab:


UUID=                swap                 swap       defaults              0 0
UUID=464de31d-fb79-462c-bc92-2314f35ef487 /                    ext3       acl,user_xattr        1 1
UUID=ec749a30-1fbc-4f3f-9e44-51872afad55c /boot                ext3       acl,user_xattr        1 2
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0
/dev/disk/by-id/ata-Maxtor_6B200M0_*******-part1 /home/kram/S200-2                ntfs-3g    uid=1000,gid=100,umask=0007,locale=en_GB.UTF-8 0 0
/dev/disk/by-id/ata-WDC_WD2500SB-*******_WD-*******-part2 /home/kram/IDE0-2    ntfs-3g    uid=1000,gid=100,umask=0007,locale=en_GB.UTF-8 0 0
/dev/disk/by-id/ata-WDC_WD2500SB-*******_WD-*******-part1 /home/kram/IDE0-FAT  vfat       uid=1000,gid=100,umask=0007,utf8=true 0 0
/dev/disk/by-id/ata-Maxtor_6B250S0_*******-part2 /home/kram/S250-Backup           ntfs-3g    uid=1000,gid=100,umask=0007,locale=en_GB.UTF-8 0 0
/dev/disk/by-id/ata-Maxtor_6B250S0_*******-part1 /home/kram/S250-Xp               ntfs-3g    uid=1000,gid=100,umask=0007,locale=en_GB.UTF-8 0 0
/dev/disk/by-id/ata-Maxtor_6Y160M0_*******-part1 /home/kram/S160-Vista            ntfs-3g    uid=1000,gid=100,umask=0007,locale=en_GB.UTF-8 0 0
/dev/disk/by-id/ata-Maxtor_6Y160M0_*******-part2 /home/kram/S160-2                ntfs-3g    uid=1000,gid=100,umask=0007,locale=en_GB.UTF-8 0 0

Thanks
Mark

baskitcaise · May 10, 2009, 9:50pm

Kramdra adjusted his/her AFB on Sunday 10 May 2009 19:26 to write:

>
> thanks, maybe I done something wrong but heres a couple of problems.
> This is my spare pc:
>
> First try installing: grub went in the right place (begging of root
> partition) but windows boot sector on other drive got corrupted somehow.
> (displayed YoYo instead of booting)
> Windows tools didnt fix it, FixNTLDR boot disk almost but said
> winnt\system corrupted.
>
>
> I made 100mb partitions for grub (should have done this to start with),
> mounted at /boot.
> In SUSE install grub chose to put itself on other drive (I dont
> remember any options about grub in the installer!) completely
> overwriting windows boot. grub wont boot the new installed linux, but it
> can boot windows 2000, so one problem is fixed
>
> So to get linux working I will take out the windows drive and reinstall
> oSUSE, so grub can only go in one place, then I will have a grub on each
> drive.

Another thing i would do while you have the drives out is with just the
windows one in place give it a check with the maxtor disk check from maxtor.

I have a sneaky feeling maybe one of you disks is either failing or does
have bad sectors, hence the smart warnings.

Probably why you can get into Windows in safe but not in normal start, might
have some corrupted files on there that only load in full blown boot.

I have a vista install on a drive here that is showing exactly the same
problem just have not got round to fixing yet ( I have not even booted to it
for weeks it is only there as I needed it for some trouble shooting ) this
drive also throws smart errors.

>
>
>
> my work pc: installed fine, but now my NTFS vista partition is
> corrupted? It can boot in safemode, and does chkdsk with no errors. If I
> try to boot normally it bluescreens at Ntfs.sys “page fault at non paged
> area”. I think this might of happened after turning SMART off in the
> bios.

Nah, smart does nothing for the O/S, it is totally independent, you
theoretically can have a machine where the O/S knows nothing at all of smart
but if the BIOS itself finds errors and thinks the disk is going to fail it
will alert you with a warning sound even if you have not started the O/S.

I think the sound itself is generated by the drive, not 100% on that but I
have heard it and it sounded like a quiet high pitched buzz.

>
>
> Is the NTFS driver stable in linux? I am thinking I should make my
> windows partitions mounted read only just incase

If you do not intend to move loads of big files around between linux an Win
then a halfwat house fat32 partition ids the safest way and leave ntfs read
only.

>
> Also, i dont know why, but my ntfs partitions wont mount anymore…
> the fat32 still does.

Wait till you have scanned and see what the result is

HTH

–
Mark

Nullus in verba
Nil illigitimi carborundum

Kramdra · May 10, 2009, 10:02pm

I found the maxtor/wd and even worse the seagate tools only see the IDE drive, IDK why.
I scanned the vista partition for bad sectors, not sure if it finnished as it normally reboots after scan, so I came back it was in linux…

But you have the same vista bluescreen at ntfs.sys?

Thanks

baskitcaise · May 11, 2009, 11:34am

Kramdra adjusted his/her AFDB on Sunday 10 May 2009 21:06 to write:

>
> I found the maxtor/wd and even worse the seagate tools only see the IDE
> drive, IDK why.

might not be capable to see the SATA interface?

not sure on the way you have your SATA set in the BIOS, Have not used many
manufacturers tools for a while but maybe if you set SATA as legacy in bios
the test app might see it as a pata???

> I scanned the vista partition for bad sectors, not sure if it finnished
> as it normally reboots after scan, so I came back it was in linux…
>
> But you have the same vista bluescreen at ntfs.sys?

No I just get a continuous repair, reboot, fail, reboot, repair circle I
have not investigated much as i do not need he drive or O/S, it was on old
drive I had from a now defunct laptop that I needed to get some data of and
so have it hanging on my SATA, this does throw smart errors but until I need
it I am not bothered.

HTh

–
Mark

Nullus in verba
Nil illigitimi carborundum

Kramdra · May 15, 2009, 5:40pm

Vista will now boot but only if I have booted into linux first. Vista wont restart straight back into vista

This is crazy - windows partitions are read only! I cant understand it :o

baskitcaise · May 15, 2009, 8:51pm

Kramdra adjusted his/her AFDB on Friday 15 May 2009 16:46 to write:

>
> Vista will now boot but only if I have booted into linux first. Vista
> wont restart straight back into vista
>
> This is crazy - windows partitions are read only! I cant understand it
> :o
>
>

What did you do to get it to even boot vista?

What happens when you choose vista from the grub menu?

Any errors?

When you say it will only boot after you have booted SuSE do you mean you
have to boot all the way to KDE/Gnome and then choose vista from the Leave
menu?

–
Mark

Nullus in verba
Nil illigitimi carborundum