Fdisk cannot open dev sda input output error

This all started when i install kubuntu 10.10 on my Western Digital Hard drive. It installed perfectly but one day i was not able to boot to kubuntu. so i tried to install it again but got the error "INPUT OUTPUT ERROR ON READ /DEV/SDA" and installer is not detecting windows partitions I have 120G western digital wdc wd1200bevs-22rst0 hard drive. I have tried following commands 1) fdisk -l this doesn't detect my hard drive

Input output error on read /dev/sda

This all started when i install kubuntu 10.10 on my Western Digital Hard drive. It installed perfectly but one day i was not able to boot to kubuntu. so i tried to install it again but got the error«INPUT OUTPUT ERROR ON READ /DEV/SDA»
and installer is not detecting windows partitionsI have 120G western digital wdc wd1200bevs-22rst0 hard drive.I have tried following commands
1) fdisk -l
this doesn’t detect my hard drive
2) sfdisk -l
read error. cannot read sector 0
3) Gparted live cd
input output error
4) test disk (gparted live cd)
read error
5) test disk(windows version)
no error detected
6) smartmontools
completly passed.no error detected
7) windows is saying that hard drive is healthy
8) even the manufacture’s life diagnostic tool says that hard drive is healthy
9) tried to burn the cds at slowest speed and even with usb stick . no luck
10) completely wiped the hard drive
11) tried the alternate cd but still no luck
12) used ‘fsck’ but still failed

I have tried ubuntu, xubuntu and kubuntu 10.10 and 11.04 but no luck

I have tried the above things and still no succes . if anyone can help?thanks in advance

Last edited by Manuj19; June 9th, 2011 at 04:59 PM.

Reason: Some additions i forgot

Re: Input output error on read /dev/sda

Re: Input output error on read /dev/sda

[QUOTE=jerrrys;10920829]maybe

http://ubuntuforums.org/showthread.php?t=1710706

Thank you mate

I have seen this thread. My problem is exactly same. But according to it i have to turn on AHCI mode in my BIOS
but my hard drive do not support AHCI mode . So i cannot turn it on. Thanks for help and would like to hear more suggestions from you.

hdd: SATA wdc wd1200bevs-22rsto

Re: Input output error on read /dev/sda

so you ran the boot info script and no joy?

Re: Input output error on read /dev/sda

AHCI is not a property of the drive; it is the native mode of the SATA controller.

Did you actually run the SMART long selftest? How about posting the actual SMART attributes? Also check your dmesg for errors.

Re: Input output error on read /dev/sda

Quote Originally Posted by jerrrys
View Post

so you ran the boot info script and no joy?

Here is the output of boot info script

Boot Info Script 0.60 from 17 May 2011

============================= Boot Info Summary: ===============================

=> No known boot loader is installed in the MBR of /dev/sda.
=> Syslinux MBR (3.61-4.03) is installed in the MBR of /dev/sdb.

sdb1: __________________________________________________ ________________________

File system: vfat
Boot sector type: SYSLINUX 4.03 2010-10-22
Boot sector info: Syslinux looks at sector 1426536 of /dev/sdb1 for its
second stage. SYSLINUX is installed in the G:syslinux
directory. The integrity check of the ADV area failed.
No errors found in the Boot Parameter Block.
Operating System:
Boot files: /syslinux/syslinux.cfg /ldlinux.sys

============================ Drive/Partition Info: =============================

Drive: sda __________________________________________________ ___________________

Partition Boot Start Sector End Sector # of Sectors Id System

Invalid MBR Signature found.

Drive: sdb __________________________________________________ ___________________

Disk /dev/sdb: 4007 MB, 4007624704 bytes
255 heads, 63 sectors/track, 487 cylinders, total 7827392 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdb1 * 63 7,823,654 7,823,592 b W95 FAT32

«blkid» output: __________________________________________________ ______________

Device UUID TYPE LABEL

/dev/loop0 squashfs
/dev/sdb1 8CCE-9A73 vfat KINGSTON

================================ Mount points: =================================

Device Mount_Point Type Options

/dev/loop0 /rofs squashfs (ro,noatime)
/dev/sdb1 /cdrom vfat (ro,noatime,fmask=0022,dmask=0022,codepage=cp437,i ocharset=iso8859-1,shortname=mixed,errors=remount-ro)

========================= sdb1/syslinux/syslinux.cfg: ==========================

———————————————————————————
# D-I config version 2.0
include menu.cfg
default vesamenu.c32
prompt 0
timeout 300
ui gfxboot bootlogo
———————————————————————————

================= sdb1: Location of files loaded by Syslinux: ==================

GiB — GB File Fragment(s)

?? = ?? ldlinux.sys 1
?? = ?? syslinux/gfxboot.c32 1
?? = ?? syslinux/syslinux.cfg 1
?? = ?? syslinux/vesamenu.c32 1

============== sdb1: Version of COM32(R) files used by Syslinux: ===============

syslinux/gfxboot.c32 : COM32R module (v4.xx)
syslinux/vesamenu.c32 : COM32R module (v4.xx)

======================== Unknown MBRs/Boot Sectors/etc: ========================

Unknown MBR on /dev/sda

=============================== StdErr Messages: ===============================

ERROR: asr: reading /dev/sda[Input/output error]
ERROR: ddf1: reading /dev/sda[Input/output error]
ERROR: ddf1: reading /dev/sda[Input/output error]
ERROR: hpt37x: reading /dev/sda[Input/output error]
ERROR: hpt45x: reading /dev/sda[Input/output error]
ERROR: isw: reading /dev/sda[Input/output error]
ERROR: isw: reading /dev/sda[Input/output error]
ERROR: isw: reading /dev/sda[Input/output error]
ERROR: jmicron: reading /dev/sda[Input/output error]
ERROR: lsi: reading /dev/sda[Input/output error]
ERROR: nvidia: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: sil: reading /dev/sda[Input/output error]
ERROR: via: reading /dev/sda[Input/output error]
ERROR: asr: reading /dev/sda[Input/output error]
ERROR: ddf1: reading /dev/sda[Input/output error]
ERROR: ddf1: reading /dev/sda[Input/output error]
ERROR: hpt37x: reading /dev/sda[Input/output error]
ERROR: hpt45x: reading /dev/sda[Input/output error]
ERROR: isw: reading /dev/sda[Input/output error]
ERROR: isw: reading /dev/sda[Input/output error]
ERROR: isw: reading /dev/sda[Input/output error]
ERROR: jmicron: reading /dev/sda[Input/output error]
ERROR: lsi: reading /dev/sda[Input/output error]
ERROR: nvidia: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: pdc: reading /dev/sda[Input/output error]
ERROR: sil: reading /dev/sda[Input/output error]
ERROR: via: reading /dev/sda[Input/output error]
hexdump: /dev/sda: Input/output error
hexdump: /dev/sda: Input/output error
hexdump: /dev/sda: Input/output error
/home/ubuntu/Desktop/boot_info_script.sh: line 1579: [: 2.73495e+09: integer expression expected

Re: Input output error on read /dev/sda

Quote Originally Posted by psusi
View Post

AHCI is not a property of the drive; it is the native mode of the SATA controller.

Did you actually run the SMART long selftest? How about posting the actual SMART attributes? Also check your dmesg for errors.

The attachment provide the output of demsg command. As for as AHCI is concerned my BIOS donot provide option for selecting the particular mode. Yes i have done that self test and I will post the result of smart test soon

Thank you for help

Last edited by Manuj19; June 9th, 2011 at 07:22 PM.

Re: Input output error on read /dev/sda

ok, you got me down to guessing and i got just two. testdisk and one i have yet to try

don’t know if you will get results or not. good luck

Re: Input output error on read /dev/sda

It looks like the controller is boned. Do you have another computer you can try the drive in?

Re: Input output error on read /dev/sda

Quote Originally Posted by psusi
View Post

It looks like the controller is boned. Do you have another computer you can try the drive in?

Unfortunately I don’t have another computer
but here is attached SMART test results

Источник

fdisk works on disks, not partitions. On Linux, a disk is referred to as e.g. /dev/sdb, whereas the partitions on it are referred to as /dev/sdb1, /dev/sdb2 etc. Note that old-style (/dev/[hs]d?, /dev/[hs]d??) partition specifiers always end with a digit, whereas disk specifiers always end with a letter.

If you just format the disk (no bad blocks checking etc.), then a format time of a few seconds is not entirely unreasonable. All you did was write the initial file system metadata structures to disk, and while I don’t have any exact numbers to cite, those are fairly small, and USB is pretty fast for writing such relatively small amounts of data. If you didn’t get any errors, the format process probably did its thing.

The first thing you should do is run fdisk on the proper device. In your case, it sounds like that will be sudo fdisk /dev/sdb, but note that in some cases the device name can change with time. I recommend using one of the entries in /dev/disk/by-id instead, as those will not change. You can see what the disk shows up with there by running, immediately before you connect the disk:

diff <(ls /dev/disk/by-id) <(sleep 15; ls /dev/disk/by-id)

This will show the differences in directory content between the two executions of ls, which will be spaced 15 seconds apart thanks to the sleep invocation in the second input pipe. 15 seconds should give the kernel enough time to identify the disk and let udev create the appropriate device nodes. If it doesn’t show any differences (empty output), unplug the disk and try it again increasing the delay. You will see both partition devices (ending with -part followed by a number and possibly @) and disk devices (without the -part part). If the file names do end with @, disregard that character; it’s a ls output artefact.

Once you have partition(s) properly in place, you can make a file system on it/them. For example, sudo mkfs.ext4 -v /dev/disk/by-id/xxxxx-Passport-XXXXXXX-part1. The -v turns on extra output («v» for verbose) which will give you an idea of whether the file system is created successfully.

After that, the disk should be perfectly usable.

Источник

Сообщения без ответов | Активные темы

Автор Сообщение

Заголовок сообщения: DNS-323 + DEBIAN

СообщениеДобавлено: Сб окт 02, 2010 20:59 

Не в сети



Зарегистрирован: Пн ноя 02, 2009 12:06
Сообщений: 17

Установка, настройка , пользование.

Вот хотел узнать пару вопросов по этой теме:

Установка естественно описана чуть ли не по всему нету

Но интересуют такие вопросы:

1) Возможен ли откат на оригинальную прошивку ?

2) Какая скорость копирования и производительность в сравнение с оригинальной?

3)Решена ли проблема с вентиляторами и светодиодами ?

4) если «я» «перемудрю» с дебианом спасет ли меня кнопка «RESET» ?? Если нет то что делать в таком случае ??

Тему создал специально для обсуждения этих вопросов на которые я ответа не нашол, ну и с уклоном на рускоязычного пользователя скажем так для написания FAQ для НАС.
Вернуться наверх

Профиль  

Isildur

Заголовок сообщения:

СообщениеДобавлено: Сб окт 02, 2010 22:04 

Не в сети



Зарегистрирован: Пн янв 12, 2009 20:37
Сообщений: 1012
Откуда: Киев, Украина

1) Возможен.

2) Общая производительность немного меньше из-за использования необрезанных библиотек, но с другой стороны — меньше ограничений.

3) Давно уже. Ставим lm-sensors и пользуемся pwmconfig и fancontrol.

4) Ресет ничего не сделает, нужен com или jtag кабель.

Советую

http://www.cyrius.com/debian/orion/d-li … index.html
Вернуться наверх

Профиль  

minoga1

Заголовок сообщения:

СообщениеДобавлено: Сб окт 02, 2010 23:14 

Не в сети



Зарегистрирован: Пн ноя 02, 2009 12:06
Сообщений: 17

Isildur писал(а):

1) Возможен.
2) Общая производительность немного меньше из-за использования необрезанных библиотек, но с другой стороны — меньше ограничений.
3) Давно уже. Ставим lm-sensors и пользуемся pwmconfig и fancontrol.
4) Ресет ничего не сделает, нужен com или jtag кабель.
Советую

http://www.cyrius.com/debian/orion/d-li … index.html

1) ну как я понимаю надо спаять СОМ кабель , скачать утелиту «dns323-firmware-tools (version 0.3 or higher)» распаковать такой командой

splitdns323fw -k uKernel -i uRamdisk vendor-firmware

причем под линуксом

мы извлечем 2 имеджа, потом записываем их в девайс

cat uKernel > /dev/mtdblock2

cat uRamdisk > /dev/mtdblock3

ну и соответственно перезагружаем ??? (это если правельно понял)

2) к примеру при файловой системе ЕХТ3 скорость записи и чтения при оригинальной прошивке соствила 10-11 мбс

3) если вам не трудно то не могли бы ли вы расписать этот процесс(на сколько мне понятно надо обновится на «2.6.32 based kernel» )

4)»Советую

http://www.cyrius.com/debian/orion/d-li … index.html

» от туда и начинал искать(так сказать первоисточник) :)

по поводу востановления не очень понял последовательность :? с английским не очень силен но стараюсь…
Вернуться наверх

Профиль  

Isildur

Заголовок сообщения:

СообщениеДобавлено: Сб окт 02, 2010 23:54 

Не в сети



Зарегистрирован: Пн янв 12, 2009 20:37
Сообщений: 1012
Откуда: Киев, Украина

1) Кабель тут нужен только если дебиан сломался. В рабочем состоянии эти операции выполняются без кабеля на самой коробке.

2) При выключенном transmission имею скорости 14-15 по самбе, при включенном — 6-8.

3) Ставим дебиан, переключаемся на тестовую ветку в репозиториях (на свой страх и риск), свежее ядро придет из офф источников (выполнять операцию отсюда не нужно), ставим lm-sensors, запускаем pwmconfig и проходим стандартный тест для создания конфига, запускаем сервис fancontrol и смотрим, чтобы он был в автозагрузке.

4) Для восстановления нужно иметь рабочий кабель в первую очередь, а уж само восстановление там по шагам описано.
Вернуться наверх

Профиль  

minoga1

Заголовок сообщения:

СообщениеДобавлено: Вс окт 03, 2010 15:34 

Не в сети



Зарегистрирован: Пн ноя 02, 2009 12:06
Сообщений: 17

Цитата:

ставим lm-sensors, запускаем pwmconfig и проходим стандартный тест для создания конфига

хм мне пишет

/usr/sbin/pwmconfig: No sensors found! (modprobe sensor modules?)
Вернуться наверх

Профиль  

Isildur

Заголовок сообщения:

СообщениеДобавлено: Вс окт 03, 2010 21:39 

Не в сети



Зарегистрирован: Пн янв 12, 2009 20:37
Сообщений: 1012
Откуда: Киев, Украина

А на тестовую ветку перешел и обновил систему?
Вернуться наверх

Профиль  

minoga1

Заголовок сообщения:

СообщениеДобавлено: Вс окт 03, 2010 22:38 

Не в сети



Зарегистрирован: Пн ноя 02, 2009 12:06
Сообщений: 17
Вернуться наверх

Профиль  

minoga1

Заголовок сообщения:

СообщениеДобавлено: Пн окт 04, 2010 19:50 

Не в сети



Зарегистрирован: Пн ноя 02, 2009 12:06
Сообщений: 17

)) да пока я в линуксе не силен …. то с торентом то с самбой проблемы..

откатился назад все ок так как нужен в работе ДНС-323

Буду на каком то ноуте тренироватся с линуксом
Вернуться наверх

Профиль  

kostasoft

Заголовок сообщения: Re: DNS-323 + DEBIAN

СообщениеДобавлено: Пн окт 17, 2016 00:39 

Не в сети



Зарегистрирован: Ср фев 27, 2008 17:25
Сообщений: 85
Откуда: Санкт-Петербург

Господа, реанимирую тему:
Девайс: DNS-323 A1.
Залил netboot.ini
Зашел на девайс по SSH. Прошел все до разбивки диска на партишены.
Но не сохраняет изменения на диске (скриншоты прилагаю)
Если установить fdisk и parted (при конфигурации installer-a), то они выдают следующее:

Код:

fdisk -l /dev/sda
fdisk: cannot open /dev/sda: Input/output error

Код:

parted /dev/sda

GNU Parted 3.2
Using /dev/sda
Welcome to GNU Parted! Type ‘help’ to view a list of commands.

(parted) print
print
Error: /dev/sda: unrecognised disk label
Model: ATA ST380815AS (scsi)
Disk /dev/sda: 80.0GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:

(parted) mklabel msdos
mklabel msdos
Error: Input/output error during read on /dev/sda
Retry/Ignore/Cancel?

Диски пробовал разные, и на 2 Tb, и на 80 Gb

Вот что в логе после выполнения fdisk:

Код:

~ # fdisk -l /dev/sda
fdisk: cannot open /dev/sda: Input/output error

~ # tail /var/log/syslog
Oct 17 10:01:46 kernel: [  679.104549] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Oct 17 10:01:46 kernel: [  679.136634] ata1.00: configured for UDMA/33
Oct 17 10:01:46 kernel: [  679.136725] ata1: EH complete
Oct 17 10:01:46 kernel: [  679.144631] ata1.00: exception Emask 0x10 SAct 0x80 SErr 0x0 action 0x6 frozen
Oct 17 10:01:46 kernel: [  679.144666] ata1.00: edma_err_cause=00000280 pp_flags=00000003, parity error, EDMA self-disable
Oct 17 10:01:46 kernel: [  679.144699] ata1.00: failed command: READ FPDMA QUEUED
Oct 17 10:01:46 kernel: [  679.144762] ata1.00: cmd 60/08:38:00:00:00/00:00:00:00:00/40 tag 7 ncq 4096 in
Oct 17 10:01:46 kernel: [  679.144762]          res 50/00:ff:ff:ff:ff/00:ff:ff:ff:ff/ff Emask 0x10 (ATA bus error)
Oct 17 10:01:46 kernel: [  679.144792] ata1.00: status: { DRDY }
Oct 17 10:01:46 kernel: [  679.144835] ata1: hard resetting link

~ # fdisk -l /dev/sdb
fdisk: cannot open /dev/sdb: Input/output error

~ # tail /var/log/syslog
Oct 17 10:09:45 kernel: [ 1158.288614] ata2.00: configured for UDMA/33
Oct 17 10:09:45 kernel: [ 1158.288703] ata2: EH complete
Oct 17 10:09:45 kernel: [ 1158.296632] ata2.00: exception Emask 0x10 SAct 0x20000 SErr 0x0 action 0x6 frozen
Oct 17 10:09:45 kernel: [ 1158.296667] ata2.00: edma_err_cause=00000280 pp_flags=00000003, parity error, EDMA self-disable
Oct 17 10:09:45 kernel: [ 1158.296703] ata2.00: failed command: READ FPDMA QUEUED
Oct 17 10:09:45 kernel: [ 1158.296767] ata2.00: cmd 60/08:88:08:00:00/00:00:00:00:00/40 tag 17 ncq 4096 in
Oct 17 10:09:45 kernel: [ 1158.296767]          res 50/00:ff:ff:ff:ff/00:ff:ff:ff:ff/ff Emask 0x10 (ATA bus error)
Oct 17 10:09:45 kernel: [ 1158.296798] ata2.00: status: { DRDY }
Oct 17 10:09:45 kernel: [ 1158.296835] ata2: hard resetting link
Oct 17 10:09:46 kernel: [ 1158.772555] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

_________________

http://kostasoft.com

— Наш софт!
Вернуться наверх

Профиль  

minoga1

Заголовок сообщения: Re: DNS-323 + DEBIAN

СообщениеДобавлено: Пн окт 17, 2016 16:49 

Не в сети



Зарегистрирован: Пн ноя 02, 2009 12:06
Сообщений: 17
Вернуться наверх

Профиль  

kostasoft

Заголовок сообщения: Re: DNS-323 + DEBIAN

СообщениеДобавлено: Пн окт 17, 2016 17:24 

Не в сети



Зарегистрирован: Ср фев 27, 2008 17:25
Сообщений: 85
Откуда: Санкт-Петербург

Да, ALT-F запустил.
Но мне нужно на NAS-е установить и запустить Node.JS
Я не встречал, как это сделать, используя ffp.

ЗЫ: Нашел вот тут интересный абзац:

Цитата:

And the 3.10 kernel in wheeze-backports and 3.11 kernel in Debian Testing (Jessie), have yet another error: they get stuck in a loop trying to talk to the hard drives, receiving errors (or messages they can’t parse) from the hard drives. So it really works best to stick with kernel 2.6.32.

По-моему, как раз моя проблема.
Но где ж теперь взять старую версию 2.6.32 инсталлера (netboot.img)?

_________________

http://kostasoft.com

— Наш софт!
Вернуться наверх

Профиль  

Кто сейчас на форуме

Сейчас этот форум просматривают: нет зарегистрированных пользователей и гости: 1

Вы не можете начинать темы
Вы не можете отвечать на сообщения
Вы не можете редактировать свои сообщения
Вы не можете удалять свои сообщения
Вы не можете добавлять вложения

Источник

batchen

Posts: 25
Joined: 2016/11/28 09:09:47

[SOLVED]Device for PV not found or rejected by a filter

Hi,

using :
CentOS Linux release 7.1.1503 (Core) x86_64 virtual machin

i had to take out one of our physical disks so i used this steps :
the disk was connected to VG allready .so :
# Add a new disk so i can move the remaining data of the disk im going to remove and then moving it :

#after all the info was moved removing /dev/sda from this VG :

now instead of removing the PV first befor removing the sda1 i did the opossite and made an error..

Code: Select all

#pvremove  /dev/sda1
No PV label found on /dev/sda

and this error while doing pvdisplay :

Code: Select all

  WARNING: Device for PV NFwK98-81XP-xcD6-keZ4-k8IF-CeSs-yCwKur not found or rejected by a filter.

and blkid returning

now i need to remove this disk but i dont know if it safe like this. what can i do ?

Last edited by batchen on 2017/02/14 11:40:14, edited 1 time in total.

batchen

Posts: 25
Joined: 2016/11/28 09:09:47

Re: Device for PV not found or rejected by a filter

Post

by batchen » 2017/02/14 11:40:03

Well, i found the solution myself.

all i needed to do is recreate the PV from the start so this was my steps :

Code: Select all

#fdisk /dev/sda
-n
-p
-1
-enter
-enter
-t
-8e
-w

and then it was safe to remove the virtual CD
after i removed the cd i had the errors when i did

Code: Select all

fdisk: cannot open /dev/sda: Input/output error

i over come them by :

Code: Select all

echo 1 > /sys/class/scsi_device/1:0:0:0/device/rescan 
echo 1 > /sys/class/scsi_device/2:0:2:0/device/rescan 
echo 1 > /sys/class/scsi_device/2:0:0:0/device/rescan

(and so on.. you need to do it to all /sys/class/scsi_device/* device there.. )

and thats it :)

Источник

Hi guys.
I encountered a filesystem issue after an unclean shutdown. I can’t mount my /dev/sda3.

I have booted from Live-USB and tried fsck but it gave me the following error:

fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
fsck.ext2: input/output error while trying to open /dev/sda3

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

I then tried e2fsck -b to use alt superblocks, and all of them gave me the following in the end:

Error writing block 1 (input/output error).  Ignore error? yes

Here is the output of fdisk -l /dev/sda:

Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: TOSHIBA MQ01ABD1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: A58C9090-719B-4126-B7D2-6D9980C7EE5C

Device         Start        End    Sectors  Size Type
/dev/sda1       2048    1050623    1048576  512M EFI System
/dev/sda2    1050624  126877695  125827072   60G Linux filesystem
/dev/sda3  126877696 1953523711 1826646016  871G Linux filesystem

smartctl -a /dev/sda3:

smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.9.200-antix.1-amd64-smp] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 2.5" HDD MQ01ABD...
Device Model:     TOSHIBA MQ01ABD100
Serial Number:    66PPCA2JT
LU WWN Device Id: 5 000039 713f076c5
Firmware Version: AX0P3D
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon Feb 24 16:59:15 2020 CST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(  120) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 241) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 128
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   050    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   100   100   001    Pre-fail  Always       -       1747
  5 Reallocated_Sector_Ct   0x0033   100   100   050    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   066   066   000    Old_age   Always       -       13773
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       1797
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       160
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       60
193 Load_Cycle_Count        0x0032   089   089   000    Old_age   Always       -       114357
194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       30 (Min/Max 11/48)
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0032   074   074   000    Old_age   Always       -       10780
241 Total_LBAs_Written      0x0032   100   100   000    Old_age   Always       -       20878586044
242 Total_LBAs_Read         0x0032   100   100   000    Old_age   Always       -       26620931857
254 Free_Fall_Sensor        0x0032   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 2575 (device log contains only the most recent five errors)
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 2575 occurred at disk power-on lifetime: 13773 hours (573 days + 21 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
  -- -- -- -- -- -- --
  40 41 10 00 00 90 40  Error: UNC at LBA = 0x00900000 = 9437184

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 10 00 00 90 40 00      06:49:14.650  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      06:49:14.650  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00      06:49:14.649  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      06:49:14.649  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      06:49:14.648  SET FEATURES [Set transfer mode]

Error 2574 occurred at disk power-on lifetime: 13773 hours (573 days + 21 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
  -- -- -- -- -- -- --
  40 41 e0 00 00 90 40  Error: UNC at LBA = 0x00900000 = 9437184

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 e0 00 00 90 40 00      06:49:10.863  READ FPDMA QUEUED
  60 08 d8 f0 67 70 40 00      06:49:10.863  READ FPDMA QUEUED
  60 08 70 80 67 70 40 00      06:49:10.838  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      06:49:10.829  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00      06:49:10.829  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 2573 occurred at disk power-on lifetime: 13773 hours (573 days + 21 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
  -- -- -- -- -- -- --
  40 41 c0 00 00 90 40  Error: UNC at LBA = 0x00900000 = 9437184

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 c0 00 00 90 40 00      06:49:07.051  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      06:49:07.050  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00      06:49:07.050  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      06:49:07.049  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      06:49:07.048  SET FEATURES [Set transfer mode]

Error 2572 occurred at disk power-on lifetime: 13773 hours (573 days + 21 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
  -- -- -- -- -- -- --
  40 41 28 00 00 90 40  Error: UNC at LBA = 0x00900000 = 9437184

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 28 00 00 90 40 00      06:49:03.272  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      06:49:03.271  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00      06:49:03.271  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      06:49:03.270  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      06:49:03.270  SET FEATURES [Set transfer mode]

Error 2571 occurred at disk power-on lifetime: 13773 hours (573 days + 21 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
  -- -- -- -- -- -- --
  40 41 00 00 00 90 40  Error: UNC at LBA = 0x00900000 = 9437184

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 20 00 00 00 90 40 00      06:48:58.991  READ FPDMA QUEUED
  ea 00 00 00 00 00 a0 00      06:48:58.990  FLUSH CACHE EXT
  ef 10 02 00 00 00 a0 00      06:27:48.070  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00      06:27:48.069  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      06:27:48.069  IDENTIFY DEVICE

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     13772         -
# 2  Extended offline    Completed: read failure       00%     13771         6960152
# 3  Extended offline    Aborted by host               90%     13764         -
# 4  Short offline       Completed without error       00%     13762         -
# 5  Short offline       Aborted by host               90%       253         -
# 6  Short offline       Aborted by host               70%       253         -
# 7  Short offline       Aborted by host               90%       253         -
# 8  Short offline       Aborted by host               90%        10         -
# 9  Short offline       Aborted by host               90%        10         -
#10  Short offline       Aborted by host               90%         8         -
#11  Short offline       Aborted by host               90%         8         -
#12  Short offline       Completed without error       00%         8         -
#13  Short offline       Completed without error       00%         1         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

dmesg‘s output has errors as below:

[34627.265357] blk_update_request: I/O error, dev sda, sector 126877696
[34627.265363] Buffer I/O error on dev sda3, logical block 0, async page read

It seems like a terrible failing. Can anyone help me with this? Better without any lower-level data recovery techniques. Thanks very much!

Last edited by zoron (2020-02-25 01:02:39)

Источник

Понравилась статья? Поделить с друзьями:

Читайте также:

  • Fd termination status error
  • Fcs error count
  • Fcprimal exe системная ошибка
  • Fcp ошибка dongin thermo
  • Fco ошибка стиральной машины haier

    • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии