• Booting problems

    Hi all,

    I have several problems at boot time.
    Can you help me to solve my problem?

    Here is my dmesg log:


    More detailed I extracted some section with problems from the dmesg:

    [    0.180663] ipmi:dmi: Invalid offset: 0
    [    2.881675] EXT4-fs (sdb2): re-mounted. Opts: discard
    [    2.908432] systemd-journald[226]: Received request to flush runtime journal from PID 1
    [    2.989829] systemd-journald[226]: /var/log/journal/4d6faa4d4eaa4a668589434a8d861583/system.journal: Journal file corrupted, rotating.
    [    3.033676] EXT4-fs (sdb2): Delayed block allocation failed for inode 2360268 at logical offset 964 with max blocks 3 with error 121
    [    3.033754] EXT4-fs (sdb2): This should not happen!! Data will be lost
    [   45.480488] EXT4-fs (sdb3): mounting with "discard" option, but the device does not support discard
    [   45.480490] EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts: discard
    [   45.485646] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
    [[email protected] ~]$ lsblk -f
    NAME   FSTYPE LABEL    UUID                                 MOUNTPOINT
    ├─sda1 ntfs   Recovery BC54A83054A7EAFA                     
    ├─sda2 vfat            4CA9-38C2                            
    ├─sda4 ntfs            C420AB4E20AB45F0                     
    └─sda5 ntfs            649033409033184E                     
    ├─sdb1 vfat   efi      44E3-3170                            /boot/efi
    ├─sdb2 ext4   root     00a9a9a0-b42d-40d7-b268-13ab35fc243f /
    ├─sdb3 ext4   home     4d50191f-cca9-40e9-87b8-4fe1ce107436 /home
    └─sdb4 swap            12ca2a2e-3cbe-45a9-bc21-df54616a776d [SWAP]
    └─sdc5 ntfs   Home     01D04E830B8CBF00  


  • @I-sty
    Seems like some kind of TRIM problem with your SSD, the SSD does not seem to support TRIM.
    How have you enabled TRIM (discard)?

  • @manuel

    [[email protected] ~]$ sudo hdparm -I /dev/sdb 
    ATA device, with non-removable media
    powers-up in standby; SET FEATURES subcmd spins-up.
    	Model Number:       KINGSTON SV300S37A120G                  
    	Serial Number:      50026B774B0394C4    
    	Firmware Revision:  580ABBF0
    	Transport:          Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
    	Used: unknown (minor revision code 0x0110) 
    	Supported: 8 7 6 5 
    	Likely used: 8
    	Logical		max	current
    	cylinders	16383	16383
    	heads		16	16
    	sectors/track	63	63
    	CHS current addressable sectors:    16514064
    	LBA    user addressable sectors:   234441648
    	LBA48  user addressable sectors:   234441648
    	Logical  Sector size:                   512 bytes
    	Physical Sector size:                   512 bytes
    	Logical Sector-0 offset:                  0 bytes
    	device size with M = 1024*1024:      114473 MBytes
    	device size with M = 1000*1000:      120034 MBytes (120 GB)
    	cache/buffer size  = unknown
    	Nominal Media Rotation Rate: Solid State Device
    	LBA, IORDY(can be disabled)
    	Queue depth: 32
    	Standby timer values: spec'd by Standard, with device specific minimum
    	R/W multiple sector transfer: Max = 1	Current = 1
    	Advanced power management level: 254
    	DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 udma6 
    	     Cycle time: min=120ns recommended=120ns
    	PIO: pio0 pio1 pio2 pio3 pio4 
    	     Cycle time: no flow control=120ns  IORDY flow control=120ns
    	Enabled	Supported:
    	   *	SMART feature set
    	    	Security Mode feature set
    	   *	Power Management feature set
    	   *	Write cache
    	   *	Host Protected Area feature set
    	   *	WRITE_BUFFER command
    	   *	READ_BUFFER command
    	   *	NOP cmd
    	   *	Advanced Power Management feature set
    	    	Power-Up In Standby feature set
    	   *	SET_FEATURES required to spinup after power up
    	    	SET_MAX security extension
    	   *	48-bit Address feature set
    	   *	Mandatory FLUSH_CACHE
    	   *	SMART error logging
    	   *	SMART self-test
    	   *	General Purpose Logging feature set
    	   *	64-bit World wide name
    	    	Write-Read-Verify feature set
    	   *	{READ,WRITE}_DMA_EXT_GPL commands
    	   *	Segmented DOWNLOAD_MICROCODE
    	    	unknown 119[6]
    	   *	Gen1 signaling speed (1.5Gb/s)
    	   *	Gen2 signaling speed (3.0Gb/s)
    	   *	Gen3 signaling speed (6.0Gb/s)
    	   *	Native Command Queueing (NCQ)
    	   *	Phy event counters
    	   *	NCQ priority information
    	   *	READ_LOG_DMA_EXT equivalent to READ_LOG_EXT
    	    	DMA Setup Auto-Activate optimization
    	    	Device-initiated interface power management
    	   *	Software settings preservation
    	   *	SMART Command Transport (SCT) feature set
    	   *	SCT Write Same (AC2)
    	   *	SCT Data Tables (AC5)
    	   *	reserved 69[3]
    	   *	DOWNLOAD MICROCODE DMA command
    	   *	WRITE BUFFER DMA command
    	   *	READ BUFFER DMA command
    	   *	Data Set Management TRIM supported (limit 1 block)
    	Master password revision code = 65534
    	not	enabled
    	not	locked
    	not	frozen
    	not	expired: security count
    		supported: enhanced erase
    Logical Unit WWN Device Identifier: 50026b774b0394c4
    	NAA		: 5
    	IEEE OUI	: 0026b7
    	Unique ID	: 74b0394c4
    Checksum: correct

    It seems that my ssd supports TRIM.
    Yes, I used discard.

    UUID=44E3-3170 /boot/efi vfat defaults,noatime 0 0
    UUID=00a9a9a0-b42d-40d7-b268-13ab35fc243f / ext4 defaults,noatime,discard 0 1
    UUID=4d50191f-cca9-40e9-87b8-4fe1ce107436 /home ext4 defaults,noatime,discard 0 0
    UUID=12ca2a2e-3cbe-45a9-bc21-df54616a776d swap swap defaults 0 0
  • @I-sty
    I’m no expert on this, but how did you create the disk? Did you copy the contents from a HDD?

    Anyway, a backup first would be wise thing to do.

    Then maybe install gsmartcontrol and check if it can give you more info about the drive’s health:

    sudo gsmartcontrol
  • @I-sty said in Booting problems:


    is set by default for Antergos, if it finds a trimmable ssd…

  • @joekamprad
    That’s what I was thinking, thus the question about was it copied/cloned from a HDD to SSD, because then maybe some drive parameters might not be correct.

  • i would try run fsck on the drive…

    3.033676] EXT4-fs (sdb2): Delayed block allocation failed for inode 2360268 at logical offset 964 with max blocks 3 with error 121
  • @joekamprad Wouldn’t it be wise to do a backup first? At least if there is something very important on the drive…
    And then fsck.

  • sure as you say before ;)

  • @manuel
    No I did not copy/clone from HDD.
    This is the install that we talked in the other topic.

  • @I-sty the error copy before from, your info can link to a real hardware defect onto the SSD, also the “TRIM not supported” error can be caused by this… but i do not want to paint the bad on the wall…

    You can try also to disable / remove the discard option from /etc/fstab for sdb and reboot to see if it works then… but best practise would be to backup data and run fsck on the ssd…

booting53 Posts 11Views 3122
Log in to reply
Bloom Email Optin Plugin

Looks like your connection to Antergos Community Forum was lost, please wait while we try to reconnect.