[SOLVED] How to kill task when Black Screen with HDD LED light blinking for hours
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
How to kill task when Black Screen with HDD LED light blinking for hours
My notebook is now running black screen but only mouse pointer appearing freeze and unfreeze on screen. The HDD LED light keep blinking and i can hear the blinking sound of the HDD.
Problem is this had been going on for hours, i have been waited long tempted to just power off forcefuly, but i don't think this is a good idea.
How can i interrupt and stop the process. i tried with Crtl+Alt+Del but no respone.I am with 512RAM,swap partition about 10GB(Is memory setting is the culprit here).
Can't show you my Spec details from Terminal as i am now posting from another Notebook PC.
WHat's your distro? Some distros have access to text console via Ctrl-Alt-F1. And you can force a kill on X Server by Ctrl-Alt-Backspace. You can try to connect to it via ssh as well.
Thanks guys, i managed to solved it with Ctrl-Alt-F1 mode, then Ctrl-Alt-Backspace.
Obviously it was memory issue here.
Can you guys please help me to diagnose and do some healing here, i am sure later it will happen again.
If you're right, you will have low figures or even 0 in the "free", "buffers" and "cached" columns of the "Mem" line and a high figure in the "used" column of the "Swap" line.
gab@gab-Inspiron-700m:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda11 during installation
UUID=daa5a1bf-ac55-44ca-9e69-815717925690 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda12 during installation
UUID=caa40260-8d73-4e3f-8e62-c7365564899a none swap sw 0 0
Distribution: Mainly Devuan, antiX, & Void, with Tiny Core, Fatdog, & BSD thrown in.
Posts: 5,490
Rep:
errors=remount
This is for the kernel on initial startup.
I believe it means that if it finds a fault in the filesystem, it will do a filesystem check, & then try to remount your root partition & continue with the boot process.
It does look like that. It can't find the swap device that is configured in fstab. fdisk -l shows that it is /dev/sda7. Chek if it's UUID is same one as in fstab. You can try using device name in fstab directly.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.