Issue creating ext4 filesystem on SSD of c220g1

[Bijan Tabatabai]

Hello,

I am trying to create a ext4 filesystem on the SSD of the c220g1 I have on the experiment at the URL https://www.cloudlab.us/status.php?uuid=fcf10c0d-d05e-11f0-bc80-e4434b2381fc.

I am taking the following steps:

1. Running fdisk on /dev/sdc to create a partition

2. Running "sudo mkfs.ext4 /dev/sdc1"

However, when I do this, I get the following output from mkfs:

mke2fs 1.47.0 (5-Feb-2023)
Discarding device blocks: done                            
Creating filesystem with 16777216 4k blocks and 4194304 inodes
Filesystem UUID: fb53685e-a60e-4589-8697-9aae63079b95
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424

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

Additionally, after running mkfs, neither /dev/sdc nor /dev/sdc1 are listed when running "lsblk" unless the machine is power cycled. Also, the console log reports many IO errors. A subset of those logs are shown below:

[  235.492659] I/O error, dev sdc, sector 2048 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 0^M
[  235.502575] Buffer I/O error on dev sdc1, logical block 0, lost async page write^M
[  235.510841] I/O error, dev sdc, sector 134219648 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 0^M
[  235.708669] I/O error, dev sdc, sector 134219648 op 0x1:(WRITE) flags 0x800 phys_seg 16 prio class 0^M
[  235.719258] I/O error, dev sdc, sector 134219648 op 0x9:(WRITE_ZEROES) flags 0x800 phys_seg 0 prio class 0^M
[  235.730486] I/O error, dev sdc, sector 10568 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 0^M
[  235.958484] I/O error, dev sdc, sector 10568 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0^M
[  235.968551] I/O error, dev sdc, sector 10568 op 0x9:(WRITE_ZEROES) flags 0x800 phys_seg 0 prio class 0^M
[  235.979426] I/O error, dev sdc, sector 76144 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 0^M
[  236.209306] I/O error, dev sdc, sector 76144 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0^M
[  236.219296] I/O error, dev sdc, sector 76144 op 0x9:(WRITE_ZEROES) flags 0x800 phys_seg 0 prio class 0^M
[  240.758312] I/O error, dev sdc, sector 67409920 op 0x1:(WRITE) flags 0x4000 phys_seg 64 prio class 0^M

At first I thought this was potential a faulty disk, but I repeated the steps on a different experiment (https://www.cloudlab.us/status.php?uuid=a683cae0-d07b-11f0-bc80-e4434b2381fc) and had the same result.

Am I doing something wrong? I would appreciate any suggestions to be able to use the SSD.

Thanks,

Bijan Tabatabai

[Mike Hibler]

The SSD is probably just bad. The c220g1 node are pretty old. We will see
if someone at Wisconsin has a replacement drive, but you may need to
reinstantiate on another node. I have scheduled the node you are currently
using to go out of service when your experiment terminates, so you will not
just get the same node back again.

> --
> You received this message because you are subscribed to the Google Groups
> "cloudlab-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email
> to cloudlab-user...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/cloudlab-users/
> a9280bcf-608d-4c06-983f-72a3277f0a17n%40googlegroups.com.

[Mike Hibler]

FYI, the SSD has been replaced and the node is back in service.

On Wed, Dec 03, 2025 at 01:26:43PM -0700, Mike Hibler wrote:
> The SSD is probably just bad. The c220g1 node are pretty old. We will see
> if someone at Wisconsin has a replacement drive, but you may need to
> reinstantiate on another node. I have scheduled the node you are currently
> using to go out of service when your experiment terminates, so you will not
> just get the same node back again.
>
> On Wed, Dec 03, 2025 at 11:52:47AM -0800, 'Bijan Tabatabai' via cloudlab-users wrote:
> > Hello,
> >
> > I am trying to create a ext4 filesystem on the SSD of the c220g1 I have on the

> > experiment at the URL??https://www.cloudlab.us/status.php?uuid=

> > fcf10c0d-d05e-11f0-bc80-e4434b2381fc.
> >
> > I am taking the following steps:
> > 1. Running fdisk on /dev/sdc to create a partition
> > 2. Running "sudo mkfs.ext4 /dev/sdc1"
> >
> > However, when I do this, I get the following output from mkfs:
> >
> > mke2fs 1.47.0 (5-Feb-2023)

> > Discarding device blocks: done ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??

> > Creating filesystem with 16777216 4k blocks and 4194304 inodes
> > Filesystem UUID: fb53685e-a60e-4589-8697-9aae63079b95
> > Superblock backups stored on blocks:
> > 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
> > 4096000, 7962624, 11239424
> >

> > Allocating group tables: done ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??
> > Writing inode tables: done ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??

> > Creating journal (131072 blocks): done
> > Writing superblocks and filesystem accounting information: mkfs.ext4: Input/
> > output error while writing out and closing file system
> >
> > Additionally, after running mkfs, neither /dev/sdc nor /dev/sdc1 are listed
> > when running "lsblk" unless the machine is power cycled. Also, the console log
> > reports many IO errors. A subset of those logs are shown below:
> >

> > [ ??235.492659] I/O error, dev sdc, sector 2048 op 0x1:(WRITE) flags 0x100000

> > phys_seg 1 prio class 0^M

> > [ ??235.502575] Buffer I/O error on dev sdc1, logical block 0, lost async page
> > write^M
> > [ ??235.510841] I/O error, dev sdc, sector 134219648 op 0x9:(WRITE_ZEROES) flags

> > 0x8000800 phys_seg 0 prio class 0^M

> > [ ??235.708669] I/O error, dev sdc, sector 134219648 op 0x1:(WRITE) flags 0x800

> > phys_seg 16 prio class 0^M

> > [ ??235.719258] I/O error, dev sdc, sector 134219648 op 0x9:(WRITE_ZEROES) flags

> > 0x800 phys_seg 0 prio class 0^M

> > [ ??235.730486] I/O error, dev sdc, sector 10568 op 0x9:(WRITE_ZEROES) flags

> > 0x8000800 phys_seg 0 prio class 0^M

> > [ ??235.958484] I/O error, dev sdc, sector 10568 op 0x1:(WRITE) flags 0x800

> > phys_seg 1 prio class 0^M

> > [ ??235.968551] I/O error, dev sdc, sector 10568 op 0x9:(WRITE_ZEROES) flags

> > 0x800 phys_seg 0 prio class 0^M

> > [ ??235.979426] I/O error, dev sdc, sector 76144 op 0x9:(WRITE_ZEROES) flags

> > 0x8000800 phys_seg 0 prio class 0^M

> > [ ??236.209306] I/O error, dev sdc, sector 76144 op 0x1:(WRITE) flags 0x800

> > phys_seg 1 prio class 0^M

> > [ ??236.219296] I/O error, dev sdc, sector 76144 op 0x9:(WRITE_ZEROES) flags

> > 0x800 phys_seg 0 prio class 0^M

> > [ ??240.758312] I/O error, dev sdc, sector 67409920 op 0x1:(WRITE) flags 0x4000

> > phys_seg 64 prio class 0^M
> >
> > At first I thought this was potential a faulty disk, but I repeated the steps
> > on a different experiment (https://www.cloudlab.us/status.php?uuid=
> > a683cae0-d07b-11f0-bc80-e4434b2381fc) and had the same result.
> >
> > Am I doing something wrong? I would appreciate any suggestions to be able to
> > use the SSD.
> >
> > Thanks,
> > Bijan Tabatabai
> >
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "cloudlab-users" group.
> > To unsubscribe from this group and stop receiving emails from it, send an email
> > to cloudlab-user...@googlegroups.com.
> > To view this discussion visit https://groups.google.com/d/msgid/cloudlab-users/
> > a9280bcf-608d-4c06-983f-72a3277f0a17n%40googlegroups.com.
>
> --
> You received this message because you are subscribed to the Google Groups "cloudlab-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to cloudlab-user...@googlegroups.com.

> To view this discussion visit https://groups.google.com/d/msgid/cloudlab-users/20251203202643.GB1107%40flux.utah.edu.