Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

no volume groups found


  • Please log in to reply
32 replies to this topic

#1 rozzer

rozzer

  • Members
  • 250 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:South Africa
  • Local time:07:42 AM

Posted 30 December 2016 - 01:48 AM

hi

 

switched on my pc this morning and I just get black screen with a movable curser

no light on the keyboard.

i googled and found :- ctrl+alt+f1 and then tried to update Grub (sudo update-grub)

and I am presented with the following:-

found......................Linux Image

found......................initrd image

found......................memtest86+elf image

found......................memtest86+bin image

No volume groups found

found......................Microsoft XP on /dev/sda1.

 

I checked the partition manager in XP and all seems ok, displays

127.99 GB NTFS (healthy)

27.94GB unknown partition (healthy)

186.26GB unknown partition (healthy)

953MB unknown partition (healthy)

588.38GB unallocated.

 

your help is appreciated

 

Cheers



BC AdBot (Login to Remove)

 


#2 cat1092

cat1092

    Bleeping Cat


  • BC Advisor
  • 7,018 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:North Carolina, USA
  • Local time:01:42 AM

Posted 30 December 2016 - 05:06 AM

May want to remove the drive, and if you have an enclosure or docking station, on a working computer, run WD diagnostics on the it to check for any bad sectors with their tool (has to be performed on a Windows computer).

 

http://support.wdc.com/downloads.aspx?p=

 

The non showing of the light on the keyboard doesn't sound good either, though this may be normal when the computer doesn't boot. There is a grub boot repair tool that's free, link on the below page. 

 

http://www.howtogeek.com/114884/how-to-repair-grub2-when-ubuntu-wont-boot/

 

See if that gets you anywhere & let us know the outcome. :)

 

Good Luck!

 

Cat


Edited by cat1092, 30 December 2016 - 05:09 AM.

Performing full disc images weekly and keeping important data off of the 'C' drive as generated can be the best defence against Malware/Ransomware attacks, as well as a wide range of other issues. 


#3 Al1000

Al1000

  • Global Moderator
  • 8,054 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:05:42 AM

Posted 30 December 2016 - 06:38 AM

As you are able to log into tty1 and update grub, your system is booting; it looks like there is something wrong with the GUI.

The fact that it boots into Windows as well, indicates that this is not a hardware issue.

"No volume groups found" isn't necessarily a warning, unless you use LVM. It looks like Grub is just telling you that it didn't find any volume groups.

First thing I would try is booting into "Recovery mode" from the Grub menu. Let us know how that goes.

#4 Al1000

Al1000

  • Global Moderator
  • 8,054 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:05:42 AM

Posted 30 December 2016 - 06:40 AM

run WD diagnostics on the it to check for any bad sectors with their tool (has to be performed on a Windows computer).


WD diagnostics can also be run from a bootable DOS USB (that's how I've used it before), and of course is only intended to be run on Western Digital hard drives. According to his profile, rozzer is using a Seagate HDD.

#5 rozzer

rozzer
  • Topic Starter

  • Members
  • 250 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:South Africa
  • Local time:07:42 AM

Posted 30 December 2016 - 07:19 AM

Hi Al1000 & Cat

 

I tried to run the recovery and it still fails.

I tried ctrl+alt+f1, logged in and this is the reading I get

0 packages can be updated

0 updates are security updates

 

Tried entering TOP in terminal and this is the results of processes

Top -13:50:46 up 7min, 2users, load average 0,00, 0,08, 0,08

Task: 117 Total, 1Running, 116 Sleeping, 0 stopped, 0 Zombie

%CPU(s) : constantly changing values

KiB Mem:        4045480 Total

                        1517620 Used

                        2527860 Free

                        404468 Buffers

 

KiB Swap:       975868 Total

                        0 Used

                        975868 Free

                        416108 Cached Mem

 

Not sure how much this information will help but hope it does

Thanks for your help

 

Cheers

 

# Edit prepared this before I logged in to the forum so will wait to run WD diagnostics until

you have read this

 

Cheers


Edited by rozzer, 30 December 2016 - 07:19 AM.


#6 Al1000

Al1000

  • Global Moderator
  • 8,054 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:05:42 AM

Posted 30 December 2016 - 07:50 AM

I tried ctrl+alt+f1, logged in and this is the reading I get

0 packages can be updated

0 updates are security updates


What command are you running to get that output?

Please also confirm:

1) The operating system you are using

2) The manufacturer of your HDD, e.g. Western Digital, Seagate, etc.

#7 rozzer

rozzer
  • Topic Starter

  • Members
  • 250 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:South Africa
  • Local time:07:42 AM

Posted 30 December 2016 - 07:58 AM

Hi Al

 

I have tried so many permutations I'm not sure what the command was

I actually think it was sudo apt-get update, i will have to retrace my steps again.

 

My HDD is

931GB Seagate ST1000DM003-1SB10C (SATA)



#8 Al1000

Al1000

  • Global Moderator
  • 8,054 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:05:42 AM

Posted 30 December 2016 - 08:09 AM

I actually think it was sudo apt-get update


The output you saw is perfectly normal.

My HDD is

931GB Seagate ST1000DM003-1SB10C (SATA)


In that case, if this does turn out to be a HDD problem, you would want to run Seatools, and not WD Diagnostics. WD Disgnostics is for WD drives; Seatools is for Seagate drives.

What operating system are you using?

#9 rozzer

rozzer
  • Topic Starter

  • Members
  • 250 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:South Africa
  • Local time:07:42 AM

Posted 30 December 2016 - 08:22 AM

Hi Al

Just tried again and this is how I arrived there.

After trying Recovery mode then resume normal boot
Ctrl+alt+f1
Login in successfully and this is what I get:

Last login, Fri Dec 30th etc etc
Welcome to Linux Mint 17.1 Rebecca
(GNU/Linux 3.13.0 37 Generic _X86_64)
Welcome to Linux Mint
*Documentation HTTP://WWW Linuxmint.com

0 packages can be updated
0 updates are security updates

roy@roy desktop ~$

Shall I go ahead with running Seatools

Thanks again

Cheers

Edited by rozzer, 30 December 2016 - 08:25 AM.


#10 Al1000

Al1000

  • Global Moderator
  • 8,054 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:05:42 AM

Posted 30 December 2016 - 08:39 AM

No I wouldn't bother with Seatools unless this turns out to be a hardware issue, and I don't see anything indicating that it is.

Boot into tty1 then run this command:
startx
What happens?

#11 rozzer

rozzer
  • Topic Starter

  • Members
  • 250 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:South Africa
  • Local time:07:42 AM

Posted 30 December 2016 - 08:43 AM

Hi Al

I will not have enough time this evening to reply so will do
as you requested but it may be tomorrow before you get the reply

Cheers

Edited by rozzer, 30 December 2016 - 08:43 AM.


#12 rozzer

rozzer
  • Topic Starter

  • Members
  • 250 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:South Africa
  • Local time:07:42 AM

Posted 31 December 2016 - 01:06 AM

Hi again Al

I tried your suggestion 'startx' and it reverts me back to the original black screen.

Tried the recovery option several times, I notice that in about the first quarter of loading there is a 'FAIL'in red, I am unable to read anymore of it as it moves so rapidly, is there a way to pause it or to view the summary, I did try the summary in the options menu of recovery but screen gives a quick flash and nothing further.

Thanks again

Cheers

Edited by rozzer, 31 December 2016 - 01:08 AM.


#13 cat1092

cat1092

    Bleeping Cat


  • BC Advisor
  • 7,018 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:North Carolina, USA
  • Local time:01:42 AM

Posted 31 December 2016 - 03:06 AM

 

run WD diagnostics on the it to check for any bad sectors with their tool (has to be performed on a Windows computer).


WD diagnostics can also be run from a bootable DOS USB (that's how I've used it before), and of course is only intended to be run on Western Digital hard drives. According to his profile, rozzer is using a Seagate HDD.

 

 

Sorry about that, though the WD diagnostics tool can be used on most any drive, I believe Seatools can be also, though for best accuracy, it's always best to use the tool that the OEM supplies. :)

 

Cat


Performing full disc images weekly and keeping important data off of the 'C' drive as generated can be the best defence against Malware/Ransomware attacks, as well as a wide range of other issues. 


#14 Al1000

Al1000

  • Global Moderator
  • 8,054 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:05:42 AM

Posted 31 December 2016 - 03:17 AM

No problem, I didn't know WD Diagnostics could be used on any drive, as I've always gone for whatever tool the OEM supplies.

it's always best to use the tool that the OEM supplies.


Indeed. :)

#15 Al1000

Al1000

  • Global Moderator
  • 8,054 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:05:42 AM

Posted 31 December 2016 - 03:32 AM

is there a way to pause it or to view the summary


Yes, as with most things in Linux, there are a few ways. :)

The easiest way is to run this command:
dmesg | less
(the symbol between "dmesg" and "less" is called a pipe, and is the vertical line symbol on your keyboard)

"dmesg" is a file that contains all of the text that scrolls down the monitor during the boot process, and "less" is a text viewer in which to view the file.

When dmesg is open in less, use the up and down buttons on your keyboard to scroll through the text one line at a time, or use the space-bar to scroll down one screen at a time. To quit less and return to the command prompt, press the "q" button on your keyboard. (press "h" for more options)

If you don't find the line of text you're looking for, try this command:
dmesg | grep FAIL
The above command searches dmesg for lines containing instances of "FAIL" and displays the results.

Edited by Al1000, 31 December 2016 - 03:37 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users