We are in the process of migrating this forum. A new space will be available soon. We are sorry for the inconvenience.

Reboot Issue Freeze and bzimage ( CentOS )


msg7086
04/12/2014, 05h53
Check the drive health first. There's an admin page when booting into rescue mode.
Check the SMART data, read the data of 5 Reallocated_Sector_Ct.

To check and fix the partition, try fsck.
Be sure to google it throughly before doing so.
It may destroy your file system if it's severely damaged.

NLBlackEagle
03/12/2014, 19h24
Aha!


Can't open filesystem. Filesystem seems damaged.

I found this using testdisk. Now I need to find a way to solve the issue

NLBlackEagle
03/12/2014, 19h23
This is what I tried:

root@rescue:~# mount /dev/sda1 /mnt/
mount: block device /dev/sda1 is write-protected, mounting read-only
NTFS signature is missing.
Failed to mount '/dev/sda1': Invalid argument
The device '/dev/sda1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

root@rescue:~# mount /dev/sda /mnt/
mount: block device /dev/sda is write-protected, mounting read-only
NTFS signature is missing.
Failed to mount '/dev/sda': Invalid argument
The device '/dev/sda' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

root@rescue:~# fdisk -l
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sda1 1 3907029167 1953514583+ ee GPT
Partition 1 does not start on physical sector boundary.

root@rescue:~# mount /dev/sda /mnt/
mount: block device /dev/sda is write-protected, mounting read-only
NTFS signature is missing.
Failed to mount '/dev/sda': Invalid argument
The device '/dev/sda' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
root@rescue:~# NTFS signature is missing.
I also found something about testdisk, would this be the proper command to find/fix any issues on the HDD?

NLBlackEagle
03/12/2014, 19h19
This is what I tried:

root@rescue:~# mount /dev/sda1 /mnt/
mount: block device /dev/sda1 is write-protected, mounting read-only
NTFS signature is missing.
Failed to mount '/dev/sda1': Invalid argument
The device '/dev/sda1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

root@rescue:~# mount /dev/sda /mnt/
mount: block device /dev/sda is write-protected, mounting read-only
NTFS signature is missing.
Failed to mount '/dev/sda': Invalid argument
The device '/dev/sda' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

root@rescue:~# fdisk -l
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sda1 1 3907029167 1953514583+ ee GPT
Partition 1 does not start on physical sector boundary.

root@rescue:~# mount /dev/sda /mnt/
mount: block device /dev/sda is write-protected, mounting read-only
NTFS signature is missing.
Failed to mount '/dev/sda': Invalid argument
The device '/dev/sda' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
root@rescue:~# NTFS signature is missing.
I also found something about testdisk, would this be the proper command to find/fix any issues on the HDD?

NLBlackEagle
03/12/2014, 19h08
Well, I only got one parition and that's the main. However if I try to mount the partition this follows:

root@rescue:~# fdisk -l
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sda1 1 3907029167 1953514583+ ee GPT
Partition 1 does not start on physical sector boundary.

root@rescue:~# mount /dev/sda /mnt/
mount: block device /dev/sda is write-protected, mounting read-only
NTFS signature is missing.
Failed to mount '/dev/sda': Invalid argument
The device '/dev/sda' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
root@rescue:~# NTFS signature is missing.
I found something about testdisk. Is this a proper way to check the hard drive health?

NLBlackEagle
03/12/2014, 19h06
Post needs to be approved my moderator.. Hmm Im new to this, anyway. Im currently following this tutorial: http://help.ovh.com/RescueMode#link6

root@rescue:~# fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sda1 1 3907029167 1953514583+ ee GPT
Partition 1 does not start on physical sector boundary.


When I put in the following command:

root@rescue:~# mount /dev/sda1

It says this:

mount: can't find /dev/sda1 in /etc/fstab or /etc/mtab

I'm not experienced with this but shouldnt that be dev/sda1 instead of /etc/fstab or /etc/mtab?

NLBlackEagle
03/12/2014, 18h58
Post needs to be approved my moderator.. Hmm Im new to this, anyway. Im currently following this tutorial: http://help.ovh.com/RescueMode#link6

root@rescue:~# fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sda1 1 3907029167 1953514583+ ee GPT
Partition 1 does not start on physical sector boundary.


When I put in the following command:

root@rescue:~# mount /dev/sda1

It says this:

mount: can't find /dev/sda1 in /etc/fstab or /etc/mtab

I'm not experienced with this but shouldnt that be dev/sda1 instead of /etc/fstab or /etc/mtab?

NLBlackEagle
03/12/2014, 18h52
root@rescue:~# fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sda1 1 3907029167 1953514583+ ee GPT
Partition 1 does not start on physical sector boundary.

NLBlackEagle
03/12/2014, 18h52
I dont have any partitions:


root@rescue:~# fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sda1 1 3907029167 1953514583+ ee GPT
Partition 1 does not start on physical sector boundary.

msg7086
03/12/2014, 18h41
In rescue mode you need to mount the partition onto directory by hand. (google mount partition)

You need to check the hard drive health as well. A failed HDD may prevent system from booting.

NLBlackEagle
03/12/2014, 18h33
Hello everyone,

I have encountered a issue while working on my server, it suddently aborted the connection so I did a hard reboot and these errors followed:

Logs:
----------------------
PING ns321835.ip-213-251-186.eu (213.251.186.118) from 213.186.33.13 : 56(84) bytes of data.
From 213.186.33.13: Destination Host Unreachable
From 213.186.33.13: Destination Host Unreachable
From 213.186.33.13: Destination Host Unreachable

--- 213.251.186.118 ping statistics ---
10 packets transmitted, 0 packets received, +6 errors, 100% packet loss
---------------------

The intervention on ns321835.ip-213-251-186.eu has been completed.

This operation was closed at 2014-12-03 17:15:47

Here are the details of this operation:
Diagnosis interface boot (rescue)
Date 2014-12-03 17:15:25, mikael.tonetti made Diagnosis interface boot (rescue):
Here are the details of the operation performed:
The server gets stuck during the boot phase, with the message:
(freeezze en bzimage )
A restart on the standard OVH kernel ('netboot') does not correct the
situation.

Actions:
Rebooting the server to "rescue" mode (Linux)

result:
Boot OK. Rescue mode accessible.

recommendations:
Configuration / error to be corrected by the customer


I would like to get this fixed, either by a paying for it or could anyone guide me trough if this isnt a hard to solve issue?

Also, using the rescue metod I can't find my server files to make a backup. Are they gone?