Error fsyncing closing dev sdb input output error

Страницы: [1] 2  Все   Вниз

0 Пользователей и 1 Гость просматривают эту тему.

Страницы: [1] 2  Все   Вверх

Hi,

i have an Asus UX32a, it came with 320GB HDD, and besides it has built-in disk for ExpressCache — Sandisk SSD i100 24GB.
as Laptop came with installed Windows, 24GB was used for ExpressCache. Two years ago I replaced HDD with SSD 256GB, and Installed Windows 10 directly on this disk. Installed Ubuntu 14 on 24GB built-in disk, but that time could not make dual boot and was using Windows 10 only. So, 24GB disk was not in use around 2 years.
Few days ago i wanted to install Ubuntu, but could not install on 24GB, and made a fresh install on 256GB disk, replaced Windows.

after i could not make dual boot (Windows on 256GB and Ubuntu on 24GB), Windows was not seeing the 24GB disk. Before that I remember i was using that inbuit disk for some VMs.

I would like to get this disk back alive and use it, would like to install Ubuntu on 24GB disk, pls guide me.

here are the some data:

$ sudo parted -l
Model: ATA TS256GSSD370 (scsi)
Disk /dev/sda: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 1049kB 512MB 511MB primary ext2 boot
2 513MB 256GB 256GB extended
5 513MB 256GB 256GB logical

Warning: Error fsyncing/closing /dev/sdb1: Input/output error
Retry/Ignore? i
Warning: Error fsyncing/closing /dev/sdb: Input/output error
Retry/Ignore? i
Model: ATA SanDisk SSD i100 (scsi)
Disk /dev/sdb: 24,0GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 24,0GB 24,0GB ntfs Basic data partition msftdata

Model: Linux device-mapper (crypt) (dm)
Disk /dev/mapper/cryptswap1: 6320MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:

Number Start End Size File system Flags
1 0,00B 6320MB 6320MB linux-swap(v1)

Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/ubuntu—vg-swap_1: 6321MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:

Number Start End Size File system Flags
1 0,00B 6321MB 6321MB linux-swap(v1)

Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/ubuntu—vg-root: 249GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:

Number Start End Size File system Flags
1 0,00B 249GB 249GB ext4

Error: /dev/mapper/sda5_crypt: unrecognised disk label
Model: Linux device-mapper (crypt) (dm)
Disk /dev/mapper/sda5_crypt: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:

Warning: Unable to open /dev/sr0 read-write (Read-only file system). /dev/sr0
has been opened read-only.
Model: Linux File-CD Gadget (scsi)
Disk /dev/sr0: 6089kB
Sector size (logical/physical): 512B/512B
Partition Table: mac
Disk Flags:

Number Start End Size File system Name Flags
1 512B 18,4kB 17,9kB MRKS
2 55,3kB 6089kB 6033kB hfs+ Toast 11.0.0 HFS+/Joliet Builde

$ sudo fdisk -lu
Disk /dev/sda: 238,5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xcb2a3748

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 999423 997376 487M 83 Linux
/dev/sda2 1001470 500117503 499116034 238G 5 Extended
/dev/sda5 1001472 500117503 499116032 238G 83 Linux

Disk /dev/sdb: 22,4 GiB, 24015495168 bytes, 46905264 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: FB26DFA8-A671-4119-B025-8E50F918B275

Device Start End Sectors Size Type
/dev/sdb1 2048 46903295 46901248 22,4G Microsoft basic data

Disk /dev/mapper/sda5_crypt: 238 GiB, 255545311232 bytes, 499111936 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mapper/ubuntu—vg-root: 232,1 GiB, 249175212032 bytes, 486670336 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mapper/ubuntu—vg-swap_1: 5,9 GiB, 6320816128 bytes, 12345344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mapper/cryptswap1: 5,9 GiB, 6320291840 bytes, 12344320 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

$ sudo dd if=/dev/zero of=/dev/sdb bs=512 count=1
1+0 records in
1+0 records out
512 bytes copied, 0,0704172 s, 7,3 kB/s

Проблема с 5-летним hdd Hitachi

После того, как в доме вырубился свет, ubuntu загрузился в initramfs. Загрузившись с лайв-флешки ubuntu, попытался смонтировать диск с помощью «disks», но не помогло.

лог «dmesg | tail»

Попытался восстановить суперблоки ext4 один за одним, но после каждого изменения система пишет

Поптка установки ubuntu:

восстановить из бекапа, если таковой имеется.

или скопировать по-блочно (например через ddrescue) на другой винт все что прочтется ( если оно вообще читается ) и там уже чинить.

пришло время платить оброк производителям hdd

то есть он совсем умер? Форматонуть согласен, критичной инфы там нет.

Битые сектора появились, чо.

Если ничего важного, пару раз полностью залить винт нулями.
Глядишь, битое отремаппится.

Ну или всякими MHDD/Victoria пройтись

Поставить удаленно диагноз — трудно. Хорошо бы смарт его посмотреть. Еще состояние БП может сказываться на работоспособность диска.

Но ошибки записи на современном десктопном диске обычно говорят о том, что диску пришел пушистый северный зверек.

GSmartControl выдаёт это

«smartctl -a /dev/sdX» был бы полезнее, но и так видно, что жизнь у него тяжелая.

2.5″ диск, почти 4 года работы,

1560 ошибок в журнале

1000 ч. назад самотестирование уже было неудачным.

Диск должен скоро умереть.

Вот такое от smartctl -a /dev/sda1

Этот хоть минимальному восстановлению подлежит?

Или завтра пора в магазин за новым hdd?

Не заметил в первый раз.

Восстанавливать 4-х летный ноутбучный винт нет смысла при условии, что на нем нет ценных данных.

Если диск сейчас ооочень нужен, то можно оставить неразмеченой часть диска с ошибками и а партицию создать на рабочей части диска, но проверка диска займет много времени и есть шанс, что во время такой проверки он умрет окончательно.

Источник

Новые HDD не работают

Всем привет.
Заменил на сервере 2 диска на новые, перед этим их отмонтировал. Новые харды у меня определились как sda, sdb
Вот вывод lsblk:

есть прога partprobe, помогает при добавлении дисков.

parted & partprobe в помощь

работать с терабайтниками лучше с ними

Ойёй, я проморгал что у тебя dmarid. Лучше бы тебе его вообще не использовать и создать нормальные md массивы.

Вот в этом и весь прикол, это досталось по наследству, что бы перенести систему на 2 новых харда, нужно их сначала инициализировать, но не получается

Заметил один факт, система, видимо думает, что 2 новых диска, должны работать со старым рейдом
https://pastebin.com/Nni2sJE1

прежде всего, надо в bios пометить эти диски как диски, а не членов raid. что, увы без перезагрузки не получится.

Удалил dm-3 и dm-1, теперь осталась ругань на /dev/sda,sdb. В любом случае это можно сделать на программном уровне, и не нужно будет делать ребут. Насколько я помню в bios можно только выключить raid целяком

Как-то возился с тем, чтобы просто сделать dd диска, котрый был частью fake-raid, не помню точно, то ли пришлось в биосе отключать возможности raid, толи вообще запускаться на материнке его не умеющей. При загрузке dmraid вцепляется в диски и не отдаёт их никакими опциями и командами.

Ну есть вариант, поставить старые диски обратно, сделать dmraid -E -r /dev/sda,sdb после чего поставить новые диски. Хз или поможет

Можно попробовать. На всякий случай стоит обложиться бэкапами.

инфа на этих 2х хардах не представляет ценности

нужно потереть метаданные за которые цепляется dmraid

Вставил новые харды, только с упаковки, на них метаданных нет. Или нужно потереть на старых?

По идее в bios должна быть конфигуратор разделов этого fakeraid’а, который обычно вызывается отдельной комбинацией клавиш.

В любом случае это можно сделать на программном уровне, и не нужно будет делать ребут.

Тут бы главное, чтобы после ваших «на программном уровне» ребут прошёл успешно, а то bios решит, что raid’а нет и всё.

Тут бы главное, чтобы после ваших «на программном уровне» ребут прошёл успешно, а то bios решит, что raid’а нет и всё.

Это не системный раздел. По логике вещей, не должно задеть.

Вставил 2 старых диска обратно, оно их определило как mdraid и пошел ребилд.

если у Вас новые диски большего объема, сделайте clonezill-ой копию диска. а после растяните партиции и файловые системы

Изначально, новые диски у меня не отвечают ни на запись ни на форматирование

Как вариант
Оставьте два диска старый и новый и загрузитесь с livecd c clonezzila .
при загрузке c clonezzila ядра linux возможно потребуется параметр raid=noautodetect или запретить загрузку модуля dmraid или какой там (на этапе загрузки загрузчика GRUB по моему) — чтобы он не схватил диски под себя.
Дальше делаете клонирование старого диска на новый.

Я такое пробовал. BIOS похоже к серийнику привязывается или ещё какому-то непонятному id.

не пойму, причем тут биос? bios ядром linux не рулит. bios raid контроллера?
ну тогда диски вставлять в десктоп без рейд контроллера и вперед, отключить raid контроллер в bios.

Короче как оказались, новые диски — битые, отвез в СЦ. dmraid развалил, был md, md развалил. Другие диски работают.

При таких вводных надо было это проверять в первую очередь. Ни фейковый, ни реальный рейд не должны приводить к тому, что диски просто нельзя прочитать (Input/output error).

Диски только распечатал, всего было 4 шт, 2 шт оказались битыми

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

Unable to install Mint fsyncing error

Unable to install Mint fsyncing error

Post by Marsu69 » Sun Feb 07, 2016 6:08 am

First of all I would like to say that English is not my native langage so sorry for any mistakes.
Second : I’m a total newbie to linux. This is my first try installing a distro and it goes wrong

So here’s my problem :
I’ve downloaded the Mint 17.3 Cinamon x64 edition to install it as dual boot with my windows 10.
I’ve put the iso on a USB flashdrive with Universal USB Installer (I’ve checked the MD5 prior to install)

When the computer boot to the USB flashdrive, it show me the «Automatic boot in 10, 9, 8. seconds»
Then the screen goes grey and it shows «ACPI PCC probe failed»
After that some other errors appears (didn’t have the time to write all down)
sda No Caching mod
Assuming caching (or something like this)
sdb : same
ata6.01 Exception Emask
ata6.01 failed command read DMA
Then the logo mint appear in full screen for some minutes
Juste before entering the desktop, it shows me somme other errors, i’ve just have the time to read SRST Failed

After that the desktop of the live session appear.
So i double clic on the «install mint», it ask me for the langage selection, then it let me choose between «Install mint» and «something else».
As I want to keep my windows I choose «Something else» and then it says «fsyncing/closing /dev /sda : input / output error
If I hit retry the popup comes again and again.
If I hit ignore, it show the entire disk without any partition.

So I have try to run gparted and here’s the log of the terminal :

FYI actually :
sda : Look to be the drive with windows (a 160 Go HDD)
sdb : My backup drive (1.5 To)
sdc : It looks like it»s my USB drive
sdd : It looks like my external HDD (2To)

Here’s my rig in case it helps :
Motherboard : Asus P5Q Premium
Proc : Intel Core 2 quad 9650
Ram : 4 * 1 Go DDR2
Graphic Card : Nvidia GTX 770

I hope i’ve put the essential information but feel free to ask for something else.

Thank you verry much for your time.

Re: Unable to install Mint fsyncing error

Post by Pierre » Sun Feb 07, 2016 6:18 am

have a look at this tutorial:
http://forums.linuxmint.com/viewtopic.php?f=42&t=163126
it’s written for win-8x but does also apply for win-10.

one other thing to try — the 2nd item on the boot menu:
— is ‘compatibility mode’ or reduced video mode — which may causing some video issues.

also2: did you turn off the windows ‘fast start’ feature:
http://www.tenforums.com/tutorials/4189 . -10-a.html
finally — disconnect any other HDDs that are connected, while you attempt any installation.

Re: Unable to install Mint fsyncing error

Post by Marsu69 » Sun Feb 07, 2016 6:28 am

Thanks for the tutorial.

I’m having issues with the Boot in UEFI mode. My motherboard is an old one. It has no UEFI on it only old BIOS.
So is this mandatory to have mint installed ?

Re: Unable to install Mint fsyncing error

Post by Laurent85 » Sun Feb 07, 2016 6:58 am

You should check the drives are properly attached. This might also indicate a failing drive cable or a drive health issue.
From the Live usb install smartmontools, open a terminal:

Источник

error fsyncing/closing/dev/sda: input/output error — hdd not detected in BIOS after this error

So here’s what happened: I created a ubuntu gnome bootable usb using unetbootin and selected to replace my windows and install a fresh copy of ubuntu. But as soon as ubuntu finished cleaning up windows and formatting i got the error error fsyncing/closing/dev/sda: input/output error

I had no choice so I restarted my system and now my HDD is not detected in BIOS and also not in ubuntu live boot mode.

I have a Sony vaio.

Any ideas how I can fix this?

3 Answers 3

I/O errors usually (but not always) indicate failing hardware. My guess is that your disk (or some other disk-related component, like a cable or your motherboard’s disk controller circuitry) was on its last legs, and the «exercise» involved in installing Ubuntu caused it to fail. You don’t say what prompted you to install Ubuntu, but if you were having problems with Windows reliability, it’s possible that this was an earlier symptom of the problem.

You might try unplugging your disk (from both ends of the cable if it’s a desktop system) and plugging it back in again. You could also try running a SMART test from an Ubuntu live CD — but if the disk isn’t detected by your firmware, it might not even show up in Ubuntu, which would make such a test impossible.

If you’ve got a spare disk, you could try using it instead. If it works, then you can pretty much conclude that your old disk is dead. If the replacement disk fails, too, then chances are the problem is with your computer motherboard’s circuitry.

Источник

Thread: Cannot find disk: Error fsyncing/closing /dev/sda: Input/output error

Thread Tools

Display

Cannot find disk: Error fsyncing/closing /dev/sda: Input/output error

Hey all, attempting to install ubuntu on a box which formerly had arch, and running into this issue. Hoping that I can find an OS which will recognize /dev/sda as my drive and install there.

A quick diagnosis:

The disk is not appearing where I think it should:
* Gparted, when launched from a usb stick, only shows /dev/sdc
* sudo fdisk -l shows only /dev/sdc, /dev/sdc1, and /dev/loop0
* df -h shows udev tmpfs, /dev/sdc1, /dev/loop0, overlay, and several tmpfs

/dev/sdc is my usb stick:
* udevadm info —query=all /dev/sdc shows that /dev/sdc is DEVLINKS=[. ]Lexar_USB_Flash_Drive[. ]

Yet /dev/sda still exists
* cat /proc/partitions shows sda, sda1, sda2, sda3, sdc, and loop0
* sudo parted /dev/sda unit s print gives the error in the title:
> Warning: Error fsyncing/closing /dev/sda1: Input/output error
> Warning: Error fsyncing/closing /dev/sda2: Input/output error
> Warning: Error fsyncing/closing /dev/sda3: Input/output error
>Error: /dev/sda: unrecognized disk label
>Model: ATA SATA SSD (scsi)
>Disk: /dev/sda: 62533296s
>Sector size (logical/physical): 512B/512B
>Partition Table: unknown

FWIW, when I try to install ubuntu from a live flash drive, I get the same «Input/output error» with an option to retry.

Any help appreciated! Is my SSD (/dev/sda) just hosed? Is there another disk reformat util you think I should try running?

Last edited by bwindsor22; September 11th, 2021 at 05:03 PM .

Re: Cannot find disk: Error fsyncing/closing /dev/sda: Input/output error

Also, a quick summary of what I’ve tried:
* Install ubuntu from flash drive —> doesn’t recognize /dev/sda
* Run gparted from flash drive [debian based] —> doesn’t recognize /dev/sda, «input/output error» when running some commands
* Run systemrescue from flash drive —> launches and shows a desktop, but still no /dev/sda in df -h, similar commands. Running «gparted» from the systemrescue boot gives «Error fsyncing/closing /dev/sda1: Input/output error»

Last edited by bwindsor22; September 11th, 2021 at 05:02 PM .

Re: Cannot find disk: Error fsyncing/closing /dev/sda: Input/output error

Update 2: «sudo shred -v /dev/sda» gives the same «Input/output error»

Re: Cannot find disk: Error fsyncing/closing /dev/sda: Input/output error

It’s not looking very fruitful right now.

Anyway let’s crack on.

Are you using an Ubuntu live session?

What does Disks (gnome-disk-utility) show?

Alternatively via a terminal:-

Re: Cannot find disk: Error fsyncing/closing /dev/sda: Input/output error

Re: Cannot find disk: Error fsyncing/closing /dev/sda: Input/output error

initial gdisk attempt below

untu@ubuntu:

$ sudo gdisk /dev/sda
GPT fdisk (gdisk) version 1.0.5

Warning! Read error 5; strange behavior now likely!
Warning! Read error 5; strange behavior now likely!
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present

Creating new GPT entries in memory.

Command (? for help):

Command (? for help): ?
b back up GPT data to a file
c change a partition’s name
d delete a partition
i show detailed information on a partition
l list known partition types
n add a new partition
o create a new empty GUID partition table (GPT)
p print the partition table
q quit without saving changes
r recovery and transformation options (experts only)
s sort partitions
t change a partition’s type code
v verify disk
w write table to disk and exit
x extra functionality (experts only)
? print this menu

Command (? for help): v

No problems found. 62533229 free sectors (29.8 GiB) available in 1
segments, the largest of which is 62533229 (29.8 GiB) in size.

Command (? for help): p
Disk /dev/sda: 62533296 sectors, 29.8 GiB
Model: SATA SSD
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 1960C385-E122-43CF-ACCF-41BF9AA0F136
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 62533262
Partitions will be aligned on 2048-sector boundaries
Total free space is 62533229 sectors (29.8 GiB)

Number Start (sector) End (sector) Size Code Name

Last edited by bwindsor22; September 11th, 2021 at 10:31 PM .

Re: Cannot find disk: Error fsyncing/closing /dev/sda: Input/output error

Command (? for help): n
Partition number (1-128, default 1): 1
First sector (34-62533262, default = 2048) or <+->size: +
Last sector (2048-62533262, default = 62533262) or <+->size:
Current type is 8300 (Linux filesystem)
Hex code or GUID (L to show codes, Enter = 8300): 8303
Changed type of partition to ‘Linux x86 root (/)’

Command (? for help): w

Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/sda.
Unable to save backup partition table! Perhaps the ‘e’ option on the experts’
menu will resolve this problem.
Warning! An error was reported when writing the partition table! This error
MIGHT be harmless, or the disk might be damaged! Checking it is advisable.
Command (? for help): v

No problems found. 2014 free sectors (1007.0 KiB) available in 1
segments, the largest of which is 2014 (1007.0 KiB) in size.

Re: Cannot find disk: Error fsyncing/closing /dev/sda: Input/output error

disk now looks different in «Disk», but reformat fails

Last edited by bwindsor22; September 11th, 2021 at 10:31 PM .

Re: Cannot find disk: Error fsyncing/closing /dev/sda: Input/output error

yes, on Ubuntu booted from flash drive now, was on systemrescue previously

Re: Cannot find disk: Error fsyncing/closing /dev/sda: Input/output error

After the above, I exited gdisk, and re-ran, seeing the same error. Write appears to fail, and when I re-run gdisk, I don’t see any partitions.

$ sudo gdisk /dev/sda
GPT fdisk (gdisk) version 1.0.5

Warning! Read error 5; strange behavior now likely!
Warning! Read error 5; strange behavior now likely!
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present

Creating new GPT entries in memory.

Command (? for help): ?
b back up GPT data to a file
c change a partition’s name
d delete a partition
i show detailed information on a partition
l list known partition types
n add a new partition
o create a new empty GUID partition table (GPT)
p print the partition table
q quit without saving changes
r recovery and transformation options (experts only)
s sort partitions
t change a partition’s type code
v verify disk
w write table to disk and exit
x extra functionality (experts only)
? print this menu

Command (? for help): n
Partition number (1-128, default 1): 1
First sector (34-62533262, default = 2048) or <+->size:
Last sector (2048-62533262, default = 62533262) or <+->size:
Current type is 8300 (Linux filesystem)
Hex code or GUID (L to show codes, Enter = 8300): 8300
Changed type of partition to ‘Linux filesystem’

Command (? for help): w

Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/sda.
Unable to save backup partition table! Perhaps the ‘e’ option on the experts’
menu will resolve this problem.
Warning! An error was reported when writing the partition table! This error
MIGHT be harmless, or the disk might be damaged! Checking it is advisable.

Command (? for help): p
Disk /dev/sda: 62533296 sectors, 29.8 GiB
Model: SATA SSD
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 572BD20F-57B3-478A-B745-846E517F9333
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 62533262
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Number Start (sector) End (sector) Size Code Name
1 2048 62533262 29.8 GiB 8300 Linux filesystem

Command (? for help): i
Using 1
Partition GUID code: 0FC63DAF-8483-4772-8E79-3D69D8477DE4 (Linux filesystem)
Partition unique GUID: 9E2405B5-841A-4FD7-AF6F-D2D3FA222E25
First sector: 2048 (at 1024.0 KiB)
Last sector: 62533262 (at 29.8 GiB)
Partition size: 62531215 sectors (29.8 GiB)
Attribute flags: 0000000000000000
Partition name: ‘Linux filesystem’

Command (? for help): w

Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/sda.
Unable to save backup partition table! Perhaps the ‘e’ option on the experts’
menu will resolve this problem.
Warning! An error was reported when writing the partition table! This error
MIGHT be harmless, or the disk might be damaged! Checking it is advisable.

Command (? for help):
Command (? for help): ^C
ubuntu@ubuntu:

$ sudo gdisk /dev/sda
GPT fdisk (gdisk) version 1.0.5

Warning! Read error 5; strange behavior now likely!
Warning! Read error 5; strange behavior now likely!
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present

Creating new GPT entries in memory.

Command (? for help): i
No partitions

Источник

Hello everybody

First of all I would like to say that English is not my native langage so sorry for any mistakes.
Second : I’m a total newbie to linux. This is my first try installing a distro and it goes wrong

So here’s my problem :
I’ve downloaded the Mint 17.3 Cinamon x64 edition to install it as dual boot with my windows 10.
I’ve put the iso on a USB flashdrive with Universal USB Installer (I’ve checked the MD5 prior to install)

When the computer boot to the USB flashdrive, it show me the «Automatic boot in 10, 9, 8…. seconds»
Then the screen goes grey and it shows «ACPI PCC probe failed»
After that some other errors appears (didn’t have the time to write all down)
sda No Caching mod
Assuming caching (or something like this)
sdb : same
ata6.01 Exception Emask
ata6.01 failed command read DMA
Then the logo mint appear in full screen for some minutes
Juste before entering the desktop, it shows me somme other errors, i’ve just have the time to read SRST Failed

After that the desktop of the live session appear.
So i double clic on the «install mint», it ask me for the langage selection, then it let me choose between «Install mint» and «something else».
As I want to keep my windows I choose «Something else» and then it says «fsyncing/closing /dev /sda : input / output error
If I hit retry the popup comes again and again.
If I hit ignore, it show the entire disk without any partition.

So I have try to run gparted and here’s the log of the terminal :

mint@mint ~ $ sudo gparted
======================
libparted : 2.3
======================

(gpartedbin:8343): GLib-CRITICAL **: Source ID 7 was not found when attempting to remove it

(gpartedbin:8343): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it

(gpartedbin:8343): GLib-CRITICAL **: Source ID 26 was not found when attempting to remove it

(gpartedbin:8343): GLib-CRITICAL **: Source ID 25 was not found when attempting to remove it

(gpartedbin:8343): GLib-CRITICAL **: Source ID 322 was not found when attempting to remove it

(gpartedbin:8343): GLib-CRITICAL **: Source ID 321 was not found when attempting to remove it

(gpartedbin:8343): GLib-CRITICAL **: Source ID 325 was not found when attempting to remove it

(gpartedbin:8343): GLib-CRITICAL **: Source ID 324 was not found when attempting to remove it

(gpartedbin:8343): GLib-CRITICAL **: Source ID 328 was not found when attempting to remove it

(gpartedbin:8343): GLib-CRITICAL **: Source ID 327 was not found when attempting to remove it

(gpartedbin:8343): GLib-CRITICAL **: Source ID 332 was not found when attempting to remove it

(gpartedbin:8343): GLib-CRITICAL **: Source ID 331 was not found when attempting to remove it
Error fsyncing/closing /dev/sda: Input/output error
Error fsyncing/closing /dev/sdb: Input/output error
Input/output error during read on /dev/sda
Error fsyncing/closing /dev/sda: Input/output error
Input/output error during read on /dev/sdb
Error fsyncing/closing /dev/sdb: Input/output error
/dev/sda: unrecognised disk label
Error fsyncing/closing /dev/sda: Input/output error
/dev/sdb: unrecognised disk label
Error fsyncing/closing /dev/sdb: Input/output error

(gpartedbin:8343): GLib-CRITICAL **: Source ID 917 was not found when attempting to remove it

(gpartedbin:8343): GLib-CRITICAL **: Source ID 916 was not found when attempting to remove it

(gpartedbin:8343): GLib-CRITICAL **: Source ID 920 was not found when attempting to remove it

(gpartedbin:8343): GLib-CRITICAL **: Source ID 919 was not found when attempting to remove it

(gpartedbin:8343): GLib-CRITICAL **: Source ID 923 was not found when attempting to remove it

(gpartedbin:8343): GLib-CRITICAL **: Source ID 922 was not found when attempting to remove it

(gpartedbin:8343): GLib-CRITICAL **: Source ID 926 was not found when attempting to remove it

(gpartedbin:8343): GLib-CRITICAL **: Source ID 925 was not found when attempting to remove it

After some search on internet I’ve seen some ask to run gdisk, so i’ve done and here’s the log :

mint@mint ~ $ sudo gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.8

Warning! Read error 5; strange behavior now likely!
Warning! Read error 5; strange behavior now likely!
Partition table scan:
  MBR: not present
  BSD: not present
  APM: not present
  GPT: not present

Creating new GPT entries.
Disk /dev/sda: 312581808 sectors, 149.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): EDA679A0-47FD-4BE2-8BB7-665B464D5BC9
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 312581774
Partitions will be aligned on 2048-sector boundaries
Total free space is 312581741 sectors (149.1 GiB)

Number  Start (sector)    End (sector)  Size       Code  Name

Then I’ve seen som to try fixparts so i’ve donne :

mint@mint ~ $ sudo fixparts /dev/sda
FixParts 0.8.8

Loading MBR data from /dev/sda

Unable to read MBR data from '/dev/sda'! Exiting!

And finaly I’ve seen everyone need Fdisk to say what happened so here it is :

mint@mint ~ $ sudo fdisk -l

Disk /dev/sdc: 4037 MB, 4037017600 bytes
2 heads, 63 sectors/track, 62577 cylinders, total 7884800 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000e021e

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *          64     7884799     3942368    c  W95 FAT32 (LBA)

Disk /dev/sdd: 2000.4 GB, 2000396746752 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907024896 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00123d72

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1            2048  3907024895  1953511424    7  HPFS/NTFS/exFAT

FYI actually :
sda : Look to be the drive with windows (a 160 Go HDD)
sdb : My backup drive (1.5 To)
sdc : It looks like it»s my USB drive
sdd : It looks like my external HDD (2To)

Here’s my rig in case it helps :
Motherboard : Asus P5Q Premium
Proc : Intel Core 2 quad 9650
Ram : 4 * 1 Go DDR2
Graphic Card : Nvidia GTX 770

I hope i’ve put the essential information but feel free to ask for something else.

Thank you verry much for your time.

Marsu69

00:04:47.118  [2020-07-08 01:11:04.905343] iscsi.c:1455:iscsi_op_login_check_target: *WARNING*: target iqn.2016-06.io.spdk:Target3 not found
00:04:49.119  [2020-07-08 01:11:06.905979] iscsi.c:1455:iscsi_op_login_check_target: *WARNING*: target iqn.2016-06.io.spdk:Target3 not found
00:04:51.119  [2020-07-08 01:11:08.906607] iscsi.c:1455:iscsi_op_login_check_target: *WARNING*: target iqn.2016-06.io.spdk:Target3 not found
00:04:53.121  [2020-07-08 01:11:10.907949] iscsi.c:1455:iscsi_op_login_check_target: *WARNING*: target iqn.2016-06.io.spdk:Target3 not found
00:04:55.121  [2020-07-08 01:11:12.908713] iscsi.c:1455:iscsi_op_login_check_target: *WARNING*: target iqn.2016-06.io.spdk:Target3 not found
00:04:57.122  [2020-07-08 01:11:14.909480] iscsi.c:1455:iscsi_op_login_check_target: *WARNING*: target iqn.2016-06.io.spdk:Target3 not found
00:04:57.281  Warning: Error fsyncing/closing /dev/sdb: Input/output error
00:04:57.281  Error: Error opening /dev/sdb: No such device or address

00:04:57.283  ========== Backtrace start: ==========
00:04:57.283  
00:04:57.295  in ./test/iscsi_tgt/filesystem/filesystem.sh:74 -> main([])
00:04:57.295       ...
00:04:57.295     69  	mkdir -p /mnt/device
00:04:57.295     70  	
00:04:57.295     71  	dev=$(iscsiadm -m session -P 3 | grep "Attached scsi disk" | awk '{print $4}')
00:04:57.295     72  	
00:04:57.295     73  	waitforfile /dev/$dev
00:04:57.295  => 74  	parted -s /dev/$dev mklabel msdos
00:04:57.295     75  	parted -s /dev/$dev mkpart primary '0%' '100%'
00:04:57.295     76  	sleep 1
00:04:57.295     77  	
00:04:57.295     78  	function filesystem_test() {
00:04:57.295     79  		fstype=$1
00:04:57.295       ...
00:04:57.295  
00:04:57.295  ========== Backtrace end ==========