Re: HD com BAD BLOCKS???
2011/9/1 Henrique de Moraes Holschuh escreveu: 2. O HD remapeia esses setores para setores spare, portanto o S.O. nunca vai encontrar um setor em que não pode *escrever* (ele remapeia na escrita, ou quando é um disco muito bom, remapeia preventivamente durante um offline test ou long test se for difícil de ler o setor direito). Se o badblocks encontra um setor com defeito permanente no modo de _escrita_, jogue o disco fora. O disco VAI retornar erro de leitura se você tentar ler um setor que está ruim e que ele ainda não remapeou. Mas na primeira escrita lá, ele remapeia e o setor não dá mais defeito. Por outro lado, o setor remapeado vai estar longe, muitas vezes no final do disco. Eu tive um problema recente com HD e quero reforçar aqui a informação do Henrique. Esse negócio de fsck para procurar bad blocks é coisa dos anos 90. Hoje em dia os discos tem inteligência suficiente para lidar sozinhos com setores ruins e o computador usando o HD nem fica sabendo. Como ele disse, se chegar ao ponto de que um fsck achou badblocks é porque o disco já deveria ter ido pro lixo há muito tempo. Assim, se o relatório SMART falou que tem setores ruins, é porque tem. Mas isso não tem a menor importância, já que setores ruins acontecem e o HD cuida deles sozinho movendo os dados para setores bons. Se a quantidade de setores ruins reportados pelo SMART está aumentando dia a dia, aí sim você sabe que seu HD deu defeito. -- Bruno Schneider http://www.dcc.ufla.br/~bruno/ -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAP1wdQv=oycspgx9=yr9tur9uek-38ry-1tznhi8l99t7gy...@mail.gmail.com
Re: HD com BAD BLOCKS???
Ola, Não vi nada de grave nas saídas que o Moksha enviou. A não ser pode 5 Reallocated_Sector_Ct 0x0033 100 100 036Pre-fail Always - 3 Que indica que o S.M.A.R.T. realocou 3 setores. Importante e verificar se esse número aumenta com o tempo e com que taxa. Precisa espera que os testes completem antes de fazer outra. tanto o short quanto o long, informam o tempo que o teste ira demorar. Depois disso rode um smartctl -a (ou opções mais especificas para ver o relatório de teste) Isso aqui que e um registro de erro. No caso, foi alguma falha no comunicação SATA. Error 16 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was active or idle . After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 53 00 8e d6 1f e0 Error: ICRC, ABRT at LBA = 0x001fd68e = 2086542 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- c8 00 2e 61 d6 1f e0 00 00:01:54.340 READ DMA c6 00 10 00 00 00 e0 00 00:01:54.340 SET MULTIPLE MODE 91 00 3f 00 00 00 ef 00 00:01:54.340 INITIALIZE DEVICE PARAMETERS [OBS-6] 10 00 00 00 00 00 e0 00 00:01:54.340 RECALIBRATE [OBS-4] 00 00 01 01 00 00 a0 00 00:01:53.950 NOP [Abort queued commands] Para um melhor diagnóstico, use a ferramenta do fabricante, normalmente disponível no site. Paulino Kenji Sato -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/camm-fmhbth-zes3vtsaewwhr7dfc4b9zvxafrgn+rvqm5ve...@mail.gmail.com
Re: HD com BAD BLOCKS???
Em quinta-feira 01 setembro 2011, às 17:41:26, Henrique de Moraes Holschuh escreveu: 3. Não monte disco Seagate em nenhuma posição que não seja horizontal, virado para cima. Você tem 50% de chance de ter um Seagate amaldiçoado (fabricado com componentes ainda piores que a média), ele se ofender com a posição vertical e eventualmente sofrer uma tempestade de setores ruins e finalmente o click da morte. Já vi em =1TB, famílias 11, 12 e ES.2. E eu que achava que só maxtor era uma @#@$#% . E agora que eu vi que o hd do meu note é seagate! :O 4. Disco não perdoa fonte e cabo de força ruim, e esses problemas causam danos estranhos na gravação de forma imprevisível. Levam inclusive a danos permanentes no HDD. 5. Cabo SATA ruim não causa bad-sector (tem CRC, tanto o chipset quanto o disco sabem que o cabo está melando a bitstream). O kernel chia, e muito, quando isso acontece. 6. Vibração, seja de baixa ou de alta frequência, e principalmente impactos, são muito perigosos para a saúde do HDD. 7. HD trabalha quente, mas não muito. Mantenha eles abaixo de 45°C e tente evitar altas amplitudes térmicas. Não precisa manter gelado, isso é lenda e o Google provou com um estudo em dezenas de milhares de HD. smartctl --xall mostra os limites térmicos e histórico térmico do HD (SATA), etc. 8. Os lotes malditos não são lenda, existem, e isso foi comprovado no estudo do Google. Mas como são lotes, nem sempre estão relacionados com um MODELO de HDD. Mesmo os modelos bons podem ter lotes ruins, e modelos ruins podem ter lotes bons que não dão defeito nenhum. O que me impressionou nesse estudo do google é o aspecto ou vai ou racha dos hds entre 3 meses a 1 ano. http://labs.google.com/papers/disk_failures.pdf -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201109021719.58470.fcann...@gmail.com
Re: HD com BAD BLOCKS???
Henrique, passei pela situação que você descreveu com um HD Externo da Iomega - Seagate 1Tb. À época o disco estava na garantia e me deram um novo, que desde então já desconectou algumas vezes assim como o outro fazia antes do click da morte. Uma vez que o HD vem com suporte para mantê-lo na posição vertical, sempre considerei que esta fosse a posição mais adequada - evitar aquecimento talvez, não sei -, mas vou fazer o teste e usá-lo na horizontal daqui em diante. Muito grato por esta informação, o medo de perder este novo HD me persegue dia-a-dia. André Nunes Batista Blog: http://tagesuhu.wordpress.com/ PGP Public Key: 0x7b0590cb6722cf80 2011/9/1 Henrique de Moraes Holschuh h...@debian.org: Nessas horas, você só vai garantir seu direito se _realmente_ souber do que está falando. Então vamos lá: 1. O SMART tem a palavra final. Se ele diz que o disco tem setores ruins, ou que já havia sido ligado n vezes, e já tinha x horas de uso, é verdade. O que não serve para NADA é a opinião do SMART de que o disco está OK (por outro lado, se ele disser que está ruim, é porque está a ponto de explodir em pedaçinhos). Se a quantidade de setores ruins crescer mais que algumas dezenas POR ANO, o disco precisa ser trocado. 2. O HD remapeia esses setores para setores spare, portanto o S.O. nunca vai encontrar um setor em que não pode *escrever* (ele remapeia na escrita, ou quando é um disco muito bom, remapeia preventivamente durante um offline test ou long test se for difícil de ler o setor direito). Se o badblocks encontra um setor com defeito permanente no modo de _escrita_, jogue o disco fora. O disco VAI retornar erro de leitura se você tentar ler um setor que está ruim e que ele ainda não remapeou. Mas na primeira escrita lá, ele remapeia e o setor não dá mais defeito. Por outro lado, o setor remapeado vai estar longe, muitas vezes no final do disco. 3. Não monte disco Seagate em nenhuma posição que não seja horizontal, virado para cima. Você tem 50% de chance de ter um Seagate amaldiçoado (fabricado com componentes ainda piores que a média), ele se ofender com a posição vertical e eventualmente sofrer uma tempestade de setores ruins e finalmente o click da morte. Já vi em =1TB, famílias 11, 12 e ES.2. 4. Disco não perdoa fonte e cabo de força ruim, e esses problemas causam danos estranhos na gravação de forma imprevisível. Levam inclusive a danos permanentes no HDD. 5. Cabo SATA ruim não causa bad-sector (tem CRC, tanto o chipset quanto o disco sabem que o cabo está melando a bitstream). O kernel chia, e muito, quando isso acontece. 6. Vibração, seja de baixa ou de alta frequência, e principalmente impactos, são muito perigosos para a saúde do HDD. 7. HD trabalha quente, mas não muito. Mantenha eles abaixo de 45°C e tente evitar altas amplitudes térmicas. Não precisa manter gelado, isso é lenda e o Google provou com um estudo em dezenas de milhares de HD. smartctl --xall mostra os limites térmicos e histórico térmico do HD (SATA), etc. 8. Os lotes malditos não são lenda, existem, e isso foi comprovado no estudo do Google. Mas como são lotes, nem sempre estão relacionados com um MODELO de HDD. Mesmo os modelos bons podem ter lotes ruins, e modelos ruins podem ter lotes bons que não dão defeito nenhum. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110901204125.gb12...@khazad-dum.debian.net -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAAKmMzGba=fuvpzlmt4+ykbt_bds5bs1i5qbtc6pqrdjxoe...@mail.gmail.com
Re: HD com BAD BLOCKS???
On Fri, 02 Sep 2011, Fabricio Cannini wrote: Em quinta-feira 01 setembro 2011, às 17:41:26, Henrique de Moraes Holschuh escreveu: 3. Não monte disco Seagate em nenhuma posição que não seja horizontal, virado para cima. Você tem 50% de chance de ter um Seagate amaldiçoado (fabricado com componentes ainda piores que a média), ele se ofender com a posição vertical e eventualmente sofrer uma tempestade de setores ruins e finalmente o click da morte. Já vi em =1TB, famílias 11, 12 e ES.2. E eu que achava que só maxtor era uma @#@$#% . Na minha experiência, no momento só existe (existia?) UM fabricante de HDD SATA 3.5 que presta: Hitachi. Já os HDD SAS de 2,5 10k RPM, nenhum deu defeito ainda (e acho que alguns são Seagate). Veremos. E agora que eu vi que o hd do meu note é seagate! :O Não sei se os HDDs de notebook da Seagate tem o mesmo problema que os de 3,5. No caso dos SATA de 3,5, é realmente 50% de chance do HDD ter defeito de fabricação, e quebrar antes do tempo. O que me impressionou nesse estudo do google é o aspecto ou vai ou racha dos hds entre 3 meses a 1 ano. http://labs.google.com/papers/disk_failures.pdf Sim. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110903014102.ga...@khazad-dum.debian.net
HD com BAD BLOCKS???
Boa tarde amigos de lista! Estou super entrigado com uma coisa... Há alguns meses comprei dois HDs de 1.5 TB para meu computador, passados alguns meses eu resolvi instalá-los e finalmente fazer uso deles, pois bem, tenho a mania de de tempos em tempos verificar o utilitário de disco que já vem no sistema e com isso verificar o status do SMART dos discos plugados em minha máquina, infelizmente o utilitário acusou que os meus dois discos novos de 1.5 TB continham setores defeituosos. Fiz dois testes que me recomendaram aqui neste forum, um foi o *e2fsck -fcv /dev/sdax* e não foram encontrados nenhum bad block e o outro e mais demorado foi o: *badblocks -o encontrados.dat -w -v /dev/sdax* e após 30 horas de verificação também recebi o retorno de que nenhum bad block foi encontrado mas mesmo assim fui ao fornecedor que me vendeu os HDs para análise e troca, após dois dias de verificação o fornecedor verificou que um HD realmente estava com bads mas o outro não, sendo assim, retornei com um HD novo trocado e o outro que já tinha instalado na minha máquina. Quando voltei a plugá-los de cara quando verifiquei novamente o status do SMART, o utilitário de disco indicava que os dois discos estavam bons mas no dia seguinte o HD que eu havia levado ao fornecedor e o mesmo dissera que segundo os testes deles o HD estaria bom, voltou a dar que o disco continham setores ruins. Voltei a fazer os testes com os mesmos comandos citados acima e novamente recebi a informação de que não foram encontrados nenhum badblock. E agora, em quem devo confiar? Posso confiar nos testes que fiz e ter a certeza de que meus discos não possuem BADs? E que diabos de utilitário é esse que está sempre me dizendo que o disco está com setores ruins mas é desmentido pelos testes de checagem que realizo. Esse diagnóstico do utilitário de discos do linux é realmente confiável? Se alguém puder me ajudar eu ficaria muito agradecido. Abraços, Moksha tux
Re: HD com BAD BLOCKS???
2011/9/1 Moksha Tux gova...@gmail.com: Boa tarde amigos de lista! Estou super entrigado com uma coisa... Há alguns meses comprei dois HDs de 1.5 TB para meu computador, passados alguns meses eu resolvi instalá-los e finalmente fazer uso deles, pois bem, tenho a mania de de tempos em tempos verificar o utilitário de disco que já vem no sistema e com isso verificar o status do SMART dos discos plugados em minha máquina, infelizmente o utilitário acusou que os meus dois discos novos de 1.5 TB continham setores defeituosos. ... Voltei a fazer os testes com os mesmos comandos citados acima e novamente recebi a informação de que não foram encontrados nenhum badblock. E agora, em quem devo confiar? Posso confiar nos testes que fiz e ter a certeza de que meus discos não possuem BADs? E que diabos de utilitário é esse que está sempre me dizendo que o disco está com setores ruins mas é desmentido pelos testes de checagem que realizo. Esse diagnóstico do utilitário de discos do linux é realmente confiável? Se alguém puder me ajudar eu ficaria muito agradecido. Abraços, Ola, como esta verificando o status do S.M.A.R.T. ? (qual o nome no utilitário, e qual a informação pertinente?) Ou, e a bios do computador que esta emitindo o alerta ? Uma das características do S.M.A.R.T. e se auto corrigir, muitas vezes fazendo ruido similar a o de quando esta sendo acessado, isso ocorre mesmo sem ter o cabo de dados conectado (basta ligar a alimentação). E essa e uma situação normal. Qual a marca e o modelo dos HDs? Usando o smartmontools: Obtem informações sobre o HD smartctl -i /dev/sda Para verificar o status smartctl -a /dev/sda Fique ciente de que a interpretação de alguns dos parâmetros depende do fabricante. O importante e o relatório de erros, apresentado após os parâmetros. A severidade depende do tipo de erro. Faz o auto teste rápido smartctl -t short /dev/sda Faz o auto teste demorando smartctl -t long /dev/sda -- Paulino Kenji Sato -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAMM-fMhuZKvtJiHBVSMNSBrcr1XZKNM=1uhhhqihxb3qrep...@mail.gmail.com
Re: HD com BAD BLOCKS???
Nessas horas, você só vai garantir seu direito se _realmente_ souber do que está falando. Então vamos lá: 1. O SMART tem a palavra final. Se ele diz que o disco tem setores ruins, ou que já havia sido ligado n vezes, e já tinha x horas de uso, é verdade. O que não serve para NADA é a opinião do SMART de que o disco está OK (por outro lado, se ele disser que está ruim, é porque está a ponto de explodir em pedaçinhos). Se a quantidade de setores ruins crescer mais que algumas dezenas POR ANO, o disco precisa ser trocado. 2. O HD remapeia esses setores para setores spare, portanto o S.O. nunca vai encontrar um setor em que não pode *escrever* (ele remapeia na escrita, ou quando é um disco muito bom, remapeia preventivamente durante um offline test ou long test se for difícil de ler o setor direito). Se o badblocks encontra um setor com defeito permanente no modo de _escrita_, jogue o disco fora. O disco VAI retornar erro de leitura se você tentar ler um setor que está ruim e que ele ainda não remapeou. Mas na primeira escrita lá, ele remapeia e o setor não dá mais defeito. Por outro lado, o setor remapeado vai estar longe, muitas vezes no final do disco. 3. Não monte disco Seagate em nenhuma posição que não seja horizontal, virado para cima. Você tem 50% de chance de ter um Seagate amaldiçoado (fabricado com componentes ainda piores que a média), ele se ofender com a posição vertical e eventualmente sofrer uma tempestade de setores ruins e finalmente o click da morte. Já vi em =1TB, famílias 11, 12 e ES.2. 4. Disco não perdoa fonte e cabo de força ruim, e esses problemas causam danos estranhos na gravação de forma imprevisível. Levam inclusive a danos permanentes no HDD. 5. Cabo SATA ruim não causa bad-sector (tem CRC, tanto o chipset quanto o disco sabem que o cabo está melando a bitstream). O kernel chia, e muito, quando isso acontece. 6. Vibração, seja de baixa ou de alta frequência, e principalmente impactos, são muito perigosos para a saúde do HDD. 7. HD trabalha quente, mas não muito. Mantenha eles abaixo de 45°C e tente evitar altas amplitudes térmicas. Não precisa manter gelado, isso é lenda e o Google provou com um estudo em dezenas de milhares de HD. smartctl --xall mostra os limites térmicos e histórico térmico do HD (SATA), etc. 8. Os lotes malditos não são lenda, existem, e isso foi comprovado no estudo do Google. Mas como são lotes, nem sempre estão relacionados com um MODELO de HDD. Mesmo os modelos bons podem ter lotes ruins, e modelos ruins podem ter lotes bons que não dão defeito nenhum. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110901204125.gb12...@khazad-dum.debian.net
RE: how to find bad blocks
pastebin.com/f5a5c595a i just started badblocks -w -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1266236447.26031.8.ca...@ubuntu
RE: how to find bad blocks
Date: Wed, 10 Feb 2010 00:39:35 -0600 From: s...@hardwarefreak.com To: debian-user@lists.debian.org Subject: Re: how to find bad blocks Vadkan Jozsef put forth on 2/9/2010 11:44 AM: Besides the badblocks app? We have a samsung hdd, that keeps falling out of raid, but there are no bad blocks on it, according to badblocks prog. This is probably because there are no bad blocks on it. we would like to return it [warranty], but it would be better to find e.g. bad blocks on it..:\ :D If falling out of raid means your hardware PCI/X/e/mobo mounted real RAID card is taking this drive off line, usually this is because of a firmware issue. The firmware on the RAID card doesn't want to play with the firmware on the drive. This most often happens when a drive of dissimilar brand/make/model/size/fw_rev is added into an existing array of identical drives, or a group of identical drives is used but the controller doesn't like the drive firmware rev, period. In either case, good drives will be kicked off line by the controller. I went through a wacky case of this back in the late 1990s with Mylex DAC960 cards kicking Seagate ST118202LC drives off-line once a week (or more). Five DAC960s and 40 identical drives. Those DAC960s just didn't like that ST118202 firmware. These were U2W 80MB/s drives and the DAC960s were limited to UW or 40MB/s. Both Mylex and Seagate tech support said this was not the problem, that is was a firmware bug in the drives unrelated to bus speed. Took a while but we eventually got all the drives replaced. That is the most array rebuilding I've ever done, or probably ever will. To get RMA authorization in this situation usually only requires telling the vendor what RAID controller you're using and what drive configuration. It always helps if you bought all components from the same vendor, and helps even more if you got a verbal or written commitment that the card and drives would work together in the configuration you had planned. If it's a low ball no name vendor that doesn't sell both RAID cards and drives, they may tell you to yourself, that the drive is fine. This is one huge disadvantage of using low end vendors and why corporations usually buy the bulk of their hardware from a single vendor. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Use 'fsck.ext3' _ Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. https://signup.live.com/signup.aspx?id=60969
Re: how to find bad blocks
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vadkan Jozsef wrote: We have a samsung hdd, that keeps falling out of raid, but there are no bad blocks on it, according to badblocks prog. we would like to return it [warranty], but it would be better to find e.g. bad blocks on it..:\ :D As others wrote, use the smartctl program from smartmontools. I had some strange problems with a samsung drive, I bought recently. I just run 'long' smartctl tests on the drive and it would fail them. I sent the drive back with the output of 'smartctl -a /dev/whatever' and got a replacement from the shop. HTH, Johannes === SMART Self-test log structure revision number 1 Num Test_DescriptionStatus Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offlineCompleted: read failure 90% 265 1651557882 # 2 Extended offlineCompleted: read failure 90% 221 1651557882 # 3 Short offline Completed: read failure 20% 171 1651557882 # 4 Extended offlineCompleted: read failure 90% 171 1651557882 # 5 Extended offlineCompleted: read failure 90% 168 1651557882 # 6 Short offline Completed without error 00% 165 - # 7 Short offline Aborted by host 10% 165 - # 8 Short offline Completed without error 00% 161 - # 9 Short offline Aborted by host 90% 161 - #10 Extended offlineCompleted: read failure 40% 150 165100 #11 Extended offlineCompleted: read failure 50% 141 1170387107 #12 Extended offlineCompleted: read failure 50% 130 1170387107 #13 Extended offlineCompleted without error 00% 108 - #14 Extended offlineInterrupted (host reset) 40%96 - #15 Extended offlineCompleted: read failure 40%83 1651556392 #16 Extended offlineCompleted: read failure 50%57 1334488458 #17 Extended offlineCompleted: read failure 50%52 1334488458 === - -- Johannes In questions of science, the authority of a thousand is not worth the humble reasoning of a single individual. - - Galileo Galilei, physicist and astronomer (1564-1642) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAktyexoACgkQC1NzPRl9qEWM5QCePoHcL85JNhGe+uwiQeQTbdIO MzAAnR/hwJP62YDQm3NtOFl0Px3D3ldH =LJoT -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
how to find bad blocks
Besides the badblocks app? We have a samsung hdd, that keeps falling out of raid, but there are no bad blocks on it, according to badblocks prog. we would like to return it [warranty], but it would be better to find e.g. bad blocks on it..:\ :D thank you! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RE: how to find bad blocks
-Original Message- From: Vadkan Jozsef [mailto:jozsi.avad...@gmail.com] Sent: Tuesday, 09 February, 2010 08:44 To: Debian User Mailing list Subject: how to find bad blocks Besides the badblocks app? We have a samsung hdd, that keeps falling out of raid, but there are no bad blocks on it, according to badblocks prog. we would like to return it [warranty], but it would be better to find e.g. bad blocks on it..:\ :D thank you! Can you get SMART data from it? I don't think you can list the bad blocks that the drive is re-mapping, but you can certainly get the number of times the drive has had to do that. The manpage for smartctl describes how to query individual disks behind various RAID controllers. HTH James Zuelow Network Specialist City and Borough of Juneau MIS (907)586-0236 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: how to find bad blocks
On 10-02-09 12:44:02, Vadkan Jozsef wrote: Besides the badblocks app? We have a samsung hdd, that keeps falling out of raid, but there are no bad blocks on it, according to badblocks prog. we would like to return it [warranty], but it would be better to find e.g. bad blocks on it..:\ :D thank you! This is probably a job for S.M.A.R.T., try `smartctl -a /dev/whatever` and look at 196 Reallocated_Event_Count, 197 Current_Pending_Sector, and 198 Offline_Uncorrectable raw values, and any WHEN_FAILED or logged errors. If all is OK, then look to your system logs for I/O errors. -- TonyN.:' mailto:tonynel...@georgeanelson.com ' http://www.georgeanelson.com/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: how to find bad blocks
Hi, On Tue, 09 Feb 2010 18:44:02 +0100 Vadkan Jozsef jozsi.avad...@gmail.com wrote: We have a samsung hdd, that keeps falling out of raid, but there are no bad blocks on it, according to badblocks prog. Did you use the write scan? (parameter -w for destructive write, -n for non-destructive write -- both cannot be used on mounted devices). Cheers Stephan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: how to find bad blocks
#include hallo.h * James Zuelow [Tue, Feb 09 2010, 08:58:15AM]: Can you get SMART data from it? I don't think you can list the bad blocks that the drive is re-mapping, but you can certainly get the number of times the drive has had to do that. The manpage for smartctl describes how to query individual disks behind various RAID controllers. And if that doesn't work then you can use dd_rescue to copy the data to another harddisk and store the list of bad blocks on-the-fly. If you need to know which files are damaged, in many cases you can later use that bad block list to retrieve the file list with debug / administrative tools for particular file system. Regards, Eduard. -- Joey Jeder, der mich verwirrt, muss einen oeffentlichen Security-Bug fixen und einen Absatz fuer's DWN schreiben. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: how to find bad blocks
On Tue, 09 Feb 2010 18:44:02 +0100, Vadkan Jozsef wrote: Besides the badblocks app? We have a samsung hdd, that keeps falling out of raid, but there are no bad blocks on it, according to badblocks prog. we would like to return it [warranty], but it would be better to find e.g. bad blocks on it..:\ :D You can use the manufacturer's tools provided for that same purpose. I dunno for Samsung, but Seagate has SeaTools¹ (only ata/sata) that can be run from a live cd and works with other hard disk brands. ¹ http://www.seagate.com/www/en-us/support/downloads/seatools Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RE: how to find bad blocks
I think the OP just needs enough data to convince Samsung that the drive is bad so he can RMA it. If the drive is at fault the SMART data should do it (especially since the first thing Samsung will do when they get the drive is query the SMART data...) Since the drive is part of a RAID array I don't think you can trust programs such as badblocks or ddrescue to accurately map bad blocks on the drive. Since a logical device like /dev/sda1 would represent more than one physical disk badblocks might be able to tell you that the array is failing or degraded, but mapping particular bad sectors on an individual disk in an array would be a pretty nifty trick. Similarly ddrescue would tell you that it could not recover parts of the partition, but again trying to figure out which disk in an array is at fault might be difficult. Hopefully it's a RAID 5 or similar so no data was actually lost. If either of these tools can report faults to that level I'd love to be corrected -- it would have been useful to me in the past! The other advantage of querying smart data is that you can do that while the disk is online -- no need to boot with a manufacturer diagnostic CD or bring a production array down to copy it with ddrescue or do a desctructive write test with badblocks -w. That is important in the case of live data people are working with. (However if the disk is part of something like a RAID 1 or 5 then the OP can just pull the drive and do whatever tests he or Samsung wants on it while the array rebuilds onto a replacement...) Just my 2c. James -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: how to find bad blocks
Vadkan Jozsef put forth on 2/9/2010 11:44 AM: Besides the badblocks app? We have a samsung hdd, that keeps falling out of raid, but there are no bad blocks on it, according to badblocks prog. This is probably because there are no bad blocks on it. we would like to return it [warranty], but it would be better to find e.g. bad blocks on it..:\ :D If falling out of raid means your hardware PCI/X/e/mobo mounted real RAID card is taking this drive off line, usually this is because of a firmware issue. The firmware on the RAID card doesn't want to play with the firmware on the drive. This most often happens when a drive of dissimilar brand/make/model/size/fw_rev is added into an existing array of identical drives, or a group of identical drives is used but the controller doesn't like the drive firmware rev, period. In either case, good drives will be kicked off line by the controller. I went through a wacky case of this back in the late 1990s with Mylex DAC960 cards kicking Seagate ST118202LC drives off-line once a week (or more). Five DAC960s and 40 identical drives. Those DAC960s just didn't like that ST118202 firmware. These were U2W 80MB/s drives and the DAC960s were limited to UW or 40MB/s. Both Mylex and Seagate tech support said this was not the problem, that is was a firmware bug in the drives unrelated to bus speed. Took a while but we eventually got all the drives replaced. That is the most array rebuilding I've ever done, or probably ever will. To get RMA authorization in this situation usually only requires telling the vendor what RAID controller you're using and what drive configuration. It always helps if you bought all components from the same vendor, and helps even more if you got a verbal or written commitment that the card and drives would work together in the configuration you had planned. If it's a low ball no name vendor that doesn't sell both RAID cards and drives, they may tell you to yourself, that the drive is fine. This is one huge disadvantage of using low end vendors and why corporations usually buy the bulk of their hardware from a single vendor. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
filed a bug report, re: mkdosfs hangs while scanning for bad blocks
On Sat, 07 Nov 2009 17:43 -0800, whollyg...@letterboxes.org wrote:
Anybody know what's going on or can help debug
this at least?
Running squeeze I am having trouble reformatting a
* 64MB memory stick and a
* 160GB 2.5 HD in a USB linked
external enclosure
using mkdosfs -c /dev/sd{ag}1.
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=556141
--
whollyg...@letterboxes.org
--
http://www.fastmail.fm - Faster than the air-speed velocity of an
unladen european swallow
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: mkdosfs hangs while scanning for bad blocks
whollyg...@letterboxes.org wrote:
On Sun, 08 Nov 2009 09:46 +, John Allen john.al...@dublinux.net
wrote:
whollyg...@letterboxes.org wrote:
Anybody know what's going on or can help debug
this at least?
Running squeeze I am having trouble reformatting a
* 64MB memory stick and a
* 160GB 2.5 HD in a USB linked
external enclosure
using mkdosfs -c /dev/sd{ag}1.
I can report the same happens on Lenny with the latest amd64 kernel.
What kind of medium did you try to format,
and how big is it?
2G SD card, it had been reporting read errors in my camera, so I thought
I'd reformat with -c :(
I tried this with a live grml cd and it choked there
as well. No luck getting the drive recognized under
dos. Think I will try making a couple of smaller
partitions and see if that works any better.
Thanks for you comment
will
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: mkdosfs hangs while scanning for bad blocks
On Sun, 08 Nov 2009 09:46 +, John Allen john.al...@dublinux.net
wrote:
whollyg...@letterboxes.org wrote:
Anybody know what's going on or can help debug
this at least?
Running squeeze I am having trouble reformatting a
* 64MB memory stick and a
* 160GB 2.5 HD in a USB linked
external enclosure
using mkdosfs -c /dev/sd{ag}1.
I can report the same happens on Lenny with the latest amd64 kernel.
What kind of medium did you try to format,
and how big is it?
I tried this with a live grml cd and it choked there
as well. No luck getting the drive recognized under
dos. Think I will try making a couple of smaller
partitions and see if that works any better.
Thanks for you comment
will
--
whollyg...@letterboxes.org
--
http://www.fastmail.fm - Send your email first class
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: mkdosfs hangs while scanning for bad blocks
whollyg...@letterboxes.org wrote:
Anybody know what's going on or can help debug
this at least?
Running squeeze I am having trouble reformatting a
* 64MB memory stick and a
* 160GB 2.5 HD in a USB linked
external enclosure
using mkdosfs -c /dev/sd{ag}1.
I can report the same happens on Lenny with the latest amd64 kernel.
In both cases the process hung while checking for
bad blocks. ps shows the process to be in
uninteruptible sleep. man ps says that it is
probably related to IO.
I eventually got the memory stick to finish but
the external HD still hangs (at the same block
count, at least, on 3 of the tries).
kill -KILL doesn't unjam the process. Only unplugging
the drive seems to free things up. If you plugg
it back in right away, it will start counting
off blocks as it checks again and finishes. But, the
filesystem mounts as ext3 because...
mke2fs -c -j /dev/sda1 will work just fine on this drive.
Thanks,
will
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
mkdosfs hangs while scanning for bad blocks
Anybody know what's going on or can help debug
this at least?
Running squeeze I am having trouble reformatting a
* 64MB memory stick and a
* 160GB 2.5 HD in a USB linked
external enclosure
using mkdosfs -c /dev/sd{ag}1.
In both cases the process hung while checking for
bad blocks. ps shows the process to be in
uninteruptible sleep. man ps says that it is
probably related to IO.
I eventually got the memory stick to finish but
the external HD still hangs (at the same block
count, at least, on 3 of the tries).
kill -KILL doesn't unjam the process. Only unplugging
the drive seems to free things up. If you plugg
it back in right away, it will start counting
off blocks as it checks again and finishes. But, the
filesystem mounts as ext3 because...
mke2fs -c -j /dev/sda1 will work just fine on this drive.
Thanks,
will
--
whollyg...@letterboxes.org
--
http://www.fastmail.fm - IMAP accessible web-mail
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
mke2fs checking bad blocks
Hi, I have beening running following command to check an external USB 1 TB disk for more than 15 hours. I am not clear if the right corner of 244190007 is the maxinum blocks it should check or not. If it is, it seems that it has already exceeded the total blocks, but it is still running. What should I do, just quit it? ~$ /sbin/mke2fs -c /dev/sda1 mke2fs 1.40-WIP (14-Nov-2006) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 122109952 inodes, 244190008 blocks 12209500 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=0 7453 block groups 32768 blocks per group, 32768 fragments per group 16384 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 2048, 23887872, 71663616, 78675968, 10240, 214990848 Checking for bad blocks (read-only test):25582272/ 244190007 Thank you. Kind Regards, Jupiter -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: mke2fs checking bad blocks
On 2009-08-09 11:51 +0200, hce wrote: Hi, I have beening running following command to check an external USB 1 TB disk for more than 15 hours. I am not clear if the right corner of 244190007 is the maxinum blocks it should check or not. If it is, it seems that it has already exceeded the total blocks, but it is still running. What should I do, just quit it? ~$ /sbin/mke2fs -c /dev/sda1 mke2fs 1.40-WIP (14-Nov-2006) This is an old version, and it may be that you hit bug #411838¹ or some other problem that has been fixed in the meantime. I would definitely try a newer version on such a big filesystem. Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 122109952 inodes, 244190008 blocks This indicates that the right boundary of 244190007 is at least close. Sven ¹ http://bugs.debian.org/411838 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: mke2fs checking bad blocks
On Sun, Aug 09, 2009 at 19:51 +1000, hce wrote: Hi, I have beening running following command to check an external USB 1 TB disk for more than 15 hours. I am not clear if the right corner of 244190007 is the maxinum blocks it should check or not. If it is, it seems that it has already exceeded the total blocks, but it is still running. What should I do, just quit it? ~$ /sbin/mke2fs -c /dev/sda1 mke2fs 1.40-WIP (14-Nov-2006) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 122109952 inodes, 244190008 blocks 12209500 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=0 7453 block groups 32768 blocks per group, 32768 fragments per group 16384 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 2048, 23887872, 71663616, 78675968, 10240, 214990848 Checking for bad blocks (read-only test):25582272/ 244190007 Assuming bad blocks are checked sequentially it seems you have to be prepared to wait a little longer :) 25582272 / 244190008. = 0.104763795 Kind Regards, Siggy Jupiter Sorry, just can't resist: quod licet bovi non licet jovi :) -- Please don't Cc: me when replying, I might not see either copy. bsb-at-psycho-dot-informationsanarchistik-dot-de or:bsb-at-psycho-dot-i21k-dot-de O ascii ribbon campaign - stop html mail - www.asciiribbon.org -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: mke2fs checking bad blocks
Thanks Sven. Will it be any problem if I quit it by pressing Ctr-c? If I understand it correctly, the mke2fs -c is only check the bad block, not write or format the disk, right? By the way, it has not reached the maximum blocks yet, but it seems it need to run another 3 days to finishe it. I cannot level my machine on so long. Thanks. Jupiter On Sun, Aug 9, 2009 at 8:10 PM, Sven Joachimsvenj...@gmx.de wrote: On 2009-08-09 11:51 +0200, hce wrote: Hi, I have beening running following command to check an external USB 1 TB disk for more than 15 hours. I am not clear if the right corner of 244190007 is the maxinum blocks it should check or not. If it is, it seems that it has already exceeded the total blocks, but it is still running. What should I do, just quit it? ~$ /sbin/mke2fs -c /dev/sda1 mke2fs 1.40-WIP (14-Nov-2006) This is an old version, and it may be that you hit bug #411838¹ or some other problem that has been fixed in the meantime. I would definitely try a newer version on such a big filesystem. Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 122109952 inodes, 244190008 blocks This indicates that the right boundary of 244190007 is at least close. Sven ¹ http://bugs.debian.org/411838 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: mke2fs checking bad blocks
On 2009-08-09 05:25, hce wrote: Thanks Sven. Will it be any problem if I quit it by pressing Ctr-c? If I understand it correctly, the mke2fs -c is only check the bad block, not write or format the disk, right? No problem. -- Scooty Puff, Sr The Doom-Bringer -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: mke2fs checking bad blocks
On 2009-08-09 04:51, hce wrote: Hi, I have beening running following command to check an external USB 1 TB disk for more than 15 hours. I am not clear if the right corner of 244190007 is the maxinum blocks it should check or not. If it is, it seems that it has already exceeded the total blocks, but it is still running. What should I do, just quit it? ~$ /sbin/mke2fs -c /dev/sda1 sda??? Is your boot disk hda? Is it plugged into a USB 1.1 port? Also, I wouldn't be surprised if check bad blocks weren't inordinately slow even on internal disks. mke2fs 1.40-WIP (14-Nov-2006) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 122109952 inodes, 244190008 blocks 12209500 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=0 7453 block groups 32768 blocks per group, 32768 fragments per group 16384 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 2048, 23887872, 71663616, 78675968, 10240, 214990848 Checking for bad blocks (read-only test):25582272/ 244190007 Thank you. Kind Regards, Jupiter -- Scooty Puff, Sr The Doom-Bringer -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: copying files on hd with bad blocks
On Wed, Jun 17, 2009 at 10:03:52AM +0800, Umarzuki Mochlis wrote: I need to copy files from a ntfs formatted hd to a ntfs hd. What tool should i use? Note: I only need to copy files and directories, not making disk image If you have a problem reading from the disk itself, consider starting with a dd-rescue of the disk (or partition) to an image and doing all the work on it. -- Tzafrir Cohen | tzaf...@jabber.org | VIM is http://tzafrir.org.il || a Mutt's tzaf...@cohens.org.il || best ICQ# 16849754 || friend -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: copying files on hd with bad blocks
2009/6/17 Tzafrir Cohen tzaf...@cohens.org.il On Wed, Jun 17, 2009 at 10:03:52AM +0800, Umarzuki Mochlis wrote: I need to copy files from a ntfs formatted hd to a ntfs hd. What tool should i use? Note: I only need to copy files and directories, not making disk image If you have a problem reading from the disk itself, consider starting with a dd-rescue of the disk (or partition) to an image and doing all the work on it. sadly the target and source both are 1 TB. That's the best I can get. -- Tzafrir Cohen | tzaf...@jabber.org | VIM is http://tzafrir.org.il || a Mutt's tzaf...@cohens.org.il || best ICQ# 16849754 || friend -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org -- Regards, Umarzuki Mochlis http://gameornot.net
copying files on hd with bad blocks
I need to copy files from a ntfs formatted hd to a ntfs hd. What tool should i use? Note: I only need to copy files and directories, not making disk image TIA -- Regards, Umarzuki Mochlis http://gameornot.net
Re: copying files on hd with bad blocks
On Wed, Jun 17, 2009 at 10:03:52AM +0800, Umarzuki Mochlis wrote: I need to copy files from a ntfs formatted hd to a ntfs hd. What tool should i use? Note: I only need to copy files and directories, not making disk image Hi, You can use ntfs-3g. First, install it by running aptitude install ntfs-3g as root (or with sudo). Then you can use the ntfs-3g mount type or command. $ man ntfs-3g will give you more info once the package is installed. Cheers, -- Eric Gerlach, Network Administrator Federation of Students University of Waterloo p: (519) 888-4567 x36329 e: egerl...@feds.uwaterloo.ca -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bad blocks and powernowd
2009/1/16 Johannes Wiedersich johan...@physik.blm.tu-muenchen.de: Davide Mancusi wrote: The hard disk of my 4-year-old laptop is starting to fail. I ran fsck.ext3 -c on my root partition yesterday and a few blocks were marked as damaged. The blocks contained some XFCE4 theme files, so I thought that reinstalling the relevant package should be enough. Now, however, the machine hangs every time I start powernowd. Kernel emergency key presses (Alt+SysRq+?) don't work and the usual log files don't contain any relevant information. I have tried uninstalling and reinstalling the powernowd package, but it didn't help; note also that fsck did not signal any damaged files belonging to powernowd. Can anyone help me sort this out? Could it be that fsck -c did not mark some blocks as damaged because I ran it with the root partition mounted read-only (as opposed to unmounted)? If your disk is dying this could mean about anything. Try smartctl from smartmontools package. What does it report about the health status of your disk (after some testing)? Try e2fsck again to see, if it detects 'new' errors on your file system. I hope you have good back ups. You could try diff -r against your backup (mounted ro). However, if your disk is damaged and loads and runs garbled kernel stuff, you risk hosing your backup. Therefore it might be safer to investigate by booting a rescue system from CD or usb-disk. YMMV. Thanks for your response, Johannes. Now I'm confused. I installed smartmontools, I ran # smartctl -t long /dev/hda and I detected two bad sectors. I followed the HOWTO at [1] and reallocated the first one. (I had no idea one could recover bad sectors. I thought they were as good as gone.) Then I ran the test again to get the LBA address of the second bad block. Surprise, surprise, the test completed without problems. I also tried booting off a live CD and running e2fsck -c -c on all ext2/3 partitions. No bad blocks were detected, but one of the inode tables was heavily modified. However, even though no files related to powernowd were touched, powernowd now works again. From the live CD I ran again # smartctl -t long /dev/hda [waited one hour] # smartctl -l selftest /dev/hda smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF READ SMART DATA SECTION === SMART Self-test log structure revision number 1 Num Test_DescriptionStatus Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offlineCompleted without error 00% 6264 - # 2 Extended offlineCompleted without error 00% 6262 - # 3 Extended offlineCompleted without error 00% 6259 - # 4 Short offline Completed without error 00% 6258 - # 5 Extended offlineCompleted: read failure 30% 6257 95245863 You can see that the last test completed without errors. However: # smartctl -A /dev/hda smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 062Pre-fail Always - 0 2 Throughput_Performance 0x0005 105 105 040Pre-fail Offline - 5874 3 Spin_Up_Time0x0007 200 200 033Pre-fail Always - 1 4 Start_Stop_Count0x0012 096 096 000Old_age Always - 6796 5 Reallocated_Sector_Ct 0x0033 100 100 005Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 120 120 040Pre-fail Offline - 36 9 Power_On_Hours 0x0012 086 086 000Old_age Always - 6268 10 Spin_Retry_Count0x0013 100 100 060Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000Old_age Always - 1167 191 G-Sense_Error_Rate 0x000a 100 100 000Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000Old_age Always - 65 193 Load_Cycle_Count0x0012 065 065 000Old_age Always - 359932 194 Temperature_Celsius 0x0002 130 130 000Old_age Always - 42 (Lifetime Min/Max 11/58) 196 Reallocated_Event_Count 0x0032 100 100 000Old_age Always - 9 197 Current_Pending_Sector 0x0022 100 100 000Old_age Always - 1 198 Offline_Uncorrectable 0x0008 100 100 000Old_age Offline - 0 199 UDMA_CRC_Error_Count0x000a 200 200 000Old_age Always
Bad blocks and powernowd
Hello everyone, The hard disk of my 4-year-old laptop is starting to fail. I ran fsck.ext3 -c on my root partition yesterday and a few blocks were marked as damaged. The blocks contained some XFCE4 theme files, so I thought that reinstalling the relevant package should be enough. Now, however, the machine hangs every time I start powernowd. Kernel emergency key presses (Alt+SysRq+?) don't work and the usual log files don't contain any relevant information. I have tried uninstalling and reinstalling the powernowd package, but it didn't help; note also that fsck did not signal any damaged files belonging to powernowd. Can anyone help me sort this out? Could it be that fsck -c did not mark some blocks as damaged because I ran it with the root partition mounted read-only (as opposed to unmounted)? Thanks in advance for the attention! Davide -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bad blocks and powernowd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Davide Mancusi wrote: The hard disk of my 4-year-old laptop is starting to fail. I ran fsck.ext3 -c on my root partition yesterday and a few blocks were marked as damaged. The blocks contained some XFCE4 theme files, so I thought that reinstalling the relevant package should be enough. Now, however, the machine hangs every time I start powernowd. Kernel emergency key presses (Alt+SysRq+?) don't work and the usual log files don't contain any relevant information. I have tried uninstalling and reinstalling the powernowd package, but it didn't help; note also that fsck did not signal any damaged files belonging to powernowd. Can anyone help me sort this out? Could it be that fsck -c did not mark some blocks as damaged because I ran it with the root partition mounted read-only (as opposed to unmounted)? If your disk is dying this could mean about anything. Try smartctl from smartmontools package. What does it report about the health status of your disk (after some testing)? Try e2fsck again to see, if it detects 'new' errors on your file system. I hope you have good back ups. You could try diff -r against your backup (mounted ro). However, if your disk is damaged and loads and runs garbled kernel stuff, you risk hosing your backup. Therefore it might be safer to investigate by booting a rescue system from CD or usb-disk. YMMV. Take care, good luck, Johannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAklwis8ACgkQC1NzPRl9qEUSBACfdVFrcPhfWly+MNdjKWaSnGmN w/kAnRDP29lgIgsQmZ92M4HgPLgDpLDa =sMal -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
e2fsck -c to check for bad blocks
I gather one can use the e2fsck with -c option to have it call /sbin/badblocks to report bad blocks on an unmounted partition. 1. Although the -c option causes fsck to use badblocks to identify any bad blocks present, does e2fsck then proceed to use this information to fix corruption as usual? That is, how does # e2fsck -cy /dev/sda1 differ from simply: # e2fsck -y /dev/sda1 2. If badblocks is non-destructive, why does the targeted filesystem have to be unmounted? 3. While e2fsck is run on an unmounted file system, the man page says, If this [-c] option is specified twice, then the bad block scan will be done using a non-destructive read-write test. Does this specified twice simply mean -cc? If the test is non-destructive, can it be run on a mounted filesystem? I assume not, but wanted to be sure. 4. Both badblocks and e2fsck -c can identify bad blocks as part of a check of hard disk viability. Is the difference only that while badblocks just reports bad blocks, e2fsck -c actually goes ahead and tries to fix them? -- Haines Brown, KB1GRM -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: e2fsck -c to check for bad blocks
On Wed, 13 Feb 2008 11:12:52 -0500 Haines Brown [EMAIL PROTECTED] wrote: I gather one can use the e2fsck with -c option to have it call /sbin/badblocks to report bad blocks on an unmounted partition. This option causes e2fsck to use badblocks(8) program to do a read-only scan of the device in order to find any bad blocks. If any bad blocks are found, they are added to the bad block inode to prevent them from being allocated to a file or directory. If this option is specified twice, then the bad block scan will be done using a non-destructive read-write test. 1. Although the -c option causes fsck to use badblocks to identify any bad blocks present, does e2fsck then proceed to use this information to fix corruption as usual? That is, how does # e2fsck -cy /dev/sda1 differ from simply: # e2fsck -y /dev/sda1 Yes, it does fix it. they are added to the bad block inode 2. If badblocks is non-destructive, why does the targeted filesystem have to be unmounted? Does it have to be? What does -f say? fsck always complains if the fs is mounted. Note that in general it is not safe to run e2fsck on mounted filesystems. The only exception is if the -n option is specified, and -c, -l, or -L options are not specified. However, even if it is safe to do so, the results printed by e2fsck are not valid if the filesystem is mounted. If e2fsck asks whether or not you should check a filesystem which is mounted, the only correct answer is ‘‘no’’. Only experts who really know what they are doing should consider answering this question in any other way. Badblocks may be non-destructive, but adding the found blocks to the inode may be bad. You don't know what fsck will do other than running badblocks. 3. While e2fsck is run on an unmounted file system, the man page says, If this [-c] option is specified twice, then the bad block scan will be done using a non-destructive read-write test. Does this specified twice simply mean -cc? If the test is non-destructive, can it be run on a mounted filesystem? I assume not, but wanted to be sure. correct. 4. Both badblocks and e2fsck -c can identify bad blocks as part of a check of hard disk viability. Is the difference only that while badblocks just reports bad blocks, e2fsck -c actually goes ahead and tries to fix them? correct. -- Haines Brown, KB1GRM pgpXcoujbkgBg.pgp Description: PGP signature
Re: e2fsck -c to check for bad blocks
Christopher - thanks for the clarications. -- Haines Brown, KB1GRM -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Duplicate/Bad blocks
Hallo nochmal! Ich hab alles durchlaufen lassen aber hat nix geholfen! Ich denke auch fast, dass das Problem am Filesystem-Treiber von meinem WinXP liegt ... also dass ich zur Zeit des ausschaltens im win war und dann dieser fs-driver den fehler verursacht hat (die partition wäre nämlich ext3)! Naja, egal, jedenfalls bin ich grad am sichern: home + etc = fertig meine daten = probleme :D Es sind nämlich diverse Dateien auch mit Umlauten/Sonderzeichen gewesen und die wurden unter Linux scheinbar irgendwie umbenannt und enthalten jetzt diverse sonderzeichen, die Windows (unter dem ich grad sichere) nicht lesen kann! Ich bräuchte jetzt ein Tool (für Linux, weil windows die dateien ja nicht verarbeiten kann), das die betroffenen dateien findet und umbenennt! Kann mir jmd sagen, wo ich so ein tool finde bzw. wie ich das mit einem bash-script selbst schaffen würde? mfg, peter Zitat von Christoph Conrad [EMAIL PROTECTED]: Hallo Peter, Und das sehr häufig! Ich hab es noch nie fertig laufen lassen, da er nach einer weile scheinbar stehen bleibt. Lass es mal einige Stunden laufen. Wenn sich dann nichts mehr regt, würde ich nach Backup deines Homeverzeichnisses und /etc neu installieren, und gleich z.B. ext3 verwenden. Da habe ich auch schon den Stecker gezogen, das macht nix. Das eben gezogene Backup kann natürlich fehlerhafte Dateien beeinhalten. Freundliche Grüße, Christoph -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl) -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Duplicate/Bad blocks
Hi! Am Thu, 06 Jul 2006 15:20:14 +0200 schrieb Bogensperger [EMAIL PROTECTED]: Es sind nämlich diverse Dateien auch mit Umlauten/Sonderzeichen gewesen und die wurden unter Linux scheinbar irgendwie umbenannt und enthalten jetzt diverse sonderzeichen, die Windows (unter dem ich grad sichere) nicht lesen kann! Ich bräuchte jetzt ein Tool (für Linux, weil windows die dateien ja nicht verarbeiten kann), das die betroffenen dateien findet und umbenennt! Hmmm, ich bin gerade verwirrt. Warum nimmst Du nicht einfach für die Sicherung wieder das gleiche Dateisystem? Worauf sicherst Du denn, auf eine zweite Platte? Ich würde einfach mit einer Knoppix-CD booten und die Dateien von da aus sichern. Da hast Du dann ja auch die entsprechenden Tools. Ich denke auch fast, dass das Problem am Filesystem-Treiber von meinem WinXP liegt ... also dass ich zur Zeit des ausschaltens im win war und dann dieser fs-driver den fehler verursacht hat (die partition wäre nämlich ext3)! Den Teil hier habe ich übrigens auch nicht verstanden. Hat es Dir die Partitionstabelle verhauen oder wie? In dem Fall könnte gpart helfen. LG, Ace -- () ASCII Ribbon Campaign - against HTML mail /\- against Microsoft attachments http://www.efn.no/html-bad.html http://www.goldmark.org/netrants/no-word/attach.html signature.asc Description: PGP signature
Duplicate/Bad blocks
Hallo Liste! Ich hab etwas ganz böses gemacht :( Vor einigen Tagen habe ich einfach die Steckerleiste abgeschalten anstatt den PC runterzufahen. Ich hatte einfach keine Zeit (musste ins KH)! Tja, das ergebnis sehe ich jetzt: Erstmal meldet sich der fsck, da er ein kaputtes filesystem gefunden hat! Nach der Überprüfung kommt: Duplicate/bad block(s) in inode: XYZ Und das sehr häufig! Ich hab es noch nie fertig laufen lassen, da er nach einer weile scheinbar stehen bleibt. Wie kann ich dieses Problem lösen? Merci, Peter -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Duplicate/Bad blocks
Hallo Peter, Und das sehr häufig! Ich hab es noch nie fertig laufen lassen, da er nach einer weile scheinbar stehen bleibt. Lass es mal einige Stunden laufen. Wenn sich dann nichts mehr regt, würde ich nach Backup deines Homeverzeichnisses und /etc neu installieren, und gleich z.B. ext3 verwenden. Da habe ich auch schon den Stecker gezogen, das macht nix. Das eben gezogene Backup kann natürlich fehlerhafte Dateien beeinhalten. Freundliche Grüße, Christoph -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
ext3 bad blocks error
Hi, my power supply switched off suddenly last week while I was doing some update of system files last week. Since then, I am not able to boot the 2.6.13.4 kernel (with udev support) anymore, more specifically, my /home parition cannot be mounted and booting stops with the message: fsck.ext3: No such file or directory while trying to open /dev/hda6: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is not valid and it really contains an ext2 filesystem, then the superblock is corrupt, and you might try running e2fsck with an alternate superblock. fsck failed. Please repair manually. No I have tried fsck -c /dev/hda6 but this device cannot be found, although it is correctly in the /proc/partitions: major minor #blocks name 3 0 39082680 hda 3 16835626 hda1 3 2 1 hda2 3 5 771088 hda5 3 6 31471303 hda6 After doing a manual mknod /dev/hda6 b 3 6 I can run fsck, but the report does not show bad block or missing inodes. Neither does the report for the /root partition. Mounting the /home from the linux 2.4.24.x kernel (with static devfs) works flawless, as does the boot from the live cd. Continuing booting with 2.6.13.4 times out after a while with some error messages on init.d/rcS script not correct. Does anyone see what is happening here ? Or, do I need to reformat my whole harddisk ? Thank you very much for your help. Patrick ___ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Verificação por bad blocks no momen to da instalação do debian-br-cdd
Olá pessoal. Já postei aqui alguns problemas que tive na instalação do debian-br-cdd e também com a imagem para testes do debian-instaler. Bom, acho que a causa dos problemas é porque deve ter badblocks no meu hd (samsung). Mas diferente do woody, esse novo instalador não me dá a opção de buscar bad blocks no hd. Existe algum modo de fazer isto antes de instalar o sistema? valeu e abraços. -- jupercio juliano DebianUser www.debian-br.org Jabber: jupercio at jabber.org
Re: Is it safe to use disk with many bad blocks?
on Sat, Jun 26, 2004 at 08:02:17PM -0400, Ben Russo ([EMAIL PROTECTED]) wrote: I have an 80GB hard disk. badblocks shows that it has about 78M blocks. The first 50 million or so can be checked (write patterns) for many days with no problems. Beyond that I start to get errors. Does anyone have any experience with creating a partition in the good part of the disk and just ignoring the rest? Late add: check to see if your HD is SMART-enabled. Install the smartmontools package and see if the badblocks allowance is within allowed ranges, and/or if the SMART tests pass or fail. Most disks from the past 3-4 years *will* be SMART capable. Peace. -- Karsten M. Self [EMAIL PROTECTED]http://kmself.home.netcom.com/ What Part of Gestalt don't you understand? Unless you are very rich and very eccentric, you will not enjoy the luxury of having a computer in your own home. - Ed Yourdon, _Techniques of Program Structure and Design_, 1975 signature.asc Description: Digital signature
Is it safe to use disk with many bad blocks?
I have an 80GB hard disk. badblocks shows that it has about 78M blocks. The first 50 million or so can be checked (write patterns) for many days with no problems. Beyond that I start to get errors. Does anyone have any experience with creating a partition in the good part of the disk and just ignoring the rest? -Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is it safe to use disk with many bad blocks?
Ben Russo wrote: I have an 80GB hard disk. badblocks shows that it has about 78M blocks. The first 50 million or so can be checked (write patterns) for many days with no problems. Beyond that I start to get errors. Does anyone have any experience with creating a partition in the good part of the disk and just ignoring the rest? _I_ wouldn't use it. If it's under waranty, get it replaced. Before this, check with your drive's manufacturer's website. Some have diagnostics you can run. IBM's used to be somewhere under www.ibm.com/harddrive - I expect it would take you to Hitachi now. I think the latest version of IBM's DFT can test other vendors drives too. IBM's is especially friendly to Linux users as it comes as a floppy disk image which contains PCDOS2000. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
very messed up reiserfs with bad blocks
Hi, I have a problem with a reiserfs partition. Some days ago the drive reported bad blocks, so I ran the badblocks program tried to fix the filesystem with the badblocksoutput. Assuming I fixed the badblock list with 'reiserfsck --badblocks' I tried to access some (reported broken) files on that partition. This gave some I/O errors, so I thought I had to rebuild the tree (reiserfsck --badblocks --rebuild-tree). This failed, and the filesystem became unmountable (mount fails with 'mount: Not a directory'). I ran another badblock scan, and the number of badblocks grew substantially (from 11 in the first run to 177 in the second). --rebuild-tree failed again and again. Now the weird thing occured: running a third badblock scan didn't increase the amount of badblocks (as I should expect, since the badblock program runs on a lower level than the filesystem). It gave me 56 badblocks. Now the following questions raised: - what causes the amount of bad blocks to fluctuate? - how can I access the filesystem again? I know the drive is bad, so I am only into copying the contents off it as soon as possible. I have the idea the file allocation table is corrupted. Now --rebuild-tree won't help me, so I was hoping there is a backup of this FAT on the drive somewhere. I couldn't find it, so how does one deal with this thing under reiser? Thanks a lot in advance! Sebastiaan -- English written by Dutch people is easily recognized by the improper use of 'In principle ...' The software box said 'Requires Windows 95 or better', so I installed Linux. Als Pacman in de jaren '80 de kinderen zo had be?nvloed zouden nu veel jongeren rondrennen in donkere zalen terwijl ze pillen eten en luisteren naar monotone electronische muziek. (Kristian Wilson, Nintendo, 1989) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[OT] CF Karte mit Bad Blocks
Moin, ich hab eine 192 MB grosse CF Karte die Bad Blocks enthält. Ich hatte sie nun mit mkfs.vfat -c /dev/hdc1 versucht zu formatieren, das Problem besteht jedoch fort. Nun bin ich auf der Suche nach dem Format der Datei, die man mit der Option '-I file' angeben soll um bestimmte Blöcke auszuschliessen. Danke -- |Michael Renner E-mail: [EMAIL PROTECTED] | |D-72072 Tuebingen Germany| |Germany Don't drink as root! ESC:wq
Re: [OT] CF Karte mit Bad Blocks
Am 2004-04-22 11:11:47, schrieb Michael Renner: Moin, ich hab eine 192 MB grosse CF Karte die Bad Blocks enthält. Ich hatte sie nun mit mkfs.vfat -c /dev/hdc1 versucht zu formatieren, das Problem besteht jedoch fort. Nun bin ich auf der Suche nach dem Format der Datei, die man mit der Option '-I file' angeben soll um bestimmte Blöcke auszuschliessen. badblocks -o output_file /dev/hdc1 mkfs.vfat -l output_file /dev/hdc1 Danke Greetings Michelle -- Registered Linux-User #280138 with the Linux Counter, http://counter.li.org/ signature.asc Description: Digital signature
Serial ATA fun (bad blocks)
this is on debian unstable but not strictly debian related. kernel 2.4.21-ac4 Intel D865PERL motherboard (with SATA interface) Maxtor 260GB SATA HD after compiling the ac kernel the SATA disk was recognized and I could create filesystem and mount the disk. However soon after starting to write the data I got lots of errors. So I ran badblocks: jojda:/home/erik# badblocks -s -v -w -c 64 -o badblocks.out /dev/sda Checking for bad blocks in read-write mode From block 0 to 245117376 Testing with pattern 0xaa: done Reading and comparing: done Testing with pattern 0x55: done Reading and comparing: done Testing with pattern 0xff: done Reading and comparing: done Testing with pattern 0x00: done Reading and comparing: done Pass completed, 110899617 bad blocks found. That looks like half the disk is unreadable (from 134217772 to 245117375, even though I didn't check whether every single block in that range is bad). Could it be a problem of new SATA driver? Or some other problem related to the size of the disk? I googled SATA, searched kernel mailing list archives, read (pretty much obsolete) Large disk HOWTO... found nothing (it could be bad disk, I am going to boot the other os and see if the CD that came with disk helps...) TIA erik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: OT: IDE/Bad Blocks: Call for mental assistance
I'd appreciate if you would not CC me, as I request in the X-Followup-To header and the signature of each email. It could be a bad controller on the motherboard and it sounds like it. You may be damaging hard drives with a bad mootherboard. Right, but using five different machines? My disks seem to last for years, unless they are in drive pulling cases and overheat. I am currently investigating overheating. Does badblocks write the list of badblocks to the hard disk so that it remembers badblocks from run to run and when you moved the hard drive? No. In my experience, one bad block means that the drive is doomed to accumulate more. I used to design disk drive electronics for a living at Quantum. Quamtum is the only drive that hasn't borked on me yet. Thanks. -- Please do not CC me when replying to lists; I read them! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than fixing a system Invalid PGP subkeys? Use subkeys.pgp.net as keyserver! pgp0.pgp Description: PGP signature
Re: OT: IDE/Bad Blocks: Call for mental assistance
On Sun, 13 Jul 2003, martin f krafft wrote: Folks, Over the past year, I have replaced something around 20 IDE Harddrives in 5 different computers running Debian because of drive faults. I know about IDE and that it's consumer quality and no more, but it can't be the case that the failure rate is that high. The drives are mostly made by IBM/Hitachi, and they run 24/7, as the machines in question are either routers, firewalls, or servers. throw those ( deskstar?? ) drives away if it's made in hungry or thailand then ran `badblocks -svw` on the disk. And usually, I'd see a number of bad blocks, usually in excess of 100. running badblocks does NOT prove that the disk is bad ... - i didn't look at the code, but if badblock bypasses the normal ide interface/system calls, than it's result is worthless if it writes directly to the disk interface ( it should tell you the same list of badblocks the manufacturer ( already coded into their disk controller's eproms - if badblock acts like anyother user app, than there should be zero badblocks - ibm and every disk manufacturer have their own disk testor to test their drives ( mostly windoze based ) c ya alvin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: OT: IDE/Bad Blocks: Call for mental assistance
On Monday 14 July 2003 10:48, Pigeon wrote: I've been mad for years, absolutely f**king years, I've been over the edge for yonks. :-) All Pink Floyd fans are anyway ;) cr ... comfortably numb... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: OT: IDE/Bad Blocks: Call for mental assistance
also sprach cr [EMAIL PROTECTED] [2003.07.14.1057 +0200]: I've been mad for years, absolutely f**king years, I've been over the edge for yonks. :-) All Pink Floyd fans are anyway ;) I beg to differ. We are normal, the rest is mad! Aside, I believe that my reference to Uncle Freddie was more appropriate to my state, as I do still try to classify as mentally stable unless I am dealing with HONKIN' HARDDRIVES. -- Please do not CC me when replying to lists; I read them! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than fixing a system Invalid PGP subkeys? Use subkeys.pgp.net as keyserver! pgp0.pgp Description: PGP signature
Re: OT: IDE/Bad Blocks: Call for mental assistance
martin f krafft wrote: problems), got the machine back into a running state, then ran `badblocks -svw` on the disk. And usually, I'd see a number of bad blocks, usually in excess of 100. Modern IDE and SCSI drives fix the bad blocks using the on chip microprocessor and give you a prefect drive. There maybe some way to turn this off, but in general you should never see bad blocks. The other day, I received a replacement drive from Hitachi, plugged it into a test machine, ran badblocks and verified that there were no badblocks. I then put the machine into a firewall, sync'd the data (ext3 filesystems) and was ready to let the computers be and head off to the lake... when the new firewall kept reporting bad reloc headers in libraries, APT would stop working, there would be random single-letter flips in /var/lib/dpkg/available (e.g. swig's Version field would be labelled Verrion), and the system kept reporting segfaults. I consequently plugged the drive into another test machine and ran badblocks -- and it found more than 2000 -- on a drive that had non the day before. It could be a bad controller on the motherboard and it sounds like it. You may be damaging hard drives with a bad mootherboard. My understanding was that EIDE does automatic bad sector remapping, and if badblocks actually finds a bad block, then the drive is declared dead. Is this not the case? Either a bad drive or bad cable or bad motherboard. And when I look around, there are thousands of consumer machines that run day-in-day-out without problems. My disks seem to last for years, unless they are in drive pulling cases and overheat. I don't think it's my IDE controller, since there are 5 different machines involved, and the chance that all IDE controllers report bad blocks where there aren't any, but otherwise function fine with respect to detecting the drives (and not reporting the dreaded dma:intr errors). Does badblocks write the list of badblocks to the hard disk so that it remembers badblocks from run to run and when you moved the hard drive? I used to design disk drive electronics for a living at Quantum. ___ Join Excite! - http://www.excite.com The most personalized portal on the Web! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
OT: IDE/Bad Blocks: Call for mental assistance
Folks, Over the past year, I have replaced something around 20 IDE Harddrives in 5 different computers running Debian because of drive faults. I know about IDE and that it's consumer quality and no more, but it can't be the case that the failure rate is that high. The drives are mostly made by IBM/Hitachi, and they run 24/7, as the machines in question are either routers, firewalls, or servers. Replacing a drive would be a result of symptoms, such as frequent segmentation faults, corrupt files, and zombie processes. In all cases, I replaced the drive, transferred the data (mostly without problems), got the machine back into a running state, then ran `badblocks -svw` on the disk. And usually, I'd see a number of bad blocks, usually in excess of 100. The other day, I received a replacement drive from Hitachi, plugged it into a test machine, ran badblocks and verified that there were no badblocks. I then put the machine into a firewall, sync'd the data (ext3 filesystems) and was ready to let the computers be and head off to the lake... when the new firewall kept reporting bad reloc headers in libraries, APT would stop working, there would be random single-letter flips in /var/lib/dpkg/available (e.g. swig's Version field would be labelled Verrion), and the system kept reporting segfaults. I consequently plugged the drive into another test machine and ran badblocks -- and it found more than 2000 -- on a drive that had non the day before. Just now, I got another replacement from Hitachi (this time it wasn't a serviceable used part, but a new drive), and out of the box, it featured 250 bad blocks. My vendor says that bad blocks are normal, and that I should be running the IBM drive fitness test on the drives to verify their functionality. Moreover, he says that there are tools to remap bad blocks. My understanding was that EIDE does automatic bad sector remapping, and if badblocks actually finds a bad block, then the drive is declared dead. Is this not the case? The reason I am posting this is because I need mental support. I'm going slightly mad. I seem to be unable to buy non-bad IDE drives, be they IBM, Maxtor, or Quantum. Thus I spend excessive time on replacing drives and keeping systems up by brute-force. And when I look around, there are thousands of consumer machines that run day-in-day-out without problems. It may well be that Windoze has better error handling when the harddrive's reliability degrades (I don't want to say this is a good thing). It may be that IDE hates me. I don't think it's my IDE controller, since there are 5 different machines involved, and the chance that all IDE controllers report bad blocks where there aren't any, but otherwise function fine with respect to detecting the drives (and not reporting the dreaded dma:intr errors). So I call to you and would like to know a couple of things: - does anyone else experience this? - does anyone know why this is happening? - is it true that bad blocks are normal and can be handled properly? - why is this happening to me? - can bad blocks arise from static discharge or impurities? when i replace disks, I usually put the new one into the case loosely and leave the cover open. The disk is not subjected to any shocks or the like, it's sitting still as a rock, it's just not affixed. I will probably never buy IDE again. But before I bash companies like Hitachi for crap quality control, I would like to make sure that I am not the one screwing up. Any comments? -- Please do not CC me when replying to lists; I read them! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than fixing a system Invalid PGP subkeys? Use subkeys.pgp.net as keyserver! pgp0.pgp Description: PGP signature
Re: OT: IDE/Bad Blocks: Call for mental assistance
What is weird is that S.M.A.R.T. reports no errors on most drives. I use the smartmontools, and even long offline tests don't produce any error information. -- Please do not CC me when replying to lists; I read them! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than fixing a system Invalid PGP subkeys? Use subkeys.pgp.net as keyserver! pgp0.pgp Description: PGP signature
Re: OT: IDE/Bad Blocks: Call for mental assistance
On Sun, 2003-07-13 at 06:51, martin f krafft wrote: Folks, Over the past year, I have replaced something around 20 IDE Harddrives in 5 different computers running Debian because of drive faults. I know about IDE and that it's consumer quality and no more, but it can't be the case that the failure rate is that high. I've been using IDE drives almost exclusively for over a decade on all of my machines with no problems. This includes 3 servers which were up for 12+ months at a time. I also ran a single server using a SCSI drive a couple of years ago. The SCSI drive is that only one that's ever died in a server box. I have replaced 4 IBM drives in 3 years due to hardware faults cropping up after a year or so, but the majority of the time the drive was in a very dirty, very poorly ventilated machine. --snip-- The other day, I received a replacement drive from Hitachi, plugged it into a test machine, ran badblocks and verified that there were no badblocks. I then put the machine into a firewall, sync'd the data (ext3 filesystems) and was ready to let the computers be and head off to the lake... when the new firewall kept reporting bad reloc headers in libraries, APT would stop working, there would be random single-letter flips in /var/lib/dpkg/available (e.g. swig's Version field would be labelled Verrion), and the system kept reporting segfaults. I consequently plugged the drive into another test machine and ran badblocks -- and it found more than 2000 -- on a drive that had non the day before. This is definitely a Bad Thing (tm). :) Getting 10 or 100 bad blocks might not be that big of a concern (though having it happen on the same day would concern me), but 2000 is quite serious. Just now, I got another replacement from Hitachi (this time it wasn't a serviceable used part, but a new drive), and out of the box, it featured 250 bad blocks. My vendor says that bad blocks are normal, and that I should be running the IBM drive fitness test on the drives to verify their functionality. Moreover, he says that there are tools to remap bad blocks. My understanding was that EIDE does automatic bad sector remapping, and if badblocks actually finds a bad block, then the drive is declared dead. Is this not the case? Some drives can, in fact do bad sector remapping on the fly. However, manually finding bad blocks on a drive is no real cause for concern. When a bad sector is found, it should be marked as such and the FS should not use it afterwards. --snip-- So I call to you and would like to know a couple of things: - does anyone else experience this? - does anyone know why this is happening? - is it true that bad blocks are normal and can be handled properly? - why is this happening to me? Lunar phases, astronomic alignment, a discontented former associate turned witch doctor, a novice voodoo practitioner practicing on HD dolls instead of human ones, or maybe sunspots. Why do any bad things happen to any good people? :) - can bad blocks arise from static discharge or impurities? when i replace disks, I usually put the new one into the case loosely and leave the cover open. The disk is not subjected to any shocks or the like, it's sitting still as a rock, it's just not affixed. Bad blocks can occur due to static discharge and/or impurities, however what I'd be looking at is not affixing the drive to the case. Elementary physics tells us that any vibrations produced by the drive will primarily be reflected back at it rather than dissipated throughout the computer chassis. I am not about to cast the proverbial first stone, however, since I have done the same thing at times. However, in my experience, I've only done it with drives that were dying anyway, and they always seemed to have an accelerated rate of death from that point on. Again, I can't state this as absolute truth, but just in my own personal experience. The other thing that I would be looking at is possibly your motherboard or (if you are using one) PCI IDE controller. You could conceivably be running a system that is through some combination of hardware and software chewing up your HDs. IDE drives can be a great alternative for companies looking to save money. I have a friend who's employer recently purchased 8 consumer-grade PC's to replace 8 aging Sun servers, saving somewhere around $10,000 (US) per machine. They then put in huge RAID-5 arrays and went to work, with no problems. p.s. As a side note, I've been using IBM drives exclusively for about 2 years now, and for the last year or so I've been running ReiserFS on all of them. I don't know if this is still the case, but I know that at one point ReiserFS would choke upon encountering a bad sector. To this day, I have yet to have a single problem. -- Alex Malinovich Support Free Software, delete your Windows partition TODAY! Encrypted mail preferred. You can get my public key from any of the pgp.net keyservers. Key ID
Re: OT: IDE/Bad Blocks: Call for mental assistance
On Sun, 2003-07-13 at 13:18, martin f krafft wrote: What is weird is that S.M.A.R.T. reports no errors on most drives. I use the smartmontools, and even long offline tests don't produce any error information. Martin, Try checking the drives on yet another machine; How old are these machines ? Might it be a motherboard fault as Alex points out. Also, it might be worth installing windows on a small partition and running scandisk surface scan to see if that picks up the faults as well. I have a few machines running IDE without any problems yet. However, the only hdd that ever died on me was an IBM. 20 hdd sounds like a lot - how many machines are you running ? It might be worth getting a new machine to see they handle the hdds better. Also, it might be the supplier, try getting drives from another supplier. Just some thoughts, Shri -- Shri Shrikumar U R Byte Solutions Tel: 0845 644 4745 I.T. Consultant Edinburgh, Scotland Mob: 0773 980 3499 Web: www.urbyte.com Email: [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
Re: OT: IDE/Bad Blocks: Call for mental assistance
On Sun, Jul 13, 2003 at 01:51:23PM +0200, martin f krafft wrote: Folks, Over the past year, I have replaced something around 20 IDE Harddrives in 5 different computers running Debian because of drive faults. I know about IDE and that it's consumer quality and no more, but it can't be the case that the failure rate is that high. The drives are mostly made by IBM/Hitachi, and they run 24/7, as the machines in question are either routers, firewalls, or servers. Replacing a drive would be a result of symptoms, such as frequent segmentation faults, corrupt files, and zombie processes. In all cases, I replaced the drive, transferred the data (mostly without problems), got the machine back into a running state, then ran `badblocks -svw` on the disk. And usually, I'd see a number of bad blocks, usually in excess of 100. The other day, I received a replacement drive from Hitachi, plugged it into a test machine, ran badblocks and verified that there were no badblocks. I then put the machine into a firewall, sync'd the data (ext3 filesystems) and was ready to let the computers be and head off to the lake... when the new firewall kept reporting bad reloc headers in libraries, APT would stop working, there would be random single-letter flips in /var/lib/dpkg/available (e.g. swig's Version field would be labelled Verrion), and the system kept reporting segfaults. I consequently plugged the drive into another test machine and ran badblocks -- and it found more than 2000 -- on a drive that had non the day before. Just now, I got another replacement from Hitachi (this time it wasn't a serviceable used part, but a new drive), and out of the box, it featured 250 bad blocks. My vendor says that bad blocks are normal, and that I should be running the IBM drive fitness test on the drives to verify their functionality. Moreover, he says that there are tools to remap bad blocks. All hard drives have a certain number of defects when new, due to the difficulty of making the platters absolutely perfect. The location of these defects is stored in a table on the drive, and the drive then doesn't use those areas. This is totally transparent, and there's no way badblocks should know about these defects. (Some drives even have a dump of this defect list printed on the label, although not very often these days.) For your vendor to be telling you this as an explanation for what you're experiencing suggests to me that either he doesn't know very much about what he's selling or that he's pulling your plonker. My understanding was that EIDE does automatic bad sector remapping, and if badblocks actually finds a bad block, then the drive is declared dead. Is this not the case? SCSI does this. In addition to the manufacturer's defect list referred to above, SCSI drives have a separate grown defect list used for automatic bad sector remapping. It's possible to dump the contents of this list eg. with scsiinfo, and when the number of grown defects starts increasing you get a chance to replace the drive before the table fills up. I could be wrong, but I don't think EIDE does this. The reason I am posting this is because I need mental support. I'm going slightly mad. I've been mad for years, absolutely f**king years, I've been over the edge for yonks. :-) I seem to be unable to buy non-bad IDE drives, be they IBM, Maxtor, or Quantum. Thus I spend excessive time on replacing drives and keeping systems up by brute-force. And when I look around, there are thousands of consumer machines that run day-in-day-out without problems. Are they all coming from the same source, or if you get them from different sources, is there a common link in the delivery chain? It may well be that Windoze has better error handling when the harddrive's reliability degrades (I don't want to say this is a good thing). This is almost certainly not true at least as far as FAT32 is concerned. The bad sector won't be marked as bad in the FAT until you run Scandisk, so it'll just go on trying to use it and crashing on the resultant errors. It may be that IDE hates me. I don't think it's my IDE controller, since there are 5 different machines involved, and the chance that all IDE controllers report bad blocks where there aren't any, but otherwise function fine with respect to detecting the drives (and not reporting the dreaded dma:intr errors). So I call to you and would like to know a couple of things: - does anyone else experience this? It is something I associate with secondhand drives that may not necessarily have been handled with due care. - does anyone know why this is happening? - why is this happening to me? I like to festoon my hard drives with fans (run off 5V instead of 12V to keep the noise down) as they can object to the temperatures they can heat themselves up to - but I think we can rule out heat in the case of your brand new Hitachi drive which is knackered as soon as you start
Re: OT: IDE/Bad Blocks: Call for mental assistance
Alex Malinovich [EMAIL PROTECTED] writes: Some drives can, in fact do bad sector remapping on the fly. By some drives, you mean all drives sold in the last 10 years, right? However, manually finding bad blocks on a drive is no real cause for concern. When a bad sector is found, it should be marked as such and the FS should not use it afterwards. Right... that'll work for now. But what will happen when the next block goes bad? You'll lose some data, rerun e2fsck -c, and wait for it to happen again, which it will, because the drive will only get worse. It's possible that the drive's remap area might get filled up early, but then go for a long time before causing significant annoyance, but in my experience, once a drive starts to show bad sectors, it's time to order a new drive. -- Alan Shutko [EMAIL PROTECTED] - I am the rocks. The Lion King is...really an adult-cartoon movie... -CHUM FM 30. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
How to isolate bad blocks/sectors?
The following is _reliably_ reported to the syslog every time I run
parted /dev/hdg print
Apr 6 11:44:36 creaky kernel: hdg: read_intr: status=0x59 { DriveReady
SeekComplete DataRequest Error }
Apr 6 11:44:36 creaky kernel: hdg: read_intr: error=0x40 {
UncorrectableError }, LBAsect=16778710, sector=16778710
Apr 6 11:44:36 creaky kernel: end_request: I/O error, dev 22:00 (hdg),
sector 16778710
parted goes on to report:
Disk geometry for /dev/hdg: 0.000-42934.992 megabytes
Disk label type: mac
MinorStart End Filesystem Name Flags
1 0.000 0.031 Apple
2 0.031 0.057 Macintosh
3 0.058 0.093 Macintosh
4 0.094 0.191 Macintosh
5 0.191 0.441 Macintosh
6 0.441 0.691 Patch Partition
7 0.691 4096.691 hfs MC_Kits
8 4096.691 8192.691 hfs Linux_Kits
9 8192.691 12288.691 hfs Delivery
10 12288.691 16384.691 hfs Development
11 16384.691 29384.691 ext2linux_dev_1
12 29384.691 42934.987 ext2linux_dev_2
Information: Don't forget to update /etc/fstab, if necessary.
My questions are:
- Where on the disk does this bad sector lie? partition table proper?
file system tables? data region?
- How can I isolate this bad sector?
Getting a disk error when reading the partition table makes me more than
a little nervous.
FWIW: the following commands yield the syslog errors:
-
parted /dev/hdg9 print
Apr 6 12:13:42 creaky kernel: hdg: read_intr: status=0x59 { DriveReady
SeekComplete DataRequest Error }
Apr 6 12:13:42 creaky kernel: hdg: read_intr: error=0x40 {
UncorrectableError }, LBAsect=16778710, sector=78
Apr 6 12:13:42 creaky kernel: end_request: I/O error, dev 22:09 (hdg),
sector 78
-
parted /dev/hdg11 print
Apr 6 12:16:55 creaky kernel: invalidate: busy buffer
-
parted /dev/hdg12 print
Apr 6 12:18:58 creaky kernel: invalidate: busy buffer
Apr 6 12:18:58 creaky last message repeated 21 times
Apr 6 12:18:58 creaky kernel: attempt to access beyond end of device
Apr 6 12:18:58 creaky kernel: 22:0c: rw=0, want=13875504, limit=13875503
-
Thanks,
--rich
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bad Blocks
Hola a todos: Tengo un Disco Duro con algunos cuantos bloques defectuosos, lo que genera que el sistema operativo me muestre mensajes de error de escritura bastante seguido. Se que debo utilizar badblocks y e2fsck para poder hacer que el sistema reconozca esos bloques como malos y los marque para no utilizarlos... el problema es que no logro entender como debo hacerlo exactamente debo utilizar un demonio para mantener la lista de sectores defectuosos ??? Desde ya Muchas Gracias Diego
Re: Bad Blocks
Buenas Diego, esto es una cosa que en su día me funcionó cuando trabajaba con un disco duro como el tuyo, quizá aún más inestable, y pude aprovecharle sin problemas tras esta operación: init 1 Baja a un nivel muy bajo para que mientras haces cosas peligrosas no anden otros procesos tocando las narices. Si conoces la partición donde estan los blolques defectuosos desmontala umount /dev/hdb1 (por ejemplo) y posteriormente efectua esta operación e2fsck -c /dev/hdb1 Esto marca los nodos de los bloques defectuosos para no ser utilizados. Probablemente ya hayas perdido algo de información que no será posible recuperar, pero por lo menos a partir de ahora sera estable. Si no conoces la partición desmonta todas las particiones que puedas y corre e2fsck sobre el disco en cuestión. e2fsck -c /dev/hda (por ejemplo) Mucha suerte. Chainy. PD: Si el sistema que tienes ahora debido a estos errores resulta muy inestable, te recomendaría que instalases una debian totalmente mínima y fuera esto lo primero que hicieses... luego ya ejecuta tasksel, dselect o apt-get directamente para instalar el resto. El lun, 03-02-2003 a las 15:07, Diego Ruiz Moreno escribió: Hola a todos: Tengo un Disco Duro con algunos cuantos bloques defectuosos, lo que genera que el sistema operativo me muestre mensajes de error de escritura bastante seguido. Se que debo utilizar badblocks y e2fsck para poder hacer que el sistema reconozca esos bloques como malos y los marque para no utilizarlos... el problema es que no logro entender como debo hacerlo exactamente debo utilizar un demonio para mantener la lista de sectores defectuosos ??? Desde ya Muchas Gracias Diego -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reiserfs bad blocks??
On Tue, 15 Oct 2002 12:49:19 +0800
Crispin Wellington [EMAIL PROTECTED] wrote:
On Tue, 2002-10-15 at 04:47, Bruce wrote:
I figured this is a hardware/bad block problem. I rebooted with a
rescue disk, and ran reiserfsck --check /dev/hda2, and received the
following error:
hda: read_intr: error-0x40 { UncorrectableError }, LBAsect=148574,
sector=148511 end_request: I/O errore, dev 03:02 (hda), sector
148511
Don't give up on that drive yet.I had the same error message on one hdd
after a power failure. Since it was under warranty but not broken enough
I ran a test on it for 48 hrs. and that didn't do anything to it. Seems
like some parts of the kernel got screwed up from the power failure.
After I reinstalled the OS the drive works fine without any hickups or
error messages.
Prost,
Klaus
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reiserfs bad blocks??
Am Dienstag, 15. Oktober 2002 09:51 schrieb Klaus Imgrund:
On Tue, 15 Oct 2002 12:49:19 +0800
Crispin Wellington [EMAIL PROTECTED] wrote:
On Tue, 2002-10-15 at 04:47, Bruce wrote:
I figured this is a hardware/bad block problem. I rebooted
with a rescue disk, and ran reiserfsck --check /dev/hda2, and
received the following error:
hda: read_intr: error-0x40 { UncorrectableError },
LBAsect=148574, sector=148511 end_request: I/O errore, dev
03:02 (hda), sector 148511
Don't give up on that drive yet.I had the same error message on
one hdd after a power failure. Since it was under warranty but
not broken enough I ran a test on it for 48 hrs. and that didn't
do anything to it. Seems like some parts of the kernel got
screwed up from the power failure. After I reinstalled the OS the
drive works fine without any hickups or error messages.
Prost,
Klaus
Hello,
I made similar experiences with my seagate. After compiling a new
kernel I had those messages. Do you use a via 686 chipset? Mabe you
have to choose an special option in your config to avoid such
messages in /var/log/messages.
I found this discussion on that issue:
http://groups.google.de/groups?hl=delr=ie=UTF-8oe=UTF-8threadm=slrn9vnna0.859.efflandt%40typhoon.xnet.comrnum=2prev=/groups%3Fq%3Dvia%2Bkernel%2B%2522read_intr:%2Berror-0x40%2B%257B%2BUncorrectableError%2B%257D%2522%26hl%3Dde%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26selm%3Dslrn9vnna0.859.efflandt%2540typhoon.xnet.com%26rnum%3D2
http://groups.google.de/groups?q=via+kernel+%22hda:+read_intr:+error-0x40+%7B+UncorrectableError+%7D%22hl=delr=ie=UTF-8oe=UTF-8selm=handler.9383.D9383.90920670422716.ackdone%40bugs.debian.orgrnum=3
http://groups.google.de/groups?hl=delr=ie=UTF-8oe=UTF-8threadm=3C3DABBC.4090302%40flock.orgrnum=6prev=/groups%3Fq%3Dvia%2Bkernel%2B%2522hda:%2Bread_intr:%2Berror-0x40%2B%257B%2BUncorrectableError%2B%257D%2522%26hl%3Dde%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26selm%3D3C3DABBC.4090302%2540flock.org%26rnum%3D6
With this search I found something about powermanagement used by
the bios but not build into the kernel:
http://groups.google.de/groups?q=via++status%3D0x59+vt82c686abtnG=Google-Suchehl=delr=ie=UTF-8oe=UTF-8
|Von:Brian McGroarty ([EMAIL PROTECTED])
|Betrifft:Re: DriveStatusError BadCRC on hda
|
|View this article only
|Newsgroups:linux.debian.user
|Datum:2001-08-18 18:20:08 PST
|
|On Sun, Aug 19, 2001 at 03:05:42AM +0100, Christian Jaeger wrote:
| Hello
|
| I've seen some messages in the system log and am wondering what
|to do
| with them:
|
| Aug 14 06:25:53 pflanze kernel: hda: timeout waiting for DMA
| Aug 14 06:25:53 pflanze kernel: ide_dmaproc: chipset supported
| ide_dma_timeout func only: 14
| Aug 14 06:25:53 pflanze kernel: hda: irq timeout: status=0x59 {
| DriveReady SeekComplete DataRequest Error }
| Aug 14 06:25:53 pflanze kernel: hda: irq timeout: error=0x84 {
| DriveStatusError BadCRC }
|
|With a previous machine, I recall seeing the above when a hard
|drive
|was configured by the BIOS to power down after some period of
|non-use,
|but power management wasn't built into the kernel. There was never
|any
|data loss, only the disturbing messages.
|
|Building a kernel with power support fixed it.
|
|I use that disk now for several month without any problems.
|
I found these options in my .config:
CONFIG_BLK_DEV_VIA82CXXX=y
CONFIG_VIA_RHINE=m
Unfortunateley I don't remember exactly the circumstances and the
solving of my harddiskproblem. It was on a mandrake system. Maybe
It was helpful to you.
regards
gerhard
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reiserfs bad blocks??
Thanks for the replies on how to deal with bad blocks on reiserfs; for the meantime, I managed to solve my problem (unable to use dpkg as several files in /var/lib/dpkg/lists were corrupt and unmoveable) by simply renaming the lists folder lists-BADBLOCKS, creating a new lists folder, copying everything over from the old folder, and replacing the ones I couldn't access with those from a similarly configured machine. Worked. Now to back up, and hope the drive doesn't die tooo soon. Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reiserfs bad blocks??
On Tue, 2002-10-15 at 04:47, Bruce wrote:
I figured this is a hardware/bad block problem. I rebooted with a rescue disk,
and ran reiserfsck --check /dev/hda2, and received the following error:
hda: read_intr: error-0x40 { UncorrectableError }, LBAsect=148574,
sector=148511 end_request: I/O errore, dev 03:02 (hda), sector 148511
From the above, I gather I have bad blocks on the hard drive. I had a look at
www.namesys.com/bad-block-handling.html, and the only mention of bad blocks
includes instructions for how to install reiserfs on a (presumably blank)
partition with bad blocks; it says nothing (that I could find) about what to
do when your _existing_ reiserfs drive gets bad blocks.
I have seen similar questions posted elsewhere, i.e., on the linux kernel
mailing list (though without answers), i.e.,
http://www.uwsg.iu.edu/hypermail/linux/kernel/0202.3/0546.html
Is there a way (yet) to mark bad blocks on a reiserfs filesystem??
No. Reiser does not handle bad-blocks. Ext2/3 does, but that doesn't
mean anything, because you shouldn't get them in the first place. Modern
HDD remap bad blocks internally, so if you see hard read error's like
your seeing, your best bet is to get a new Hard Drive.
This has happened to me, and I moved the filesystem to a new HDD, and
re-formatted the dodgy drive with ext3 with a complete bad-block scan
during the format. I now use this space as spare non-critical space.
Lots of rubbish and downloads, and iso images (of cd's I have), and
backups of data etc. I am fully expecting the HDD to start smoking any
day and for me to loose all my data (which doesn't matter anyway). But
so far its been turning for nigh on 6 months now without a blip.
The important thing though, is *dont trust it*.
Kind Regards
Crispin Wellington
signature.asc
Description: This is a digitally signed message part
Re: Reiserfs bad blocks??
Thanks for the reply; luckily, the machine is still bootable, and seems to work fine except for the fact that I cannot install or remove any packages. I'll back up the drive, and dig out the receipt; the drive is only 6 months old and is still under warranty, so shouldn't have started deteriorating quite yet... B. On Tuesday 15 October 2002 00:46, Crispin Wellington wrote: Is there a way (yet) to mark bad blocks on a reiserfs filesystem?? No. Reiser does not handle bad-blocks. Ext2/3 does, but that doesn't mean anything, because you shouldn't get them in the first place. Modern HDD remap bad blocks internally, so if you see hard read error's like your seeing, your best bet is to get a new Hard Drive. This has happened to me, and I moved the filesystem to a new HDD, and re-formatted the dodgy drive with ext3 with a complete bad-block scan during the format. I now use this space as spare non-critical space. Lots of rubbish and downloads, and iso images (of cd's I have), and backups of data etc. I am fully expecting the HDD to start smoking any day and for me to loose all my data (which doesn't matter anyway). But so far its been turning for nigh on 6 months now without a blip. The important thing though, is *dont trust it*. Kind Regards Crispin Wellington -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[OFFTOPIC]: How to recover reiserfs from bad blocks on HD?
Apologies for not directly debian-related question on the list, but I run sid on the problem computer ( hope this is good excuse:-) ) One of my hard drives had developed bad sectors on reiserfs partition and kernel paniced. Now I cannot mount that partition, because of the read errors on the drive. How do I salvage the data? So far I made an image of that partition with copy-blocks tool from ftp://ftp.atnf.csiro.au/pub/people/rgooch/linux/disc-recovery-utils-current.tgz and I can mount the image using loop devices. However I am concerned with files/metadata damaged by missing data from the bad sectors and possible further damage from journal replay. How can I figure out if anything is damaged and if yes what files are damaged? How do I match sectors/blocks with filesystem data? Also, any thoughts on future use of that HD are welcome. -- = mailto:[EMAIL PROTECTED] ===http://www.geocities.com/astavitsky = GPG Key 0xF7343C8B: 68DD 1E1B 2C98 D336 E31F C87B 91B9 5244 F734 3C8B |_Alexander Stavitsky pgpSmUSuugZ9D.pgp Description: PGP signature
Re: Marking bad blocks
on Sun, Apr 15, 2001 at 09:29:07PM +0200, Enrico Zini ([EMAIL PROTECTED]) wrote: Hello! Using badblocks I've found some bad blocks on one of my hard disks, and I'd like to mark them bad so that Linux will avoid to use them. The number of bad blocks I've found is low, but they are scattered on many disk partitions: some of them are formatted ext2, some reiserfs and one is used as swap. For the ext2 partition the problem is easily solved, since e2fsck has the -l switch to be used exactly for that purpose. The problem are reiserfs and the swap partition. The swap partition could be solved, too, by running mkswap with the -c option. The only problem with that is that I'll have to wait for another full badblock check, and since I already have the bad block list, I'd like to just pass that list to mkswap to make it quicker. If there isn't any way of doing it, I'll use mkswap -c and be fine. We remain with reierfs. Reiserfsck has no options regarding bad blocks, and I can't remember any other reiserfs utilities that could help with that. Is there a way of doing it? Now I'll just wait for news here, while trying to figure out why an IBM-DJNA-352500 three months old which passes all ide-smart internal OnLine and OffLine tests should turn out to have bad blocks at all. And doing backups, of course. Did you ever get an answer to this? I'd run the question past a reiserfs development list or Hans himself. -- Karsten M. Self kmself@ix.netcom.comhttp://kmself.home.netcom.com/ What part of Gestalt don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org pgpsvGnyrS8Z0.pgp Description: PGP signature
Marking bad blocks
Hello! Using badblocks I've found some bad blocks on one of my hard disks, and I'd like to mark them bad so that Linux will avoid to use them. The number of bad blocks I've found is low, but they are scattered on many disk partitions: some of them are formatted ext2, some reiserfs and one is used as swap. For the ext2 partition the problem is easily solved, since e2fsck has the -l switch to be used exactly for that purpose. The problem are reiserfs and the swap partition. The swap partition could be solved, too, by running mkswap with the -c option. The only problem with that is that I'll have to wait for another full badblock check, and since I already have the bad block list, I'd like to just pass that list to mkswap to make it quicker. If there isn't any way of doing it, I'll use mkswap -c and be fine. We remain with reierfs. Reiserfsck has no options regarding bad blocks, and I can't remember any other reiserfs utilities that could help with that. Is there a way of doing it? Now I'll just wait for news here, while trying to figure out why an IBM-DJNA-352500 three months old which passes all ide-smart internal OnLine and OffLine tests should turn out to have bad blocks at all. And doing backups, of course. Bye, Enrico -- GPG public key available on finger -l [EMAIL PROTECTED]
SCSI HD developping bad blocks (was Re: wu-ftpd fails CRC checks
On Thu, 24 Feb 2000 10:51:08 -0800, Alex McCool wrote: I've noticed that the sector=591714 (and one other) is always the culprit. Can someone tell me how to repair/badblock these sectors? Back it up, then low-level format it. BUT BEWARE: Usually bad sector remapping works transparently w/o the user noticing it. The fact that there are bad sectors visible to the user usually means the HD is dying, so prepare for the worst. Sorry, but this is the truth. -- Sign the EU petition against SPAM: L I N U X .~. http://www.politik-digital.de/spam/The Choice /V\ of a GNU /( )\ Generation ^^-^^
mke2fs - bad blocks
Hi, I got a small used disk given to me that I am trying to put into a small system I have. When I tried to run mke2fs on any of the partitions I had created I get Checking fro bad blocks (read-only test): Bad block 0 out of range;ignored. done Block 1 in primary superblock/group descriptor area bad. Blocks 1 through 3 must be good in order to build a filesystem. Aborting Similarly, mkswap gives: --- 4120 bad pages mkswap: fatal: first page unreadable --- I suspect the drive is toast, but thought I would check first. Does anyone know if a low level format or something else can save this, or is it just garbage ? Thanks, Gerald Crimp -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: mke2fs - bad blocks
Many vendors supply low-level format utilities which run under DOS. These programs are able to mark the bad blocks at a very low level so you can use the disk. Check out the disk manufacturer's website. Alternatively, create a small partition over the first couple blocks and start your real partition after that. G. Crimp wrote: Hi, I got a small used disk given to me that I am trying to put into a small system I have. When I tried to run mke2fs on any of the partitions I had created I get Checking fro bad blocks (read-only test): Bad block 0 out of range;ignored. done Block 1 in primary superblock/group descriptor area bad. Blocks 1 through 3 must be good in order to build a filesystem. Aborting Similarly, mkswap gives: --- 4120 bad pages mkswap: fatal: first page unreadable --- I suspect the drive is toast, but thought I would check first. Does anyone know if a low level format or something else can save this, or is it just garbage ? Thanks, Gerald Crimp -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Jens B. Jorgensen [EMAIL PROTECTED] -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: mke2fs - bad blocks
I suspect the drive is toast, but thought I would check first. Does anyone know if a low level format or something else can save this, or is it just garbage ? Generally one bad block will come many, sooner or later. It is a defect on the surface of the disk. However modern harddisks have some part of their capacity hidden and it is used to map the bad blocks away. If the beginning of the disk has many bad blocks, then you most propably are out of luck. --j -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: how to cope with bad blocks (and off-topic: WD warranty policy)
Hi, I have now some bad blocks on my 2-year-old WD Caviar IDE drive. I'm not overly concerned, because I have a brand new SeaGate, on where I install hamm atm, but I wonder if linux can mark bad blacks as 'used', so that it doesn't write on them anymore. Or how do you cope with bad blocks? (I also get irq timeouts and drive resets, and then the system hangs. Why?) The drive has a three year warranty. Will WD fix the drive or sent me a new one because of bad blocks? Has anyone has experience with WD warranty? Should I try to make heavy use of the drive to detect more (soon to be) bad blocks, as long as I have warranty? [If you have not thrown your HD around your house...] Bad blocks means that there is something wrong in the surface of the disk. Most likely there will be more sooner or later, and that will be on a disk that contains your data. It is a valid reason for warranty exchange or repair. I don't know any manufacturers that would repair HD's anymore, atleast if the defect is in the disks or in mechanics.. repairs are worth it only conserning the electronics parts. Contact the place you bought the drive, they know the procedure, some manufacturers do the change themselves, some operate only through dists. (Me does this for work, forget any beliefs, that brand xyz, model xyz won't blow up :)) .. And did I mention backups? --j -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how to cope with bad blocks (and off-topic: WD warranty policy)
On Sun, Apr 12, 1998 at 02:55:29PM -0700, George Bonser wrote: On Sun, Apr 12, 1998 at 04:09:50PM +0200, Marcus Brinkmann wrote: I have now some bad blocks on my 2-year-old WD Caviar IDE drive. I'm not overly concerned, because I have a brand new SeaGate, on where I install hamm atm, but I wonder if linux can mark bad blacks as 'used', so that it doesn't write on them anymore. Or how do you cope with bad blocks? (I also get irq timeouts and drive resets, and then the system hangs. Why?) Just a little note: I installed one of these new DMA33/EIDE drives in a system that had been running for over 6 months. At the same time, I moved from 2.0.29 kernel to 2.0.33. The machine has not been up for more than two weeks since. I started getting disk errors and IDE resets as soon as I installed that new drive. Is that new Seagate that you mention one of the new large DMA33 capable drives and did the problems with the WD start around the time you installed the Seagate? Also which kernel are you running? Interesting. The disk in our system is an ancient Quantum 1Gb, and actually I suspected the power supply might have been faulty before deploying the machine (but it took 15 months for anything to happen); occasionally I got disk resets even loading LILO. I suspect dry joints in the power supply (Quantums seem to be very power-sensitive, a friend of mine has had the same power supply problem with the same disk) but I haven't opened it to look yet. Hamish -- Hamish Moffatt, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5 CCs of replies from mailing lists are welcome. http://hamish.home.ml.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how to cope with bad blocks (and off-topic: WD warranty policy)
On Sun, Apr 12, 1998 at 02:55:29PM -0700, George Bonser wrote: On Sun, Apr 12, 1998 at 04:09:50PM +0200, Marcus Brinkmann wrote: I have now some bad blocks on my 2-year-old WD Caviar IDE drive. I'm not overly concerned, because I have a brand new SeaGate, on where I install hamm atm, but I wonder if linux can mark bad blacks as 'used', so that it doesn't write on them anymore. Or how do you cope with bad blocks? (I also get irq timeouts and drive resets, and then the system hangs. Why?) Just a little note: I installed one of these new DMA33/EIDE drives in a system that had been running for over 6 months. At the same time, I moved from 2.0.29 kernel to 2.0.33. The machine has not been up for more than two weeks since. I started getting disk errors and IDE resets as soon as I installed that new drive. Is that new Seagate that you mention one of the new large DMA33 capable drives and did the problems with the WD start around the time you installed the Seagate? Also which kernel are you running? Wow, what shall I say? I installed the SeaGate Medalist 2122 (ST32122A) 2,1 GB just a couple of days ago, and am running the 2.0.33-5 kernel. I didn't have any trouble before installing the new drive. I got first bad blocks trouble yesterday. But I don't know if the SeaGate drive is one of the new drives you mention. This is what dmesg tells me: ide: i82371 PIIX (Triton) on PCI bus 0 function 57 ide0: BM-DMA at 0xe800-0xe807 ide1: BM-DMA at 0xe808-0xe80f hda: WDC AC21000H, 1033MB w/128kB Cache, CHS=525/64/63, DMA hdc: ST32122A, 2014MB w/128kB Cache, CHS=4092/16/63 hdd: TOSHIBA CD-ROM XM-5302TA, ATAPI CDROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 Do you think this is a kernel bug? Gosh. I'm out of knowledge and experience here (and have to get some sleep). (BTW: atm all is okay, but I don't work with hda much. I installed Debian 2.0 fresh on hdc and am now moving). Good night good fellows, Marcus -- Rhubarb is no Egyptian god.Debian GNU/Linuxfinger brinkmd@ Marcus Brinkmann http://www.debian.orgmaster.debian.org [EMAIL PROTECTED]for public PGP Key http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ PGP Key ID 36E7CD09 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
how to cope with bad blocks (and off-topic: WD warranty policy)
Hi, I have now some bad blocks on my 2-year-old WD Caviar IDE drive. I'm not overly concerned, because I have a brand new SeaGate, on where I install hamm atm, but I wonder if linux can mark bad blacks as 'used', so that it doesn't write on them anymore. Or how do you cope with bad blocks? (I also get irq timeouts and drive resets, and then the system hangs. Why?) The drive has a three year warranty. Will WD fix the drive or sent me a new one because of bad blocks? Has anyone has experience with WD warranty? Should I try to make heavy use of the drive to detect more (soon to be) bad blocks, as long as I have warranty? Thank you for your help, Marcus -- Rhubarb is no Egyptian god.Debian GNU/Linuxfinger brinkmd@ Marcus Brinkmann http://www.debian.orgmaster.debian.org [EMAIL PROTECTED]for public PGP Key http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ PGP Key ID 36E7CD09 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how to cope with bad blocks (and off-topic: WD warranty policy)
On Sun, Apr 12, 1998 at 04:09:50PM +0200, Marcus Brinkmann wrote: I have now some bad blocks on my 2-year-old WD Caviar IDE drive. I'm not overly concerned, because I have a brand new SeaGate, on where I install hamm atm, but I wonder if linux can mark bad blacks as 'used', so that it doesn't write on them anymore. Or how do you cope with bad blocks? (I also get irq timeouts and drive resets, and then the system hangs. Why?) e2fsck -c /dev/device will do it. I believe the IRQ timeouts and drive resets are a symptom of bad blocks, they were when I got some here. Actually, most of the IRQ timeouts and drive resets were caused by a faulty power supply in that machine. I replaced it, and found one bad blocks with e2fsck, and the machine has been perfect ever since. (Up 62 days, exactly 62 days since I replaced that power supply.) The drive has a three year warranty. Will WD fix the drive or sent me a new one because of bad blocks? Has anyone has experience with WD warranty? Should I try to make heavy use of the drive to detect more (soon to be) bad blocks, as long as I have warranty? It's worth calling them. hamish -- Hamish Moffatt, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5 CCs of replies from mailing lists are welcome. http://hamish.home.ml.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how to cope with bad blocks (and off-topic: WD warranty policy)
The drive has a three year warranty. Will WD fix the drive or sent me a new one because of bad blocks? Has anyone has experience with WD warranty? Should I try to make heavy use of the drive to detect more (soon to be) bad blocks, as long as I have warranty? If the drive is actively developing more bad blocks, back up important data *NOW*. You may have as little as three days, or even less, before it dies forever. IDE drives do not develop bad blocks, in a normal situation, unless they are about to die. In my experience, anyway. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how to cope with bad blocks (and off-topic: WD warranty policy)
On Mon, Apr 13, 1998 at 12:14:33AM +1000, Hamish Moffatt wrote: On Sun, Apr 12, 1998 at 04:09:50PM +0200, Marcus Brinkmann wrote: I have now some bad blocks on my 2-year-old WD Caviar IDE drive. I'm not overly concerned, because I have a brand new SeaGate, on where I install hamm atm, but I wonder if linux can mark bad blacks as 'used', so that it doesn't write on them anymore. Or how do you cope with bad blocks? (I also get irq timeouts and drive resets, and then the system hangs. Why?) e2fsck -c /dev/device will do it. I believe the IRQ timeouts and drive resets are a symptom of bad blocks, they were when I got some here. If this really will mark bad blocks, I could have real trouble (and I will follow Ben Pfaffs advise to backup). I'm a bit confused: When I run e2fsck -c on the drive again, will it find the bad blocks already found again? I ran this command, and again I got timeouts. Then I ran the command a second time, and it found (the same?) bad blocks. I think it were the same because the sector numbers have been the same/similar? Actually, most of the IRQ timeouts and drive resets were caused by a faulty power supply in that machine. I replaced it, and found one bad blocks with e2fsck, and the machine has been perfect ever since. (Up 62 days, exactly 62 days since I replaced that power supply.) I think the power supply is okay... I will run e2fsck -c again, will backup and repartition the drive and will use it. And I will contact WD about the warranty. Thank you for your help, Marcus -- Rhubarb is no Egyptian god.Debian GNU/Linuxfinger brinkmd@ Marcus Brinkmann http://www.debian.orgmaster.debian.org [EMAIL PROTECTED]for public PGP Key http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ PGP Key ID 36E7CD09 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ext2fs: bad blocks handling
Dear Debian users, Does anybody know how are handled the bad blocks on an ext2fs partition? Is there an automatic handling or must I always use the badblocks command and update the badblocks list with e2fsck? -- __ Cedric Bapst / /__ __ [EMAIL PROTECTED] / / D e b i a n G N U \ \/ / / / __ __ __ \ / / / / / / _ \ / / / / / \ ...Look out Bill, / /___ / / / / ) // (_/ / / /\ \ here comes... (__)(_/ (_/ (_/ \/ (_/ \_) ___ http://www.debian.org ___ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Linux Bad Blocks
-BEGIN PGP SIGNED MESSAGE- On 2 Mar 1998, Pedro Quaresma de Almeida wrote: I have a hard disk that had gained a couple of bad blocks recently. Linux (Debian 1.3.1) is having problems dealing with them kernel panic ... what can I do to mark the bad block in Linux? Try e2fsck -c on the root partition, using the rescue disk. - From the e2fsck man page: -c This option causes e2fsck to run the badblocks(8) program to find any blocks which are bad on the filesystem, and then marks them as bad by adding them to the bad block inode. -BEGIN PGP SIGNATURE- Version: 2.6.3ia Charset: latin1 iQCVAgUBNQAktCqK7IlOjMLFAQF3uQP7BIbc7aDxuvXkmjVfBLInoMY71rOwXKKm Ox52PpxbkZPB04y7MyQ5pR9Zj2f5YHq1SPdgFKjYX3rMsaS0WyM2AgTzDLXtNkFT t7YzT46VmOOR90HRASEYv9Tgdpp4O7WBRRgmNaUxKx6AqxhBwTGnE0alYepwMRc8 KpIMgpPGGyQ= =3zoZ -END PGP SIGNATURE- -- E-mail the word unsubscribe to [EMAIL PROTECTED] TO UNSUBSCRIBE FROM THIS MAILING LIST. Trouble? E-mail to [EMAIL PROTECTED] .
Linux Bad Blocks
Hi I have a hard disk that had gained a couple of bad blocks recently. Linux (Debian 1.3.1) is having problems dealing with them kernel panic ... what can I do to mark the bad block in Linux? Shoud I go to msdos and format the disk? will this last option solve my problem? Thanks -- At\'e breve === Pedro Quaresma de Almeida Departamento de Matem\'atica Faculdade de Ci\^encias e Tecnologia Universidade de Coimbra P-3000 COIMBRA, PORTUGAL e-mail: [EMAIL PROTECTED] url: http://www.mat.uc.pt/~pedro/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Bad blocks
I keep getting {DriveReady SeekComplete DataRequest Error }'s and I
figure
it's all bad blocks. I ran fsck /dev/hda2 but it only seems to do a
cursory examination (not taking nearly as long as the scan when I installed
Linux) and I keep getting the same errors after presumably correcting them.
So I was wondering what the utility was to thouroughly check all of the HD
for errors.
Also, I've been told not to run disk checks while the HD is mounted, how
can I load linux sans mounting the HD? does it work if I boot from a
floppy?
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Re: Bad blocks
I keep getting {DriveReady SeekComplete DataRequest Error }'s and I
figure
it's all bad blocks. I ran fsck /dev/hda2 but it only seems to do a
cursory examination (not taking nearly as long as the scan when I installed
Linux) and I keep getting the same errors after presumably correcting them.
So I was wondering what the utility was to thouroughly check all of the HD
for errors.
Use the badblocks(8) program.
Also, I've been told not to run disk checks while the HD is mounted,
how
can I load linux sans mounting the HD? does it work if I boot from a
floppy?
It shouldn't be a problem to run badblocks while the HD is mounted; it
does not write to the drive, just reads from it.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Re: Bad blocks
Normally you would boot from a rescue floppy for such maintenance
activities and mount your filesystem read only. I haven't had to do
this in a long time but it also seems to me that you can boot to single
user and remount root as read only.
FizzyPop wrote:
I keep getting {DriveReady SeekComplete DataRequest Error }'s and I
figure
it's all bad blocks. I ran fsck /dev/hda2 but it only seems to do a
cursory examination (not taking nearly as long as the scan when I installed
Linux) and I keep getting the same errors after presumably correcting them.
So I was wondering what the utility was to thouroughly check all of the HD
for errors.
Also, I've been told not to run disk checks while the HD is mounted,
how
can I load linux sans mounting the HD? does it work if I boot from a
floppy?
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
--
best,
-bill
[EMAIL PROTECTED] [EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED]
from a 1996 Micro$loth ad campaign:
The less you know about computers the more you want Micro$oft!
See! They do get some things right!
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Re: Bad blocks
On Thu, Feb 26, 1998 at 08:12:29PM -0500, Ben Pfaff wrote:
I keep getting {DriveReady SeekComplete DataRequest Error }'s and I
figure
it's all bad blocks. I ran fsck /dev/hda2 but it only seems to do a
cursory examination (not taking nearly as long as the scan when I installed
Linux) and I keep getting the same errors after presumably correcting them.
So I was wondering what the utility was to thouroughly check all of the HD
for errors.
Use the badblocks(8) program.
Also, I've been told not to run disk checks while the HD is mounted,
how
can I load linux sans mounting the HD? does it work if I boot from a
floppy?
It shouldn't be a problem to run badblocks while the HD is mounted; it
does not write to the drive, just reads from it.
Hmmm. If badblocks doesn't write to the drive, how will this help?
e2fsck -c /dev/hda2 will run e2fsck, and it will run badblocks, and
note the blocks as bad and move all the data it can to other places.
Note that these IDE disk errors can be power supply related. Most of
the errors I was having with a disk went away when I replaced the power
supply. One bad sector remained which I fixed with e2fsck.
Hamish
--
Hamish Moffatt, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5
CCs of replies from mailing lists are welcome. http://hamish.home.ml.org
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Re: Bad blocks
Also, I've been told not to run disk checks while the HD is mounted, how can I load linux sans mounting the HD? does it work if I boot from a floppy? It shouldn't be a problem to run badblocks while the HD is mounted; it does not write to the drive, just reads from it. Hmmm. If badblocks doesn't write to the drive, how will this help? e2fsck -c /dev/hda2 will run e2fsck, and it will run badblocks, and note the blocks as bad and move all the data it can to other places. Running badblocks by itself first is a good way to determine whether you should just do an `e2fsck -c' or whether it's time to buy a new drive :-) -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Fixing Bad Blocks
Hi. I recently posted a message about Kernel Panic that was due to bad blocks in my hard drive. My plan is to just start all over. What I need now is a way to fix bad blocks or to skip over them if neccessary. I received a message that told me to use e2fsck -c /dev/hda? ( where ? is any one of my 5 partions) to find the bad the bad block and then to use badblocks to mark them. However when I did e2fsck -c /dev/hda? again it still sees the bad blocks and I am afraid that this will still cause the system to hang. I am thinking of reformatting and drive all over again. Will this fix the problem? Does any body have any suggestions. Is there any program that fixes badblocks? Patrick -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Fixing Bad Blocks
You need to create a file containing the block numbers of the bad blocks. The badblocks program should work. Then run e2fsck -L on the *un-mounted* filesystem. See the manpages for badblocks and e2fsck. You may still need to re-make the filesystem on the affected partition. I would repeat e2fsck -f -L badblock_filename device_name until a clean check is achieved and cross your fingers. --Bob PATRICK DAHIROC wrote: Hi. I recently posted a message about Kernel Panic that was due to bad blocks in my hard drive. My plan is to just start all over. What I need now is a way to fix bad blocks or to skip over them if neccessary. I received a message that told me to use e2fsck -c /dev/hda? ( where ? is any one of my 5 partions) to find the bad the bad block and then to use badblocks to mark them. However when I did e2fsck -c /dev/hda? again it still sees the bad blocks and I am afraid that this will still cause the system to hang. I am thinking of reformatting and drive all over again. Will this fix the problem? Does any body have any suggestions. Is there any program that fixes badblocks? Patrick -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Fixing Bad Blocks
On Mon, 20 Oct 1997, Bob Clark wrote: You need to create a file containing the block numbers of the bad blocks. The badblocks program should work. Then run e2fsck -L on the *un-mounted* filesystem. See the manpages for badblocks and e2fsck. You may still need to re-make the filesystem on the affected partition. I would repeat e2fsck -f -L badblock_filename device_name until a clean check is achieved and cross your fingers. However, if you repeat this, and the filesystem keeps getting more and more badblocks, the problem is getting worse (e.g. it's slowly crashing). Brandon - Brandon Mitchell [EMAIL PROTECTED] We all know linux is great... it PGP: finger -l [EMAIL PROTECTED] does infinite loops in 5 seconds Phone: (757) 221-4847 --Linus Trovalds -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: bad blocks
Hi,
I am running Debian 1.1 and am having problems with bad blocks. I would
appreciate any help in solving my problem.
This is the error message:
Bad Block 1384505 in group 169's inode table. Relocate? Yes.
WARNING: Severe data loss possible!
Bad Block 1384521 in group 169's inode table. Relocate? Yes.
WARNING: Severe data loss possible!
hda: read_intr: status=0X59 {DriveReady SeekComplete DataRequest Error}
hda: read_intr: error=0X40 {Uncorrectable Error}, LBAsect=2902066,
sector=2769010
end_request: I/O error, dev 03:02, sector 2769010
Error reading block 1384505 (attempt to read block from filesystem resulted
in short read) while doing inode scan.
/dev/hda2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
fsck failed. Please repair manually and reboot.
NOTE: I have tried running both fsck e2fsck manually but get the same
error. I also, tried marking the bad blocks with e2fsck but wasn't
successful.
First idea: Your harddisk is breaking. Solution: replace it.
Second thought: I faintly remember someone having similar problems with LBA
addressing.
If your system started having these problems suddenly, without any changes
in confiuration, the first idea is most propably the right one, I'm afraid.
I've seen
a lot of broken harddisks - they do break down.
--j
Thanks,
Thalia
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
bad blocks
Hi,
I am running Debian 1.1 and am having problems with bad blocks. I would
appreciate any help in solving my problem.
This is the error message:
Bad Block 1384505 in group 169's inode table. Relocate? Yes.
WARNING: Severe data loss possible!
Bad Block 1384521 in group 169's inode table. Relocate? Yes.
WARNING: Severe data loss possible!
hda: read_intr: status=0X59 {DriveReady SeekComplete DataRequest Error}
hda: read_intr: error=0X40 {Uncorrectable Error}, LBAsect=2902066,
sector=2769010
end_request: I/O error, dev 03:02, sector 2769010
Error reading block 1384505 (attempt to read block from filesystem resulted
in short read) while doing inode scan.
/dev/hda2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
fsck failed. Please repair manually and reboot.
NOTE: I have tried running both fsck e2fsck manually but get the same
error. I also, tried marking the bad blocks with e2fsck but wasn't
successful.
Thanks,
Thalia
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
hard drive problem - cannot mark bad blocks
Recently, I posted that I got these errors with my hard drive:
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=2342358,
sector=2342294
end_request: I/O error, dev 03:01, sector 2342294
It also crashed on occasion. Running e2fsck -cvf /dev/hda1 didn't fix
the problem. At Bruce's suggestion, I tried running the badblocks
program. It found 48 bad blocks. I then ran e2fsck -l BadBlocksFile
/dev/hda1 where BadBlocksFile was the output from running badblocks.
Everything appeared to worked great for a while after that. I did a
complete backup of the hard drive without getting any of these messages
(previously, I got many of these errors during backups and sometimes a
crash). Running the badblocks program after that did not turn up any bad
blocks.
I then left town for a few days. When I came back, we were once again
getting these messages. I tried doing the same fix as before. Running
badblocks revealed the same 48 bad blocks as before. However, now after
running e2fsck -l BadBlocksFile /dev/hda1 the problem still persists. It
appears that the bad blocks aren't being put in the list of bad blocks for
the filesystem. But, running dumpe2fs /dev/hda1 shows that those blocks
are indeed marked as bad blocks!
Any thoughts on what could be happening and what I could try next?
Thanks,
Gerry
[EMAIL PROTECTED]
