Computer Freezes During Reboot

Hi there, I’m getting the following screen during the reboot process:

Image Link: https://drive.google.com/file/d/0B5yli3l4UWzjcHFjby1Iel9obVU/view?usp=sharingMy computer freezes, and doesn’t respond to any keyboard command, forcing me to do a hard reset

I update openSuse once every month, and this error only popped up after I updated the system today.

I tried googling around, but I couldn’t seem to find problems that matched my situation.

My machine suspends and shuts down with no problems. This only comes up during a reboot.

I think it’s also worth mentioning that I’m dual booting with windows 7. Both os’s boot up fine

Please let me know if more information is needed to try to solve this problem.

EDIT: The same error is now also happening during shutdown

Update: The problem seems to have been resolved after updating my system today. I have rebooted successfully a coupe of times with no error.

Thanks for reporting the issue as solved. Hard to say anything about what happened.
Some advice: the Advanced Options offer to boot from a previous kernel…

There are “Kernel panic: not syncing” issues being reported for Ubuntu and Mint systems running version 4.4 and 4.8 kernels. There seems to be 2 possible causes for the problem:

  1. RTL WLAN hardware problems – firmware version;
  2. Bad disk sectors.

[HR][/HR]Given that trtbub has indicated that the system is a dual-boot MS Windows 7 system, the thought arises that, the disk may be a few years old.

  • Therefore: bad sectors and/or blocks.

Two things to do:

  1. Drop into “systemctl rescue” mode (SysV “init 1”) and run fsck on the root partition to inspect and repair any bad blocks and/or sectors.
  2. Check the “smartctl” output – especially the disk’s health . . .

Unfortunately the error has not been resolved after the update like I thought.

Sorry about going back and fourth with this, but this shutdown/reboot problem seems to be happening randomly.

Some advice: the Advanced Options offer to boot from a previous kernel…

Thanks for the advice. I reverted back to using version 4.4.70-18.9-default.

Until now, I think the error has only happened with version 4.4.74-18.20-default (I say “I think” because I’m not sure 4.4.70-18.9-default was the version that I was using prior to my monthly update)

Two things to do:

1.Drop into "systemctl rescue" mode (SysV "init 1") and run fsck on the root partition to inspect and repair any bad blocks and/or sectors.
2.Check the "smartctl" output -- especially the disk's health . . .

One of my hard drives has a single SMART failure, but I was aware of that for some time, and have been running both openSuse and Win7 on it with this failure with no perceivable problems (until now) for the past couple of months.

This hard drive is on a hardware RAID 1 with another hard drive that has yet to report any problem. Though both have the same age and are indeed kinda of old (running about 3 years, but I don’t leave my system on 24/7, it’s a desktop that’s only on during work hours and I suspend it regularly).

For a PC HDD, 3 years is normally not enough to qualify for “old age” – take a look at the SMART logs and the “end-of-life” hours which are normally logged there.
A hardware RAID should also help to avoid these issues but, are there any firmware updates available for your RAID controller?
In addition, “produced on a Monday” hardware can, and does, happen – the MTBF metric only indicates the expected life for the majority of the hardware delivered – you may have a HDD which is failing early with a specific driver version . . .

take a look at the SMART logs and the “end-of-life” hours which are normally logged there.

My RAID 1 Hard Drives are at +8000 hours of use

These are the only errors that pop up in one of them:

SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
Device Error Count: 2
        CR     = Command Register
        FEATR  = Features Register
        COUNT  = Count (was: Sector Count) Register
        LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
        LH     = LBA High (was: Cylinder High) Register    ]   LBA
        LM     = LBA Mid (was: Cylinder Low) Register      ] Register
        LL     = LBA Low (was: Sector Number) Register     ]
        DV     = Device (was: Device/Head) Register
        DC     = Device Control Register
        ER     = Error register
        ST     = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 2 [1] occurred at disk power-on lifetime: 1964 hours (81 days + 20 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 01 00 00 00 00 00 00 00 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d6 00 01 00 00 00 c2 4f e0 00 00     01:55:16.408  SMART WRITE LOG
  b0 00 d5 00 01 00 00 00 c2 4f e0 00 00     01:55:16.397  SMART READ LOG
  b0 00 d5 00 01 00 00 00 c2 4f 09 00 00     01:55:16.382  SMART READ LOG
  2f 00 00 00 01 00 00 00 00 00 07 40 00     01:55:16.378  READ LOG EXT
  2f 00 00 00 01 00 00 00 00 05 03 40 00     01:55:16.325  READ LOG EXT

Error 1 [0] occurred at disk power-on lifetime: 1964 hours (81 days + 20 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 01 00 00 00 00 00 00 00 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d6 00 01 00 00 00 c2 4f e0 00 00     01:55:16.110  SMART WRITE LOG
  b0 00 d5 00 01 00 00 00 c2 4f e0 00 00     01:55:16.110  SMART READ LOG
  60 00 30 00 00 00 00 00 11 34 9c 40 00     01:55:16.102  READ FPDMA QUEUED
  60 00 38 00 00 00 00 00 11 33 34 40 00     01:55:16.097  READ FPDMA QUEUED
  ec 00 00 00 01 00 00 00 00 00 00 00 00     01:55:16.080  IDENTIFY DEVICE

Though this “faulty” hd passes on the “overall health self-assessment” test.

My other hd’s don’t return any errors.

are there any firmware updates available for your RAID controller?

Probably, but I think I would need to flash my motherboard BIOS to update. I’d rather only do that as a last resource in troubleshooting. And up to this point, this seems to be a kernel version problem with my hardware, as my machine has not presented the reboot/shutdown freeze since I went back to using 4.4.70-18.9-default

you may have a HDD which is failing early with a specific driver version

My RAID1 hd’s are the same brand/model and have been used for the same amount of time. Smartctl also reports that both have the same firmware version.

It’s been a couple of days since I’ve went back to kernel version 4.4.70-18.9-default and stopped using version 4.4.74-18.20-default.

Since then the error has not appeared again.

Is there any additional information that I can share about this error (some sort of log)? As I think that I don’t have enough info to report this problem at http://bugzilla.opensuse.org/