Input output error while writing out and closing file system - Исправление ошибок и поиск оптимальных решений проблем

Rava: Contributor; Posts: 4606; Joined: 11 Jan 2011, 02:46; Distribution: XFCE 5.0 x86_64 + 4.0 i586; Location: Forests of Germany

USB thumbdrive — mkfs.ext2: Input/output error while writing out and closing file system

mkfs.ext2: Input/output error while writing out and closing file system is not something one wants to hear.
My manual attempt using fdisk and mkfs.ext2:

Code: Select all

root@porteus:/# fdisk -l /dev/sdd
Disk /dev/sdd: 14.45 GiB, 15518924800 bytes, 30310400 sectors
Disk model: Alu Line        
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

root@porteus:/# fdisk /dev/sdd

Welcome to fdisk (util-linux 2.36.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Device does not contain a recognized partition table.
Created a new DOS disklabel with disk identifier 0xc24adb2a.

Command (m for help): p
Disk /dev/sdd: 14.45 GiB, 15518924800 bytes, 30310400 sectors
Disk model: Alu Line        
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: 0xjaddajadda

Command (m for help): n
Partition type
   p   primary (0 primary, 0 extended, 4 free)
   e   extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1): 
First sector (2048-30310399, default 2048): 
Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-30310399, default 30310399): 
 
Created a new partition 1 of type 'Linux' and of size 14.5 GiB.

Command (m for help): p
Disk /dev/sdd: 14.45 GiB, 15518924800 bytes, 30310400 sectors
Disk model: Alu Line        
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: 0xc24adb2a

Device     Boot Start      End  Sectors  Size Id Type
/dev/sdd1        2048 30310399 30308352 14.5G 83 Linux

Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

root@porteus:/# mkfs.ext2 /dev/sdd1
mke2fs 1.45.6 (20-Mar-2020)
Creating filesystem with 3788544 4k blocks and 948416 inodes
Filesystem UUID: b07a7ef5-93fc-4419-8a22-1ac6a2241696
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Allocating group tables: done                            
Writing inode tables: done                            
Writing superblocks and filesystem accounting information: mkfs.ext2: Input/output error while writing out and closing file system

gparted has similar issues, so here the GUI attempt

Code: Select all

Device:	/dev/sdd
Model:	Intenso Alu Line
Serial:	
Sector size:	512
Total sectors:	30310400
 
Heads:	255
Sectors/track:	2
Cylinders:	59432
 
Partition table:	msdos
 
Partition	Type	Start	End	Flags	Partition Name	File System	Label	Mount Point
/dev/sdd1	Primary	2048	30310399			unknown		

========================================
Format /dev/sdd1 as ext2  00:01:10    ( ERROR )
     	
calibrate /dev/sdd1  00:00:00    ( SUCCESS )
     	
path: /dev/sdd1 (partition)
start: 2048
end: 30310399
size: 30308352 (14.45 GiB)
clear old file system signatures in /dev/sdd1  00:00:10    ( SUCCESS )
     	
write 512.00 KiB of zeros at byte offset 0  00:00:00    ( SUCCESS )
write 4.00 KiB of zeros at byte offset 67108864  00:00:00    ( SUCCESS )
write 512.00 KiB of zeros at byte offset 15517351936  00:00:00    ( SUCCESS )
write 4.00 KiB of zeros at byte offset 15517810688  00:00:00    ( SUCCESS )
write 8.00 KiB of zeros at byte offset 15517868032  00:00:00    ( SUCCESS )
flush operating system cache of /dev/sdd  00:00:09    ( SUCCESS )
     	
libparted messages    ( INFO )
     	
Input/output error during write on /dev/sdd
set partition type on /dev/sdd1  00:01:00    ( SUCCESS )
     	
new partition type: ext2
libparted messages    ( INFO )
     	
Input/output error during write on /dev/sdd
create new ext2 file system  00:00:00    ( ERROR )
     	
mkfs.ext2 -F -L '' '/dev/sdd1'  00:00:00    ( ERROR )
     	
mke2fs 1.45.6 (20-Mar-2020)
/dev/sdd1: Read-only file system while setting up superblock

Read-only file system while previous operations have been successful?

What can be done to make the thumb drive useable? Using Linux tool, no Witless-OS currently available.

It was like this from the start, and silly me misplaced the receipt and I bought it when 16 GB (or more like 14.45 GB — 15518924800 can never be counted as 16 GB — even when using 1000×1000 units instead of 1024×1024) sticks have been much more expansive than they are now.

Cheers!
Yours Rava

Ed_P: Contributor; Posts: 7442; Joined: 06 Feb 2013, 22:12; Distribution: Cinnamon 5.0 ISO; Location: Western NY, USA

USB thumbdrive — mkfs.ext2: Input/output error while writing out and closing file system

Post#2

by Ed_P » 12 Jan 2021, 17:25

Can you try a different format? FAT for example.

Rava: Contributor; Posts: 4606; Joined: 11 Jan 2011, 02:46; Distribution: XFCE 5.0 x86_64 + 4.0 i586; Location: Forests of Germany

USB thumbdrive — mkfs.ext2: Input/output error while writing out and closing file system

Post#3

by Rava » 12 Jan 2021, 18:32

Silly me forgot adding that failed attempts in the past used Type b aka ‘W95 FAT32’. Everyone would always try FAT32 first, then maybe ext2 later.

So here what the fail looks like using FAT32

Code: Select all

root@porteus:/# fdisk /dev/sde

Welcome to fdisk (util-linux 2.36.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): p
Disk /dev/sde: 14.45 GiB, 15518924800 bytes, 30310400 sectors
Disk model: Alu Line        
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: 0xblablubb

Device     Boot Start      End  Sectors  Size Id Type
/dev/sde1        2048 30310399 30308352 14.5G 83 Linux

Command (m for help): t
Selected partition 1
Hex code or alias (type L to list all): b
Changed type of partition 'Linux' to 'W95 FAT32'.

Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

root@porteus:/# mkfs.vfat -F 32 /dev/sde1
mkfs.fat 4.1 (2017-01-24)
mkfs.vfat: unable to open /dev/sde1: Read-only file system
root@porteus:/# mkfs.fat -F 32 /dev/sde1
mkfs.fat 4.1 (2017-01-24)
mkfs.fat: unable to open /dev/sde1: Read-only file system

Seems mkfs.fat fails as much as mkfs.ext2 .

Removing and reinserting…

Code: Select all

Jan 12 19:17:47 porteus kernel: [288680.283166] usb 2-1.2.2: USB disconnect, device number 66
Jan 12 19:17:51 porteus kernel: [288683.931930] usb 2-1.2.2: new high-speed USB device number 67 using ehci-pci
Jan 12 19:17:51 porteus kernel: [288683.955855] usb 2-1.2.2: New USB device found, idVendor=058f, idProduct=6387, bcdDevice= 1.0b
Jan 12 19:17:51 porteus kernel: [288683.955863] usb 2-1.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 12 19:17:51 porteus kernel: [288683.955869] usb 2-1.2.2: Product: Intenso Alu Line
Jan 12 19:17:51 porteus kernel: [288683.955874] usb 2-1.2.2: Manufacturer: Alcor Tech
Jan 12 19:17:51 porteus kernel: [288683.955879] usb 2-1.2.2: SerialNumber: 13082800005231
Jan 12 19:17:51 porteus kernel: [288683.956499] usb-storage 2-1.2.2:1.0: USB Mass Storage device detected
Jan 12 19:17:51 porteus kernel: [288683.956893] scsi host9: usb-storage 2-1.2.2:1.0
Jan 12 19:17:51 porteus mtp-probe: checking bus 2, device 67: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2.2" 
Jan 12 19:17:51 porteus mtp-probe: bus: 2, device: 67 was not an MTP device 
Jan 12 19:17:52 porteus kernel: [288684.996421] scsi 9:0:0:0: Direct-Access     Intenso  Alu Line         8.07 PQ: 0 ANSI: 4
Jan 12 19:17:52 porteus kernel: [288684.998457] sd 9:0:0:0: [sde] 30310400 512-byte logical blocks: (15.5 GB/14.5 GiB)
Jan 12 19:17:52 porteus kernel: [288684.999682] sd 9:0:0:0: [sde] Write Protect is off
Jan 12 19:17:52 porteus kernel: [288685.000940] sd 9:0:0:0: [sde] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Jan 12 19:17:53 porteus kernel: [288685.616114] sd 9:0:0:0: [sde] Attached SCSI removable disk

/var/log/messages lines 810-821/821 (END)

See the

line?

Next try…

Code: Select all

root@porteus:/# fdisk -l /dev/sde
Disk /dev/sde: 14.45 GiB, 15518924800 bytes, 30310400 sectors
Disk model: Alu Line        
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

As you can see, all previous fdisk changes are nil.

Code: Select all

root@porteus:/# fdisk  /dev/sde

Welcome to fdisk (util-linux 2.36.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Device does not contain a recognized partition table.
Created a new DOS disklabel with disk identifier 0xbad505ca.

Command (m for help): p
Disk /dev/sde: 14.45 GiB, 15518924800 bytes, 30310400 sectors
Disk model: Alu Line        
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: 0xbad505ca

Command (m for help): n
Partition type
   p   primary (0 primary, 0 extended, 4 free)
   e   extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1): 
First sector (2048-30310399, default 2048): 
Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-30310399, default 30310399): 
 
Created a new partition 1 of type 'Linux' and of size 14.5 GiB.

Command (m for help): t
Selected partition 1
Hex code or alias (type L to list all): b
Changed type of partition 'Linux' to 'W95 FAT32'.

Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
/dev/sde: fsync device failed: Input/output error

No.

LOL at the newest disk identifier 0xbad — bad indeed.

Cheers!
Yours Rava

donald: Full of knowledge; Posts: 1975; Joined: 17 Jun 2013, 13:17; Distribution: Porteus 3.2.2 XFCE 32bit; Location: Germany

USB thumbdrive — mkfs.ext2: Input/output error while writing out and closing file system

Post#4

by donald » 13 Jan 2021, 02:00

I would dd the whole drive
dd if=/dev/zero of=/dev/sdX bs=1M
If no errors occur, format the drive using GParted.

Cheap fake from ebay?

beny: Full of knowledge; Posts: 1669; Joined: 02 Jan 2011, 11:33; Location: italy

USB thumbdrive — mkfs.ext2: Input/output error while writing out and closing file system

Post#5

by beny » 13 Jan 2021, 02:27

hi donald,also sandisk cruzer 128 giga with an arch on, read only system and no cheap fake sandisk tell us is read only system to preserve data inside but you can’t read the key so….trashcan

Kulle: Warlord; Posts: 503; Joined: 28 Jan 2017, 10:39; Distribution: v4.0 64bit Xfce; Location: Berlin

USB thumbdrive — mkfs.ext2: Input/output error while writing out and closing file system

Post#6

by Kulle » 13 Jan 2021, 08:56

Hi Rava,
mkfs.vfat: unable to open /dev/sde1: Read-only file system
I also had this mistake once

Remedy:
On Windows with diskpart.exe:

list disk
select disk …
Be careful, dial the correct number!!
attributes disk clear readonly
clean

And further (if you want to format a partition with fat32)
create partition primary
active
format fs=fat32 label=»…» quick override
exit

Rava: Contributor; Posts: 4606; Joined: 11 Jan 2011, 02:46; Distribution: XFCE 5.0 x86_64 + 4.0 i586; Location: Forests of Germany

USB thumbdrive — mkfs.ext2: Input/output error while writing out and closing file system

Post#7

by Rava » 13 Jan 2021, 23:01

Kulle wrote: ↑

13 Jan 2021, 08:56

Hi Rava,
mkfs.vfat: unable to open /dev/sde1: Read-only file system
I also had this mistake once

Remedy:
On Windows with diskpart.exe:

unfortunately, like I wrote above: currently no windoze available.

donald wrote: ↑

13 Jan 2021, 02:00

I would dd the whole drive
dd if=/dev/zero of=/dev/sdX bs=1M
If no errors occur, format the drive using GParted.

Cheap fake from ebay?

neither cheap nor from ebay.

Code: Select all

Jan 13 09:32:01 porteus kernel: [339934.278726] usb 2-1.2.1: USB disconnect, device number 85
Jan 13 09:32:11 porteus kernel: [339943.883879] usb 2-1.3: new high-speed USB device number 86 using ehci-pci
Jan 13 09:32:11 porteus kernel: [339943.907695] usb 2-1.3: New USB device found, idVendor=058f, idProduct=6387, bcdDevice= 1.0b
Jan 13 09:32:11 porteus kernel: [339943.907703] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 13 09:32:11 porteus kernel: [339943.907707] usb 2-1.3: Product: Intenso Alu Line
Jan 13 09:32:11 porteus kernel: [339943.907711] usb 2-1.3: Manufacturer: Alcor Tech
Jan 13 09:32:11 porteus kernel: [339943.907714] usb 2-1.3: SerialNumber: 13082800005231
Jan 13 09:32:11 porteus kernel: [339943.908304] usb-storage 2-1.3:1.0: USB Mass Storage device detected
Jan 13 09:32:11 porteus kernel: [339943.908739] scsi host8: usb-storage 2-1.3:1.0
Jan 13 09:32:11 porteus mtp-probe: checking bus 2, device 86: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3" 
Jan 13 09:32:11 porteus mtp-probe: bus: 2, device: 86 was not an MTP device 
Jan 13 09:32:12 porteus kernel: [339944.963321] scsi 8:0:0:0: Direct-Access     Intenso  Alu Line         8.07 PQ: 0 ANSI: 4
Jan 13 09:32:12 porteus kernel: [339944.965476] sd 8:0:0:0: [sdd] 30310400 512-byte logical blocks: (15.5 GB/14.5 GiB)
Jan 13 09:32:12 porteus kernel: [339944.966654] sd 8:0:0:0: [sdd] Write Protect is off
Jan 13 09:32:12 porteus kernel: [339944.967863] sd 8:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Jan 13 09:32:12 porteus kernel: [339944.977037] sd 8:0:0:0: [sdd] Write Protect is on
Jan 13 09:32:12 porteus kernel: [339944.978662] sd 8:0:0:0: [sdd] Attached SCSI removable disk
/var/log/messages lines 2119-2160/2160 (END)

sdd it is.

but soon after

Code: Select all

Jan 13 09:32:12 porteus kernel: [339944.966654] sd 8:0:0:0: [sdd] Write Protect is off

there is

Code: Select all

Jan 13 09:32:12 porteus kernel: [339944.977037] sd 8:0:0:0: [sdd] Write Protect is on

how does one disable Write Protect?
I only know of the remount rw option of mount, but we are far from the goal to mount the stick. How to change from Write Protect is on to Write Protect is off on an external non-mountable device?

Code: Select all

root@porteus:/# fdisk /dev/sdd

Welcome to fdisk (util-linux 2.36.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

fdisk: cannot open /dev/sdd: Read-only file system
root@porteus:/# sfdisk  /dev/sdd
sfdisk: cannot open /dev/sdd: Read-only file system
root@porteus:/# cfdisk  /dev/sdd
cfdisk: cannot open /dev/sdd: Read-only file system

fdisk —help nor sfdisk —help nor cfdisk —help give info on switching off write protect.

For now, dd sure fails even writing even a single bit:

Code: Select all

root@porteus:/# time dd if=/dev/zero of=/dev/sdd bs=1M;echo $?
dd: failed to open '/dev/sdd': Read-only file system

real	0m0.008s
user	0m0.005s
sys	0m0.003s
1
root@porteus:/#

Cheers!
Yours Rava

beny: Full of knowledge; Posts: 1669; Joined: 02 Jan 2011, 11:33; Location: italy

USB thumbdrive — mkfs.ext2: Input/output error while writing out and closing file system

Post#8

by beny » 13 Jan 2021, 23:34

from ubuntu forum,i do not have usb key damaged so…..

To turn off disk device`s write protect, we use the low level system utility hdparm like this:

sudo hdparm -r0 /dev/sdb

where we asume that /dev/sdb is the Physical disk device we’re working on. If the device has partitions that are mounted as read-only, you should re-mount ’em as read-write in order to write data to them.

Hope that helps.

Rava: Contributor; Posts: 4606; Joined: 11 Jan 2011, 02:46; Distribution: XFCE 5.0 x86_64 + 4.0 i586; Location: Forests of Germany

USB thumbdrive — mkfs.ext2: Input/output error while writing out and closing file system

Post#9

by Rava » 14 Jan 2021, 03:12

beny wrote: ↑

13 Jan 2021, 23:34

Hope that helps.

Unfortunately, no.

Code: Select all

Jan 14 03:42:02 porteus kernel: [397072.295871] usb 2-1.2.1: new high-speed USB device number 113 using ehci-pci
Jan 14 03:42:02 porteus kernel: [397072.321002] usb 2-1.2.1: New USB device found, idVendor=058f, idProduct=6387, bcdDevice= 1.0b
Jan 14 03:42:02 porteus kernel: [397072.321008] usb 2-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 14 03:42:02 porteus kernel: [397072.321013] usb 2-1.2.1: Product: Intenso Alu Line
Jan 14 03:42:02 porteus kernel: [397072.321016] usb 2-1.2.1: Manufacturer: Alcor Tech
Jan 14 03:42:02 porteus kernel: [397072.321019] usb 2-1.2.1: SerialNumber: […]
Jan 14 03:42:02 porteus kernel: [397072.321571] usb-storage 2-1.2.1:1.0: USB Mass Storage device detected
Jan 14 03:42:02 porteus kernel: [397072.322562] scsi host8: usb-storage 2-1.2.1:1.0
Jan 14 03:42:02 porteus mtp-probe: checking bus 2, device 113: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2.1" 
Jan 14 03:42:02 porteus mtp-probe: bus: 2, device: 113 was not an MTP device 
Jan 14 03:42:03 porteus kernel: [397073.347511] scsi 8:0:0:0: Direct-Access     Intenso  Alu Line         8.07 PQ: 0 ANSI: 4
Jan 14 03:42:03 porteus kernel: [397073.349491] sd 8:0:0:0: [sdc] 30310400 512-byte logical blocks: (15.5 GB/14.5 GiB)
Jan 14 03:42:03 porteus kernel: [397073.350828] sd 8:0:0:0: [sdc] Write Protect is off
Jan 14 03:42:03 porteus kernel: [397073.352879] sd 8:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Jan 14 03:42:03 porteus kernel: [397073.362613] sd 8:0:0:0: [sdc] Write Protect is on
Jan 14 03:42:03 porteus kernel: [397073.363942] sd 8:0:0:0: [sdc] Attached SCSI removable disk

so, sdc it is.

Code: Select all

root@porteus:/# hdparm -r0 /dev/sdc

/dev/sdc:
 setting readonly to 0 (off)
 readonly      =  0 (off)
root@porteus:/# fdisk  /dev/sdc

Welcome to fdisk (util-linux 2.36.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

fdisk: cannot open /dev/sdc: Read-only file system
root@porteus:/# hdparm -r0 /dev/sdc

/dev/sdc:
 setting readonly to 0 (off)
 readonly      =  0 (off)
root@porteus:/# time dd if=/dev/zero of=/dev/sdc bs=1M;echo $?
dd: failed to open '/dev/sdc': Read-only file system

real	0m0.006s
user	0m0.003s
sys	0m0.003s
1
root@porteus:/#

Seems hdparm has no effect.
There is no report in /var/log/messages about
sd 8:0:0:0: [sdc] Write Protect is off
either…

Cheers!
Yours Rava

Rava: Contributor; Posts: 4606; Joined: 11 Jan 2011, 02:46; Distribution: XFCE 5.0 x86_64 + 4.0 i586; Location: Forests of Germany

USB thumbdrive — mkfs.ext2: Input/output error while writing out and closing file system

Post#10

by Rava » 14 Jan 2021, 21:10

Update
Tried hdparm also on my 32 bit system running Porteus 4.0 — with the very same results.
Maybe booting Knoppix might help?

Does anyone has the porteus.cfg cheatcode to successfully boot the newest Knoppix DVD — from Nov 2020 when I recall right — copied as iso onto an USB stick?

Tried looking for that info on the official Knoppix forum to no prevail.

Cheers!
Yours Rava

Ed_P: Contributor; Posts: 7442; Joined: 06 Feb 2013, 22:12; Distribution: Cinnamon 5.0 ISO; Location: Western NY, USA

USB thumbdrive — mkfs.ext2: Input/output error while writing out and closing file system

Post#11

by Ed_P » 14 Jan 2021, 23:28

The hard part in booting an ISO is finding the parm it uses to boot the ISO. Possible ISO boot parms I have found are: boot=/, from=all, from=$iso, fromiso=$iso, findiso=$iso, iso-scan/filename=$iso, bootfrom=/dev/sda6$iso Where $iso has been set to the name of the ISO to be booted. Root should be set to the location of the ISO with a search command.

nanZor: Shogun; Posts: 331; Joined: 09 Apr 2019, 03:27; Distribution: Porteus 5.0 x86-64 LXDE; Location: Los Angeles

USB thumbdrive — mkfs.ext2: Input/output error while writing out and closing file system

Post#12

by nanZor » 17 Mar 2021, 08:52

You may want to try the latest 9.1, which is back to offering both cd or dvd-sized isos to download. I used Sonic which is close to me in San Francisco.

https://www.knopper.net/knoppix-mirrors/index-en.html

I know that Knoppix itself uses the last one Ed mentioned (changed device and filenames of course)

Last edited by nanZor on 17 Mar 2021, 09:09, edited 1 time in total.

That’s a UNIX book — cool. -Garth

Источник

Ubuntu 20.04, format of disk gives error, how to solve?

# mkfs -t ext4 /dev/nvme6n2
mke2fs 1.45.5 (07-Jan-2020)
Discarding device blocks: done                            
Creating filesystem with 3750232064 4k blocks and 468779008 inodes
Filesystem UUID: 9dc6c2f9-2297-4e44-a61d-481617e40158
Superblock backups stored on blocks: 
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
    4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 
    102400000, 214990848, 512000000, 550731776, 644972544, 1934917632, 
    2560000000

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: mkfs.ext4: Input/output error while writing out and closing file system

from dmesg:

[31366539.313763] print_req_error: 9 callbacks suppressed
[31366539.313766] blk_update_request: I/O error, dev nvme6c10n2, sector 1842432 op 0x1:(WRITE) flags 0x4004800 phys_seg 32 prio class 0
[31366539.314934] buffer_io_error: 596 callbacks suppressed
[31366539.314938] Buffer I/O error on dev nvme6n2, logical block 230304, lost async page write
[31366539.315492] Buffer I/O error on dev nvme6n2, logical block 230305, lost async page write
[31366539.316038] Buffer I/O error on dev nvme6n2, logical block 230306, lost async page write
[31366539.316566] Buffer I/O error on dev nvme6n2, logical block 230307, lost async page write
[31366539.317080] Buffer I/O error on dev nvme6n2, logical block 230308, lost async page write
[31366539.317582] Buffer I/O error on dev nvme6n2, logical block 230309, lost async page write
[31366539.318073] Buffer I/O error on dev nvme6n2, logical block 230310, lost async page write
[31366539.318554] Buffer I/O error on dev nvme6n2, logical block 230311, lost async page write
[31366539.319021] Buffer I/O error on dev nvme6n2, logical block 230312, lost async page write
[31366539.319482] Buffer I/O error on dev nvme6n2, logical block 230313, lost async page write
[31366539.319993] blk_update_request: I/O error, dev nvme6c10n2, sector 12854784 op 0x1:(WRITE) flags 0x4004800 phys_seg 32 prio class 0
[31366539.320929] blk_update_request: I/O error, dev nvme6c10n2, sector 163847936 op 0x1:(WRITE) flags 0x4004800 phys_seg 32 prio class 0
[31366539.321838] blk_update_request: I/O error, dev nvme6c10n2, sector 89918976 op 0x1:(WRITE) flags 0x4004800 phys_seg 32 prio class 0
[31366539.322782] blk_update_request: I/O error, dev nvme6c10n2, sector 63701504 op 0x1:(WRITE) flags 0x4004800 phys_seg 32 prio class 0
[31366539.323677] blk_update_request: I/O error, dev nvme6c10n2, sector 63704320 op 0x1:(WRITE) flags 0x4004800 phys_seg 32 prio class 0
[31366539.324621] blk_update_request: I/O error, dev nvme6c10n2, sector 163847680 op 0x1:(WRITE) flags 0x4004800 phys_seg 32 prio class 0
[31366539.329814] blk_update_request: I/O error, dev nvme6c10n2, sector 191112448 op 0x1:(WRITE) flags 0x4004800 phys_seg 32 prio class 0
[31366539.330868] blk_update_request: I/O error, dev nvme6c10n2, sector 191107584 op 0x1:(WRITE) flags 0x4004800 phys_seg 32 prio class 0
[31366539.348081] blk_update_request: I/O error, dev nvme6c10n2, sector 1719938048 op 0x1:(WRITE) flags 0x4004800 phys_seg 32 prio class 0

but disk is good:

smartctl -a /dev/nvme6n2
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-91-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       SAMSUNG MZWLR15THALA-00007
Serial Number:                      S6EXNE0R800894
Firmware Version:                   MPK90B5Q
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x002538
Total NVM Capacity:                 15,360,950,534,144 [15.3 TB]
Unallocated NVM Capacity:           0
Controller ID:                      65
Number of Namespaces:               32
Namespace 1 Size/Capacity:          15,360,950,534,144 [15.3 TB]
Namespace 1 Formatted LBA Size:     512
Local Time is:                      Mon Dec 19 18:06:52 2022 GMT
Firmware Updates (0x17):            3 Slots, Slot 1 R/O, no Reset required
Optional Admin Commands (0x00df):   Security Format Frmw_DL NS_Mngmt Self_Test MI_Snd/Rec Vrt_Mngmt
Optional NVM Commands (0x007f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Resv Timestmp
Maximum Data Transfer Size:         32 Pages
Warning  Comp. Temp. Threshold:     71 Celsius
Critical Comp. Temp. Threshold:     84 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +    25.00W   22.00W       -    0  0  0  0      180     180

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 -     512       0         1
 1 -     512       8         3
 2 -    4096       0         0
 3 -    4096       8         2
 4 -    4096      64         3

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

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        32 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    388,363,814 [198 TB]
Data Units Written:                 1,230,470,407 [630 TB]
Host Read Commands:                 2,891,609,287
Host Write Commands:                6,972,724,748
Controller Busy Time:               2,098
Power Cycles:                       1
Power On Hours:                     7,181
Unsafe Shutdowns:                   0
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               32 Celsius
Temperature Sensor 2:               32 Celsius
Temperature Sensor 3:               31 Celsius

Error Information (NVMe Log 0x01, max 256 entries)
No Errors Logged

One thing I see that I do find strange — the device enumeration in dev/ for these drives is missing. So nvme6n2 is a partition (partition 2) on disk nvme6, however nvme6 is not listed as a device in dev/

# ls /dev/nvme[6,7,8]*
/dev/nvme6n2  /dev/nvme7n2  /dev/nvme8n2

example of a WORKING disk, you can see the device nvme5:

# ls /dev/nvme[5]*
/dev/nvme5  /dev/nvme5n1  /dev/nvme5n1p1  /dev/nvme5n1p2

Источник

Same story here with my ASUS BR1100FKA, 128GB eMMC and Ubuntu 20.04.

It seems the laptop has eMMC controller with buggy CQE implementation.

Since linux kernel version 5.5 it is possible to make system avoid using CQE by specifying debug_quirks=0x20000 option to sdhci module. (0x20000 is the value for SDHCI_QUIRK_BROKEN_CQE flag in sdhci.h). After properly propagating the option I was able to install and use Ubuntu 20.04 with ext4 rootfs on the eMMC drive of this laptop.

There are few common ways to push the option to the system, depending on the situation you’re in:

Way 1: Unload the module and reload it with the option specified.

sudo modprobe -r sdhci_pci
sudo modprobe -r sdhci
sudo modprobe sdhci debug_quirks=0x20000
sudo modprobe sdhci_pci

This works when the system isn’t going to access eMMC drive during boot. For example, you are in some kind of linux installer and about to begin installation on the eMMC drive.

Way 2: Specify sdhci.debug_quirks=0x20000 option to the kernel command line.

This often can be done with bootloader menu. It might save the day when the eMMC drive is used during boot and you didn’t have a chance to burn the option via /etc/modprobe.d to initramfs.

Way 3: Use /etc/modprobe.d

Create a file like /etc/modprobe.d/sdhci-disable-cqe.conf which contains:

options sdhci debug_quirks=0x20000

This is usually «the right» way to permanently tweak module load behaviour. However, in order for it to work at early boot, one should make sure the config file gets to initrd image. Ways to do this may differ across distributions. For Ubuntu it’s usually running sudo update-initramfs -u after creating/editing a file in /etc/modprobe.d.

PS: From what I see — debug_quirks thing seems to be the only available option for disabling CQE on common kernel builds. The issue seems to be rare and usually encountered on some specific non-x86 hardware. I was really desperate and about to order an SSD, the idea to dig sdhci source code for all available options in response to some (non-CQE related) debug_quirks mentions came up just the last moment =)

Источник

butchkemper wrote: ↑

Sun Aug 08, 2021 9:35 pm

A couple of questions:

Have you partitioned the disk under Linux? Enter the command «sudo fdisk /dev/sdb», then enter p to print the partition table, and then q to quit.

What USB to SATA adapter are you using? Enter the command «lsusb -tv» to get information about the adapter(s).

Hopefully, the answers to the above questions will help.

Butch

Code: Select all

Command (m for help): p
Disk /dev/sdb: 698.7 GiB, 750156371968 bytes, 1465149164 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: 0xfe6aa3e7

Device     Boot Start        End    Sectors   Size Id Type
/dev/sdb1        2048 1465145343 1465143296 698.7G  7 HPFS/NTFS/exFAT

Command (m for help): t
Selected partition 1
Hex code (type L to list all codes): 83
Changed type of partition 'HPFS/NTFS/exFAT' to 'Linux'.

Command (m for help): p
Disk /dev/sdb: 698.7 GiB, 750156371968 bytes, 1465149164 sectors
Disk model: high speed
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: 0xfe6aa3e7

Device     Boot Start        End    Sectors   Size Id Type
/dev/sdb1        2048 1465145343 1465143296 698.7G 83 Linux

Command (m for help): w
fdisk: failed to write disklabel: Input/output error

I get error if I change to Linux.

2)
I order it from Aliexpress. The problem should not be the cable because all the other HDD drives are working on the same USB to SATA cable. I even swapped with the other HDD USB to SATA cables and still the problem exist.

When I type «lsusb -tv» while faulty HDD drive is not connected to RPI I get this:

Code: Select all

mohamed@RPI:~ $ lsusb -tv
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
    |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M

When I type «lsusb -tv» while faulty HDD drive is connected to RPI I get this:

Code: Select all

mohamed@RPI:~ $ lsusb -tv
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
    |__ Port 1: Dev 63, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
    |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M

So it’s the Bus 02 port 1: Dev 63, but what should I do with the info?

Источник

Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.

VoiceOfAgape: Level 1; Posts: 8; Joined: Wed Feb 16, 2022 11:27 am

Error formatting disk: (udisks-error-quark, 0)

I used the wipe command in Terminal to wipe my 2 TB hard drive
I then tried to use the “Disk” option to format the wiped drive
I selected “overwrite existing data with zeros” and “Compatible with modern systems and hard disk > 2 TB (GPT)”
When I press “Format” I get this message: “Error formatting disk: Error wiping device: Failed to probe the device ‘/dev/sda’ (udisks-error-quark, 0)”

Out of curiosity I entered “lsblk” at terminal and got this.

Code: Select all

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0   1.8T  0 disk 
sdb      8:16   0   1.8T  0 disk 
├─sdb1   8:17   0   512M  0 part /boot/efi
└─sdb2   8:18   0   1.8T  0 part /run/timeshift/backup
sdc      8:32   0 232.9G  0 disk 
├─sdc1   8:33   0   300M  0 part 
├─sdc2   8:34   0   100M  0 part 
├─sdc3   8:35   0   128M  0 part 
└─sdc4   8:36   0 232.3G  0 par

Just so you know, the target disk is sda.
Also, I don’t know much about computers, even less about Linux Mint. Please help me resolve this

Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.

Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.

AndyMH: Level 20; Posts: 11043; Joined: Fri Mar 04, 2016 5:23 pm; Location: Wiltshire

Re: Error formatting disk: (udisks-error-quark, 0)

Post

by AndyMH » Wed Feb 16, 2022 12:52 pm

Try again with gparted (install from software manager). Drive select is top right, View > device information will give you the panel on the left so you can confirm it has a gpt partition table. Right click in unallocated space to create new partitions. You will get a window at the bottom telling you want needs to be done, it doesn’t happen until you edit > apply all operations.

I have a suspicion that the partition table was not written correctly.

Homebrew i5-8400+GTX1080 Cinnamon 19.0, 4 x Thinkpad T430 Cinnamon 20.1, 2 x i7-3632 , i5-3320, i5-3210, Thinkpad T60 19.0 Mate

VoiceOfAgape: Level 1; Posts: 8; Joined: Wed Feb 16, 2022 11:27 am

Re: Error formatting disk: (udisks-error-quark, 0)

Post

by VoiceOfAgape » Wed Feb 16, 2022 2:31 pm

AndyMH wrote: ↑

Wed Feb 16, 2022 12:52 pm

Try again with gparted (install from software manager). Drive select is top right, View > device information will give you the panel on the left so you can confirm it has a gpt partition table. Right click in unallocated space to create new partitions. You will get a window at the bottom telling you want needs to be done, it doesn’t happen until you edit > apply all operations.

I have a suspicion that the partition table was not written correctly.
Screenshot from 2022-02-16 16-51-52.png

Thanks for your help.
When I try your suggestion I get the attached message.

Attachments

Gparted error msg.odg: (40.78 KiB) Downloaded 247 times

AndyMH: Level 20; Posts: 11043; Joined: Fri Mar 04, 2016 5:23 pm; Location: Wiltshire

Re: Error formatting disk: (udisks-error-quark, 0)

Post

by AndyMH » Wed Feb 16, 2022 3:06 pm

I cannot read the error message. You don’t need to create a libreoffice document (which I don’t use), you can post screenshots directly in your reply. Alt + PrtScn will take a screenshot of the active window, you will get a message box asking if you want to save it as a file, default save location is /home/you/Pictures. File size limit is 200kB, it will tell you if it is too big*.

Below the reply window on the forum — see the attachments tab. Click on that, click the button ‘Add file’, upload your screenshot and then a ‘place inline’ button appears. Clicking that will put the screenshot in your reply where your cursor is. Check with ‘Preview’.

Your next step is to wipe the start of the drive with dd, but I want to see the error message first.

* a very useful utility for cropping images is gthumb, install from software manager, it doesn’t do much else so very easy to use.

Homebrew i5-8400+GTX1080 Cinnamon 19.0, 4 x Thinkpad T430 Cinnamon 20.1, 2 x i7-3632 , i5-3320, i5-3210, Thinkpad T60 19.0 Mate

AndyMH: Level 20; Posts: 11043; Joined: Fri Mar 04, 2016 5:23 pm; Location: Wiltshire

Re: Error formatting disk: (udisks-error-quark, 0)

Post

by AndyMH » Wed Feb 16, 2022 7:23 pm

Better although it doesn’t tell me an awful lot.

Open a terminal and

Code: Select all

sudo dd if=/dev/zero of=/dev/sda bs=1M count=1

This will write zeros to the first MB of the drive wiping out the partition table.

Check and be absolutely sure that the drive is sda and double check before you hit Enter, get it wrong and you could wipe the wrong drive. dd is sometimes known as disk destroyer — make a typo, wrong drive and you can very easily wipe your system drive (do you have a backup?).

If it runs correctly you should see similar to this:

Code: Select all

andy@T432 ~ $ sudo dd if=/dev/zero of=/dev/sda bs=1M count=1
[sudo] password for andy:          
1+0 records in
1+0 records out
1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.00690903 s, 152 MB/s

Assuming that runs without any errors (if it does report any errors post them), try with gparted again. It will initially look like this. There is a warning triangle because there is no partition table on the drive.

create a new partition table — device > create partition table, select gpt. When that is done…

right click in the unallocated space to create a new partition, it will default to using the whole drive and ext4. When you create the partition, add a label*. When you click on Add, a window will open at the bottom of the gparted screen saying what has to be done. It doesn’t happen until you Edit > Apply all operations.

If gparted reports any errors, post screenshots. If you have any warning triangles next to partitions, right click on them and select information — what does it say?

* with a label, mint will automount the partition for you at /media/you/mylabel, if you don’t have a label it will use the UUID, e.g. /media/you/fb689910-e942-46e1-b03d-e7032e0e36bb, not user friendly.

Homebrew i5-8400+GTX1080 Cinnamon 19.0, 4 x Thinkpad T430 Cinnamon 20.1, 2 x i7-3632 , i5-3320, i5-3210, Thinkpad T60 19.0 Mate

VoiceOfAgape: Level 1; Posts: 8; Joined: Wed Feb 16, 2022 11:27 am

Re: Error formatting disk: (udisks-error-quark, 0)

Post

by VoiceOfAgape » Wed Feb 16, 2022 9:47 pm

After I entered the «gparted» command, the image appeared exactly like the one you showed. I however got the following on the Terminal:

Unit boot.mount does not exist, proceeding anyway.
Unit tmp.mount does not exist, proceeding anyway.
GParted 1.0.0
configuration —enable-libparted-dmraid —enable-online-resize
libparted 3.3
/dev/sda: unrecognised disk label

Should I proceed as per the rest of your instructions? (Won’t do anything until I hear from you).

AndyMH: Level 20; Posts: 11043; Joined: Fri Mar 04, 2016 5:23 pm; Location: Wiltshire

Re: Error formatting disk: (udisks-error-quark, 0)

Post

by AndyMH » Thu Feb 17, 2022 6:17 am

VoiceOfAgape wrote: ↑

Wed Feb 16, 2022 9:47 pm

Should I proceed as per the rest of your instructions? (Won’t do anything until I hear from you).

Did you run the dd command and did it report any errors?

Homebrew i5-8400+GTX1080 Cinnamon 19.0, 4 x Thinkpad T430 Cinnamon 20.1, 2 x i7-3632 , i5-3320, i5-3210, Thinkpad T60 19.0 Mate

AndyMH: Level 20; Posts: 11043; Joined: Fri Mar 04, 2016 5:23 pm; Location: Wiltshire

Re: Error formatting disk: (udisks-error-quark, 0)

Post

by AndyMH » Thu Feb 17, 2022 5:37 pm

No that is fine, the gparted default is to have 1MB free space before on the first partition — that leaves room for the partition table at the start of the drive.

You did create a partition table first?

Homebrew i5-8400+GTX1080 Cinnamon 19.0, 4 x Thinkpad T430 Cinnamon 20.1, 2 x i7-3632 , i5-3320, i5-3210, Thinkpad T60 19.0 Mate

VoiceOfAgape: Level 1; Posts: 8; Joined: Wed Feb 16, 2022 11:27 am

Re: Error formatting disk: (udisks-error-quark, 0)

Post

by VoiceOfAgape » Fri Feb 18, 2022 1:23 pm

The «Applying pending operation» (see image) ran for a while.

Then this:

I clicked on «save details» and was taken to a window on my hard drive that listed «gparted_details.htm» in the root directory. According to the instructions on the gparted website, this file must be copied to the hard drive because it will be deleted when computer is turned off. The site provided instructions to copy using a USB stick or to the hard drive. When I put the USB stick in, the computer fails to recognize it. I then tried the hard drive option but no success there either.

VoiceOfAgape: Level 1; Posts: 8; Joined: Wed Feb 16, 2022 11:27 am

Re: Error formatting disk: (udisks-error-quark, 0)

Post

by VoiceOfAgape » Fri Feb 18, 2022 1:54 pm

Here is the gparted report:

Create Primary Partition #1 (ext4, 1.82 TiB) on /dev/sda 00:12:12 ( ERROR )

create empty partition 00:00:24 ( SUCCESS )

path: /dev/sda1 (partition)
start: 2048
end: 3907028991
size: 3907026944 (1.82 TiB)
clear old file system signatures in /dev/sda1 00:02:06 ( SUCCESS )

write 512.00 KiB of zeros at byte offset 0 00:00:00 ( SUCCESS )
write 4.00 KiB of zeros at byte offset 67108864 00:00:00 ( SUCCESS )
write 4.00 KiB of zeros at byte offset 274877906944 00:00:00 ( SUCCESS )
write 512.00 KiB of zeros at byte offset 2000397271040 00:00:00 ( SUCCESS )
write 4.00 KiB of zeros at byte offset 2000397729792 00:00:00 ( SUCCESS )
write 8.00 KiB of zeros at byte offset 2000397787136 00:00:00 ( SUCCESS )
flush operating system cache of /dev/sda 00:00:21 ( SUCCESS )
set partition type on /dev/sda1 00:00:24 ( SUCCESS )

new partition type: ext4
create new ext4 file system 00:09:18 ( ERROR )

mkfs.ext4 -F -O ^64bit -L ‘NewData’ ‘/dev/sda1’ 00:09:18 ( ERROR )

64-bit filesystem support is not enabled. The larger fields afforded by this feature enable full-strength checksumming. Pass -O 64bit to rectify.
Discarding device blocks: done
Creating filesystem with 488378368 4k blocks and 122101760 inodes
Filesystem UUID: 713fac47-165e-4c8d-9246-b2ccd5a3bb76
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848

Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: 0/14905
mke2fs 1.45.5 (07-Jan-2020)
mkfs.ext4: Input/output error while writing out and closing file system

AndyMH: Level 20; Posts: 11043; Joined: Fri Mar 04, 2016 5:23 pm; Location: Wiltshire

Re: Error formatting disk: (udisks-error-quark, 0)

Post

by AndyMH » Fri Feb 18, 2022 8:36 pm

Try

if that fixes some errors, then try creating a partition with gparted again.

but I am running out of ideas

Homebrew i5-8400+GTX1080 Cinnamon 19.0, 4 x Thinkpad T430 Cinnamon 20.1, 2 x i7-3632 , i5-3320, i5-3210, Thinkpad T60 19.0 Mate

deck_luck: Level 6; Posts: 1381; Joined: Mon May 27, 2019 6:57 pm; Location: R-4808 North

Re: Error formatting disk: (udisks-error-quark, 0)

Post

by deck_luck » Sun Feb 27, 2022 3:45 am

VoiceOfAgape wrote: ↑

Fri Feb 18, 2022 1:54 pm

…

new partition type: ext4
create new ext4 file system 00:09:18 ( ERROR )

mkfs.ext4 -F -O ^64bit -L ‘NewData’ ‘/dev/sda1’ 00:09:18 ( ERROR )

64-bit filesystem support is not enabled. The larger fields afforded by this feature enable full-strength checksumming. Pass -O 64bit to rectify.

…

Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: 0/14905
mke2fs 1.45.5 (07-Jan-2020)

mkfs.ext4: Input/output error while writing out and closing file system

I assume you are using a 64 bit Linux. The 64bit warning is puzzling.

On the other hand, the input/output error is usually a hard disk or SSD failure. Did you check the dmesg or syslog for disk related errors. Also, did you check the s.m.a.r.t. status?

🐧Linux Mint 19 XFCE 💡Give a friend a fish, and you feed them for a day. Teach a friend how to fish, and you feed them for a lifetime. ✝️ Proverbs 4:7 Wisdom is the principal thing; therefore get wisdom: and with all thy getting get understanding.

Источник