Ubuntu 17.10 intermittently stalls on booting, Memtest86 ok

Asked by Pablo on 2018-05-16

Ubuntu logo will begin to blink when booting and boot process will stall. I power off with power button and most often on 2nd time around will boot appropriately, although sometimes it will take a third time. At other times it will boot right up normally. This is with Ubuntu 17.10. Can you suggest solution? Thank you (This is similar to earlier question still open....)

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
2018-05-25
Last reply:
2018-06-09

Have you ran an fsck on the Linux partitions? You can do this from the Live Ubuntu desktop easily
Make sure you have the latest BIOS too

Pablo (ceascolombia) said : #2

thank you. I will be back in touch. (I started a new question because I received no further feedback on my earlier question.) I look forward to your walking me through this.

Pablo (ceascolombia) said : #4

I made a LIve Ubuntu DVD. I booted with it and chose the Try Ubuntu option. I opened the terminal and gave the following command:
sudo fsck /dev/sda1

this is the response I got:
fsck from util-linux 2.30.1

Is that it? I don't know what to do next,. where to I go from there?

(Again, I lament my limited know-how.)

Pablo (ceascolombia) said : #5

It would be hlepful to me to orient me to checking for whether I have the most recent bios.

Would a solution be to simply update to 18.04?

sudo dmidecode -t 1

Will give you some output then check the manufacturer website. Often the upgraders need a windows based OS.

Did you read the link I gave about fsck? It gives an explanation of the command

Pablo (ceascolombia) said : #7

Thank you for the BIOS info. I will check on possible upgrade.

About fsck, yes I consulted the link y0u sent about fsck, but I didn't understand what to do with it. I think I have used "sudo fsck /dev/sda1" in the past to run fsck from a live Ubuntu DVD, but apparently it is not the right command .... I don't know what to do with the response, "fsck from util-linux 2.30.1". I think I will need for you to walk me through the process.

Thank you in advance

Pablo (ceascolombia) said : #8

Re BIOS update: My machine is old, and Lenovo doesn't indicate a BIOS update for the version of windows I have (10), only for earlier versions of Windows. I am inquiring how to update BIOS given that fact.

Can you walk me through running fsck with Live Ubuntu CD (see earlier note).

thank you

Pablo (ceascolombia) said : #9

I updated BIOS. Problem persists.

Pablo (ceascolombia) said : #10

running fsck from UbuntuLive:

ubuntu@ubuntu:~$ sudo fsck /dev/sda1
fsck from util-linux 2.30.1
ubuntu@ubuntu:~$ sudo fsck /dev/sda3
fsck from util-linux 2.30.1
e2fsck 1.43.5 (04-Aug-2017)
fsck.ext2: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda3
Could this be a zero-length partition?
ubuntu@ubuntu:~$ sudo fsck /dev/sda5
fsck from util-linux 2.30.1
e2fsck 1.43.5 (04-Aug-2017)
/dev/sda5: clean, 480422/12722176 files, 31583438/50867712 blocks

Pablo (ceascolombia) said : #11

This describes the partitions:

$ sudo parted /dev/sda print
[sudo] password for paul:
Model: ATA HGST HTS725032A7 (scsi)
Disk /dev/sda: 320GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
 1 1049kB 525MB 524MB primary ntfs boot
 2 525MB 112GB 111GB primary ntfs
 3 112GB 320GB 208GB extended
 5 112GB 320GB 208GB logical ext4

Pablo (ceascolombia) said : #12

Problem persists, seems to take more vailed boots before positive boot happens.

Please recommend next steps.

thank you

After the issue subsides, run:

dmesg | tail

Copy the output and paste as an update.

Thanks

Pablo (ceascolombia) said : #14

~$ dmesg | tail
[ 7330.387712] wlp3s0: authenticated
[ 7330.387896] iwlwifi 0000:03:00.0 wlp3s0: disabling HT as WMM/QoS is not supported by the AP
[ 7330.387899] iwlwifi 0000:03:00.0 wlp3s0: disabling VHT as WMM/QoS is not supported by the AP
[ 7330.392401] wlp3s0: associate with cc:35:40:90:61:6f (try 1/3)
[ 7330.394806] wlp3s0: RX AssocResp from cc:35:40:90:61:6f (capab=0x411 status=0 aid=2)
[ 7330.397593] wlp3s0: associated
[ 7348.003578] audit: type=1400 audit(1526993670.303:142): apparmor="DENIED" operation="open" profile="snap.wavebox.wavebox" name="/proc/2833/sched" pid=2271 comm="Wavebox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
[ 7348.004819] audit: type=1400 audit(1526993670.304:143): apparmor="DENIED" operation="open" profile="snap.wavebox.wavebox" name="/proc/2800/sched" pid=2271 comm="Wavebox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
[ 7348.005978] audit: type=1400 audit(1526993670.305:144): apparmor="DENIED" operation="open" profile="snap.wavebox.wavebox" name="/proc/2799/sched" pid=2271 comm="Wavebox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
[ 7348.008172] audit: type=1400 audit(1526993670.308:145): apparmor="DENIED" operation="open" profile="snap.wavebox.wavebox" name="/proc/2271/sched" pid=2271 comm="Wavebox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
paul@paul-ThinkPad-T420s:~$

Pablo (ceascolombia) said : #15

When I try to create a folder from Ubuntu into my Windows partition II get the message "Error creating directory...:Read-only file system" and I am unable to save files into the Windows partition. Is this related to the problem we are considering?

Run a chkdsk on the partition. Sounds like the file system isn't quite consistent. You will need a Windows OS for this as NTFS is proprietary to Microsoft and only they know how it really works. The NTFS access in Ubuntu is a best effort attempt through lots of hard work by the ntfs-3g guys

Pablo (ceascolombia) said : #17

Problem accessing Windows partition was due to fast start-up being reactivated in Windows 10 after Windows 10 update. Once I desabled fast start-up, problem accessing the Windows partition disappeared. So I didn't run chkdsk on the Windows partitions.

Pablo (ceascolombia) said : #18

Regarding the boot problem, could it be related to the result of fsck for sda3 (see above) and which I paste here?
ubuntu@ubuntu:~$ sudo fsck /dev/sda3
fsck from util-linux 2.30.1
e2fsck 1.43.5 (04-Aug-2017)
fsck.ext2: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda3
Could this be a zero-length partition?

sda 3 is described as : 112GB 320GB 208GB extended

Launchpad Janitor (janitor) said : #19

This question was expired because it remained in the 'Open' state without activity for the last 15 days.