Pc not starting after power failure

English Install/Boot/Login
1

hello,
my pc power went dead (it exploded :’( ) , i bought a new one but since then i have this error at start :

doing fast boot
              creating devices node with udev
              welcome to emergency mode, use systemctl default or ^D to               enter default mode

          then with ^D i have : 

failed to enqueue onfailure= job: invalid argument

also one disk is not displayed anymore in fdisk-l, i’ll have to check all the sata/ide connections to be sure if it’s dead or not.

how can i solve this please ? (if the missing disk is dead for example)

Thanks :wink:

2

On 12/16/2012 10:06 PM, manchette fr wrote:
> how can i solve this please ?

note: i’ve used Linux since '98 and i’ve seen those kinds of error
messages before, so all i can say is:

if, as the power supply exploded it sent a sharp/spiked over voltage to
the mother board, drives, and etc–there is no telling what might be
ruined…

i mean, it might have burned out components on the main board as well
as the small controller boards in the drives, the networking, sound,
graphics parts of the MB…or the whole graphics card (if you have one
of those)

you may not know it, but the spark from static electricity from your
finger is enough to KILL a CPU or RAM stick…depending on where it
gets to…

if it were my machine i think i’d find someone (or more likely a repair
shop) who could trouble shoot the system…and give an estimate to
repair it…

but! how old is it? you might be better off taking the drives out
(hoping you can get your data off it) and throw the rest away…

i mean, the repair shop might charge you a good percentage of what it
will cost for you to find a new machine…OR, maybe catch a used one
somewhere…

BUT, i can’t make that decision from here…who knows, the symptom you
are having might be ONE very inexpensive and quick repair…but, it
sure SOUNDS bad to me.

suggest you wait around until more have pitched their opinions at you…

–
dd http://tinyurl.com/DD-Caveat

3

I have had the Power Supply fail on one PC running openSUSE and the hard disk partition was messed up. As luck would have it, my /home was OK (on a second hard drive), but I got to reload and reformat the root / partition drive. The drive was not physically damaged, but no data on it was usable until all partitions were redone. At first, I just redid the root / partition, but I continued to get warnings from the YaST Partitioner until I took all the way to zero and restarted over.

Thank You,

4

On 2012-12-16 22:06, manchette fr wrote:

> then with ^D i have :

You are expected to solve the issue, then press ^D to continue. Pressing
it before does nothing useful.

Unfortunately, systemd doesn’t give much clues about what the problem
may be. You can try booting in systemv mode instead.

> also one disk is not displayed anymore in fdisk-l, i’ll have to check
> all the sata/ide connections to be sure if it’s dead or not.

I’d guess that you have to remove the corresponding entry from fstab.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

5

hi,

i checked the sata/ide connections and pc boot ok as usual … this untill today when i had the same errors and pc not booting untill i # 'ed an entry in fstab


cat /etc/fstab
/dev/disk/by-id/ata-WDC_WD1600PD-07FZB1_WD-WMAES3562221-part2 /                    ext4       acl,user_xattr        1 1
/dev/disk/by-id/ata-WDC_WD1600PD-07FZB1_WD-WMAES3562221-part1 swap                 swap       defaults              0 0
/dev/disk/by-id/ata-WDC_WD1600PD-07FZB1_WD-WMAES3562221-part3 /home                ext4       acl,user_xattr        1 2
/dev/disk/by-id/ata-ST3320620AS_9QF5PH60-part2 /osvirtuels          ext4       acl,user_xattr        1 2
/dev/disk/by-id/ata-ST3320620AS_9QF5PH60-part1 /stockage1           ext4       defaults              1 2
/dev/disk/by-id/ata-SAMSUNG_HD103UJ_S13PJ90S208022-part1 /stockage2           ext4       defaults              1 2
#/dev/disk/by-id/ata-WDC_WD1600PD-07FZB1_WD-WMAES3561246-part1 /stockage3           ext4       defaults              1 2
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0

i have 4 hdds :
WD1 160 gb
WD2 160 gb
Seagate 320 gb
Samsung 1 Tb

now only 3 hdds appear in fdisk -l (when all of them where there yesterday) :


# fdisk -l

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders, total 312581808 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: 0x20e3865f

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1       306280448   312580095     3149824   82  Linux swap / Solaris
/dev/sda2   *     4209030    67119569    31455270   83  Linux
/dev/sda3        67119570   306279224   119579827+  83  Linux

Partition table entries are not in disk order

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 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: 0x000c1b47                                                                                                                                 
                                                                                                                                                            
   Device Boot      Start         End      Blocks   Id  System                                                                                              
/dev/sdc1              63  1953520064   976760001   83  Linux                                                                                               

Disk /dev/sdb: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 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: 0x00072096

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1              63   415248119   207624028+  83  Linux
/dev/sdb2   *   415248120   625137344   104944612+  83  Linux

is there a way to check is the disk is still alive without trying it in another machine ?

thanks ;=)

6

For your fstab, you can add the option nofail, to allow you to keep going. You can also try a liveCD, but it sounds like your hard drive partition is not loading. You can use the partitioner to create a new one perhaps. But if the drive is not there at all it may have failed.

Thank You,

7

Do you mean that ‘no fail’ option in fstab is the way so that the os boots even if the disk fails ?
how shall i write this ?

I was wondering if a live cd as gparted and the like could see anyhting when bios and os can’t.

I shall try the partitioner too , good idea.

8

On 2012-12-19 13:36, manchette fr wrote:
>
> Do you mean that ‘no fail’ option in fstab is the way so that the os
> boots even if the disk fails ?
> how shall i write this ?

It is in the man.


>   /dev/whateverdevice  /mountpoint   ext4   defaults,nofail    1 2

>
> I was wondering if a live cd as gparted and the like could see anyhting
> when bios and os can’t.

If the bios does not see the disk, you can’t do anything.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

9

well i understand that with nofail option in fstab i will boot if a disk is ko, but on the other way i loose some important check informations. Is there a way to use nofail so that i can boot and use the pc as usual but still gather the errors in another way ?

someone told me that pata disks where both masters and the 2d one was not seen, it is possible for sata disks ?

10

[QUOTE=manchette_fr;2511992]

replace last sentence with : someone told me that pata disks where both masters and the 2d one was not seen,
but here i have 2 sata and 2 ide disks , 1 ide is missing, i did not change the settings i had before , might this apply ?

11

On 12/19/2012 12:06 PM, manchette fr wrote:
>
> manchette_fr;2511992 Wrote:
>>
>>
>> replace last sentence with : someone told me that pata disks where
>> both masters and the 2d one was not seen,
>> but here i have 2 sata and 2 ide disks , 1 ide is missing, i did not
>> change the settings i had before , might this apply ?

If both IDE disks were seen before the power failure, then that does not apply.

My impression is that one of your hard drives did not survive the power shock. I
hope you have a backup of that data.

12

On 2012-12-19 18:56, manchette fr wrote:
>
> well i understand that with nofail option in fstab i will boot if a disk
> is ko, but on the other way i loose some important check informations.
> Is there a way to use nofail so that i can boot and use the pc as usual
> but still gather the errors in another way ?

With the nofail option, if the disk is not present you get no warning,
but this is preferable, IMO, to not booting. You can, of course, create
your own scripts and do the checking.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

13

hi,
so is nofail option only adressing hardware failures ? (meaning that if no disk is seen it will not impede boot but also that with nofail option all the other controls are still done as usual when the disk is ok : filesystems and other tests).

If these controls are not when using nofail i 'd be interested knowing the kind of tests that would be interesting and why not try to set them up in scripts.

14

On 2012-12-21 14:26, manchette fr wrote:
>
> hi,
> so is nofail option only adressing hardware failures ?

No. It simply means that if there is any kind of error when mounting a
filesystem, for whatever reason, you will not see the error, and the
operation will not abort.

You get no feedback at all regardless of success or failure, that is up
to you to find out.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))