laptop failed to wake up from suspend mode, boot failure afterwards

erdos · 2019-06-23 03:11:13

hi, my thinkpad t60 has devuan ascii installed along with windowsXP/freebsd. recently when i opened the lid to wake it from previous sleep state in devuan, it displayed shell instead of returning to X /WM. when i power cycle and reboot it, the machine won't boot, after thinkpad logo appears on the screen, it display a bunch of '07 07 07....' on the screen, no grub menu.

screenshot of boot error screen.
https://1drv.ms/u/s!AgFqxF-g9pqPvxl_RJq … 2?e=WHYDzz

i can get into bios and change settings, i can also boot into slackware linux installed onto an external hdd, and mounted the windows partition and my /home partition on devuan.
however, i can't mount devuan root / partion, receiving error.

bash-4.2# fdisk -l

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders, total 156301488 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
Disk identifier: 0x9f114bc6

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63    62929439    31464688+   7  HPFS/NTFS/exFAT
/dev/sda2       106027047   143775701    18874327+  a5  FreeBSD
/dev/sda3       143806320   156295439     6244560    c  W95 FAT32 (LBA)
/dev/sda4        62930942   106027007    21548033    f  W95 Ext'd (LBA)
/dev/sda5        62930944    82460671     9764864   83  Linux
/dev/sda6        82462720    85053439     1295360   82  Linux swap
/dev/sda7        85055488   106027007    10485760   83  Linux

bash-4.2# mount /dev/sda5 /mnt/tmp
mount: wrong fs type, bad option, bad superblock on /dev/sda5,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

bash-4.2# mount /dev/sda7 /mnt/tmp

any advice?

laptop specs:
Lenovo Thinkpad T60 1.83Ghz/2G RAM/80G HDD
WinXP/freebsd/Debian8 triple boot

Head_on_a_Stick · 2019-06-23 09:22:19

Which filesystem is Devuan installed on?

Do you have the appropriate filesystem tools package installed in the system from which you are trying to mount the Devuan partition?

Have you tried fsck?

It may be best to boot the Devuan ASCII minimal-live.iso image to ensure compatibility:

https://mirror.leaseweb.com/devuan/devu … imal-live/

PedroReina · 2019-06-23 10:44:51

erdos wrote:

it display a bunch of '07 07 07....' on the screen, no grub menu.

Strange enough, it seems a LILO problem to me.

From https://www.linux.org/threads/linux-lin … tup.10146/

L – First stage of the boot loader has finished and has been unable to load the second stage. This usually indicates bad BIOS parameters or bad sectors on the media or even a corruption of the boot loader. The letter is usually followed by an error code as follows:
07 – Invalid initialization – BIOS did not initialize the boot disk

Last edited by PedroReina (2019-06-23 22:20:08)

erdos · 2019-06-23 21:03:40

Head_on_a_Stick wrote:

Which filesystem is Devuan installed on?
Do you have the appropriate filesystem tools package installed in the system from which you are trying to mount the Devuan partition?
Have you tried fsck?
It may be best to boot the Devuan ASCII minimal-live.iso image to ensure compatibility:
https://mirror.leaseweb.com/devuan/devu … imal-live/

devuan ascii was installed on ext4, on partition /dev/sda5, slackware was installed as ext4 on external HDD.

bash-4.2# file -sL /dev/sd*
/dev/sda:  x86 boot sector
/dev/sda1: x86 boot sector
/dev/sda2: x86 boot sector
/dev/sda3: x86 boot sector
/dev/sda4: x86 boot sector
/dev/sda5: Linux rev 1.0 ext4 filesystem data, UUID=0262b140-607c-4a24-b40b-faa1e1cd222b (extents) (64bit) (large files) (huge files)
/dev/sda6: Linux/i386 swap file (new style), version 1 (4K pages), size 323839 pages, no label, UUID=c844573e-30c1-4c64-8e7d-0857e041b5ba
/dev/sda7: Linux rev 1.0 ext4 filesystem data, UUID=244b532e-263c-41ac-b009-28669b7301e3 (extents) (large files) (huge files)

running fsck from slackware (ver. 14.1) results,

bash-4.2# fsck /dev/sda5
fsck from util-linux 2.21.2
e2fsck 1.42.8 (20-Jun-2013)
/dev/sda5 has unsupported feature(s): metadata_csum
e2fsck: Get a newer version of e2fsck!

i have ascii installation image on usb drive, will that be of help?

erdos · 2019-06-23 21:09:47

PedroReina wrote:

erdos wrote:
it display a bunch of '07 07 07....' on the screen, no grub menu.
Strange enough, its seems a LILO problem to me.
From https://www.linux.org/threads/linux-lin … tup.10146/
L – First stage of the boot loader has finished and has been unable to load the second stage. This usually indicates bad BIOS parameters or bad sectors on the media or even a corruption of the boot loader. The letter is usually followed by an error code as follows:
07 – Invalid initialization – BIOS did not initialize the boot disk

thank you, this is very strange, did ascii corrupt my bootloader somehow? i had 'pm-suspend' feature working most of time on my thinkpad with devuan ascii, when it didn't work properly, i had to recycle power. however this time it results a boot failure.

i ran built-in hdd diagnostic tool in Bios as well as 'badlocks' command from slackware, both reporting no error.

badblocks -v /dev/sda
checking blocks 0 to 78150743
checking for bad blocks(read-only test):
done
pass completed, 0 bad blocks found (0/0/0 errors)

czeekaj · 2019-06-24 03:23:44

Could be the way your bios is reading the boot instructions. Although if it's not mounting somthing odd is happening.

I know it's a stretch but try pulling the battery out of your laptop and re-seat the ram. If you can't mount it from a live image than something went amiss while your lid was closed.

have you tried chrooting and re-installing? Or efibootmgr from a live image?

Are you using MBR boot? If so installing a new system can overwrite the old one.

Last edited by czeekaj (2019-06-24 11:54:52)

Head_on_a_Stick · 2019-06-24 16:32:23

erdos wrote:

running fsck from slackware (ver. 14.1) results,
bash-4.2# fsck /dev/sda5
fsck from util-linux 2.21.2
e2fsck 1.42.8 (20-Jun-2013)
/dev/sda5 has unsupported feature(s): metadata_csum
e2fsck: Get a newer version of e2fsck!
i have ascii installation image on usb drive, will that be of help?

Yes, run fsck from the USB drive system, the version in Slackware is not compatible.

You should also be able to mount & chroot from the USB system.

erdos · 2019-06-25 00:39:42

Head_on_a_Stick wrote:

Yes, run fsck from the USB drive system, the version in Slackware is not compatible.
You should also be able to mount & chroot from the USB system.

Great! I reinstalled grub bootloader from bootable ascii USB drive onto hdd, now it boots into devuan again!

The officially official Devuan Forum!

#1 2019-06-23 03:11:13

laptop failed to wake up from suspend mode, boot failure afterwards

#2 2019-06-23 09:22:19

Re: laptop failed to wake up from suspend mode, boot failure afterwards

#3 2019-06-23 10:44:51

Re: laptop failed to wake up from suspend mode, boot failure afterwards

#4 2019-06-23 21:03:40

Re: laptop failed to wake up from suspend mode, boot failure afterwards

#5 2019-06-23 21:09:47

Re: laptop failed to wake up from suspend mode, boot failure afterwards

#6 2019-06-24 03:23:44

Re: laptop failed to wake up from suspend mode, boot failure afterwards

#7 2019-06-24 16:32:23

Re: laptop failed to wake up from suspend mode, boot failure afterwards

#8 2019-06-25 00:39:42

Re: laptop failed to wake up from suspend mode, boot failure afterwards

Board footer