Arch Linux

lumio

Member

Registered: 2017-12-21

Posts: 5

[SOLVED] Delayed block allocation failed

Hello everyone,

I just got myself a new SSD because I wanted to have a separate Arch installation to work with.
However, after installation I do get the following error message, often even before I log in:

EXT4-fs (sdb2): Delayed block allocation failed for inode 13894747 at logical offset 1099 with max blocks 1 with error 121
EXT4-fs (sdb2): This should not happen!! Data will be lost

Now I wonder if I should send that SSD back or is there somehow a workaround for this error?

Last edited by lumio (2017-12-22 14:24:24)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,863

Re: [SOLVED] Delayed block allocation failed

W/o context this can be either a HW or FS error, there should be a causing call for that - is this on a Raspberry Pi?
=> Run smartctl and fsck on the disk.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

lumio

Member

Registered: 2017-12-21

Posts: 5

Re: [SOLVED] Delayed block allocation failed

Thanks seth!

I have a MacBook Pro Mid 2015 and since I'm pretty fed up with macOS I thought I give Arch a try.
So I got myself an SSD, an external case and connected it via USB.

But I think the case itself is quite cheap and doesn't support SMART. So I need to try it with another adapter a little later.

However, I tested all partitions with fsck:

$ fsck /dev/sdd1 # (type EFI System)
fsck from util-linux 2.31
fsck.fat 4.1 (2017-01-24)
/dev/sdd1: 353 files, 6414/63965 clusters

$ fsck /dev/sdd2 # (type Linux filesystem, ext4)
fsck from util-linux 2.31
e2fsck 1.43.7 (16-Oct-2017)
/dev/sdd2: clean, 49345/15073280 files, 1655348/60293120 blocks

$ fsck /dev/sdd3 # (type Linux swap)
fsck from util-linux 2.31

When I use fsck directly on /dev/sdd, I get the following error:

$ fsck /dev/sdd
fsck from util-linux 2.31
e2fsck 1.43.7
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdd

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 ith an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

/dev/sdd contains `DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 500118191 sectors, extended partition table (last)' data

But I guess that is normal.

Last edited by lumio (2017-12-21 12:01:32)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,863

Re: [SOLVED] Delayed block allocation failed

Why is there an EFI partition on the disk?
SMART is not a feature of any case, but of the disk. A real SDD should support it (SD cards certainly won't)
=> try and see.
In doubt run badblocks - but not if the partition is mounted (and contains the running OS - you shouldn't even do that with fsck)
Use grml or some other live media.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

lumio

Member

Registered: 2017-12-21

Posts: 5

Re: [SOLVED] Delayed block allocation failed

Sorry for the misunderstanding. I'm using a Solid State Drive, not an SD card. Actually it is a Samsung SAM 850 Pro 256GB. And the external case is this one here https://www.amazon.de/gp/product/B00KW4 … ge_o00_s00
I tested with the drive unmounted, but will retry this evening with a proper SATA adapter.

I also tested it with my macs Disk Utility, and it didn't throw any errors. Also I booted onto my SSD and this time there was no bad block error.

Last edited by lumio (2017-12-21 15:16:51)

frostschutz

Member

Registered: 2013-11-15

Posts: 1,658

Re: [SOLVED] Delayed block allocation failed

When I use fsck directly on /dev/sdd

You're not supposed to

Be careful with fsck, it stands for "file system check and repair", but also for "file system crunch kill"

lumio

Member

Registered: 2017-12-21

Posts: 5

Re: [SOLVED] Delayed block allocation failed

well... since my current installation is kind of a vanilla one, it doesn't matter too much. In fact I am doing a destructive badblocks test right now.

Anyway... as I suspected, the USB interface of my case is kind of crap and does not allow an easy SMART check. I did with a proper SATA adapter and got the following result:

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

=== START OF INFORMATION SECTION ===
Model Family:     Samsung based SSDs
Device Model:     Samsung SSD 850 PRO 256GB
Serial Number:    S39KNX0J645749J
LU WWN Device Id: 5 002538 d420c546c
Firmware Version: EXM04B6Q
User Capacity:    256,060,514,304 bytes [256 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 4c
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is:    Thu Dec 21 21:32:38 2017 UTC
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: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x53) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					No 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: 	 ( 133) 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: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       2
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       22
177 Wear_Leveling_Count     0x0013   100   100   000    Pre-fail  Always       -       0
179 Used_Rsvd_Blk_Cnt_Tot   0x0013   100   100   010    Pre-fail  Always       -       0
181 Program_Fail_Cnt_Total  0x0032   100   100   010    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   010    Old_age   Always       -       0
183 Runtime_Bad_Block       0x0013   100   100   010    Pre-fail  Always       -       0
187 Uncorrectable_Error_Cnt 0x0032   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0032   075   069   000    Old_age   Always       -       25
195 ECC_Error_Rate          0x001a   200   200   000    Old_age   Always       -       0
199 CRC_Error_Count         0x003e   100   100   000    Old_age   Always       -       0
235 POR_Recovery_Count      0x0012   099   099   000    Old_age   Always       -       18
241 Total_LBAs_Written      0x0032   099   099   000    Old_age   Always       -       63072811

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

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
  255        0    65535  Read_scanning was never started
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.

Well I haven't done a read scanning. But other than that it doesn't look bad at all.

I think it is just the USB interface itself. I probably ditch the case and just get a normal adapter.

lumio

Member

Registered: 2017-12-21

Posts: 5

Re: [SOLVED] Delayed block allocation failed

Alright, last update on this one: The problem is indeed the SSD Case/Adapter. It is just a cheap interface and fails sometimes.
I ordered another Adapter which should work way better. I also got the installation right this time - so it was actually worth the destructive badblocks test

Thanks for you help @seth!