PANIC after clean install
- Thread starter docmattman
- Start date
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
A little more info... I can boot from the cd if I enter at the boot prompt:
pveboot nomodeset
This spits out a lot of stuff on the screen that I don't have time to read, but eventually it comes to this:
Activating lvm and md swap...done.
Checking file system...fsck from util-linux-ng 2.17.2
fsck.ext4: No such file or directory while trying to open /dev/pve/data
/dev/pve/data:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8103 <device>
/dev/sda1: clean, 230/131072 files, 75707/52364 blocks
fsck died with exit status 8
failed (code 8).
File system check failed. A log is being saved in /var/log/fsck/checkfs if that
location is writable. Please repair the file system manually. ... failed!
A maintenance shell will now be started. CONTROL-D will terminate this shell and
resume system boot. ... (warning).
Give root password for maintenance
(or type Control-D to continue):
If I type Ctrl-D, it continues to the pve with the message to use the web browser and shows the IP and login. When I open it up in my browser, it seems to work, as I get the interface and all that. I just still can't figure out how to boot to pve without going this method with the cd. Does the above information spark any new ideas?
pveboot nomodeset
This spits out a lot of stuff on the screen that I don't have time to read, but eventually it comes to this:
Activating lvm and md swap...done.
Checking file system...fsck from util-linux-ng 2.17.2
fsck.ext4: No such file or directory while trying to open /dev/pve/data
/dev/pve/data:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8103 <device>
/dev/sda1: clean, 230/131072 files, 75707/52364 blocks
fsck died with exit status 8
failed (code 8).
File system check failed. A log is being saved in /var/log/fsck/checkfs if that
location is writable. Please repair the file system manually. ... failed!
A maintenance shell will now be started. CONTROL-D will terminate this shell and
resume system boot. ... (warning).
Give root password for maintenance
(or type Control-D to continue):
If I type Ctrl-D, it continues to the pve with the message to use the web browser and shows the IP and login. When I open it up in my browser, it seems to work, as I get the interface and all that. I just still can't figure out how to boot to pve without going this method with the cd. Does the above information spark any new ideas?
Here is the readout of the fdisk command in case it helps anything:
root@master:~# fdisk -l
Disk /dev/sda: 499.6 GB, 499558383616 bytes
255 heads, 63 sectors/track, 60734 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00080550
Device Boot Start End Blocks Id System
/dev/sda1 * 1 66 523264 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 66 60735 487325696 8e Linux LVM
Disk /dev/dm-0: 33.3 GB, 33285996544 bytes
255 heads, 63 sectors/track, 4046 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1: 103.1 GB, 103079215104 bytes
255 heads, 63 sectors/track, 12532 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/dm-1 doesn't contain a valid partition table
Disk /dev/dm-2: 345.5 GB, 345476431872 bytes
255 heads, 63 sectors/track, 42001 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/dm-2 doesn't contain a valid partition table
root@master:~# fdisk -l
Disk /dev/sda: 499.6 GB, 499558383616 bytes
255 heads, 63 sectors/track, 60734 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00080550
Device Boot Start End Blocks Id System
/dev/sda1 * 1 66 523264 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 66 60735 487325696 8e Linux LVM
Disk /dev/dm-0: 33.3 GB, 33285996544 bytes
255 heads, 63 sectors/track, 4046 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1: 103.1 GB, 103079215104 bytes
255 heads, 63 sectors/track, 12532 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/dm-1 doesn't contain a valid partition table
Disk /dev/dm-2: 345.5 GB, 345476431872 bytes
255 heads, 63 sectors/track, 42001 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/dm-2 doesn't contain a valid partition table
Is there anymore information I can post here that would be helpful in trying to solve this issue? I'd love to get this up and running as soon as I can. It feels like I'm very close here, just need to solve the boot problem...
Install latest BIOS version: http://www.dell.com/support/drivers...?driverId=29KNC&osCode=W764&fileId=2992765419
AFAIK you will need to install windows first and then run update Bios.
AFAIK you will need to install windows first and then run update Bios.
I already have the latest bios installed.
Unfortunately I don't have very in depth knowledge of Linux, but it seems like I'm very close to solving my problem. Since I can use "pveboot" from the PVE 2.1 disc, it will get me booted into the system, but booting from Grub still gives me the PANIC error. So I'm thinking that I just need to configure Grub somehow to look for the proper disk partition for the root system. I just don't know much about configuring Grub. I'm not even sure what to try to get it working. But since I can install PVE and boot to it using "pveboot" from the disc, it makes me think that PVE is fine with the RAID controller I have. Any advice for getting Grub to boot to pve properly?
Unfortunately I don't have very in depth knowledge of Linux, but it seems like I'm very close to solving my problem. Since I can use "pveboot" from the PVE 2.1 disc, it will get me booted into the system, but booting from Grub still gives me the PANIC error. So I'm thinking that I just need to configure Grub somehow to look for the proper disk partition for the root system. I just don't know much about configuring Grub. I'm not even sure what to try to get it working. But since I can install PVE and boot to it using "pveboot" from the disc, it makes me think that PVE is fine with the RAID controller I have. Any advice for getting Grub to boot to pve properly?
I noticed that PVE 2.2 was released. I was hoping that the new release would solve my problem. But, unfortunately, I am still getting the same results. Are there any GRUB experts out there that can help me out? I really need to get this up and running on several of my servers.
If there is no advice to get it running, would anyone know where I can go to get more answers? I'm pretty sure it's boiled down to a GRUB issue now. If there is a better place to ask these questions, please let me know.
If there is no advice to get it running, would anyone know where I can go to get more answers? I'm pretty sure it's boiled down to a GRUB issue now. If there is a better place to ask these questions, please let me know.