| View previous topic :: View next topic |
| Author |
Message |
ckoeber
Apprentice
Joined: 21 May 2007
Posts: 156
|
 Posted: Tue Feb 12, 2013 11:45 pm Post subject: |
 |
|
| BillWho wrote: | What does fdisk -l report - I've never had output like that from sfdisk  |
fdisk -l:
| Code: | Disk /dev/sda: 1099.5 GB, 1099511627776 bytes
255 heads, 63 sectors/track, 133674 cylinders, total 2147483648 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: 0xb38b7adc
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 206847 102400 83 Linux
/dev/sda2 206848 8599551 4196352 82 Linux swap / Solaris
/dev/sda3 8599552 2147483647 1069442048 83 Linux
|
|
|
| Back to top |
|
 |
BillWho
Veteran
Joined: 03 Mar 2012
Posts: 1600
Location: US
|
| Posted: Wed Feb 13, 2013 12:35 am Post subject: |
|
|
It looks like sfdisk detected a /sda4, but not fdisk.
Just to leave no stone unturned, how would you feel doing a e2fsck -f -ckPv /dev/sda3 
I can't think of anything else at this time. When I had that error with sabayon, the kernel continued on its way after entering the root block device /dev/sda3.
_________________
Good luck 
Since installing gentoo, my life has become one long emerge  |
|
| Back to top |
|
|
ckoeber
Apprentice
Joined: 21 May 2007
Posts: 156
|
| Posted: Wed Feb 13, 2013 1:01 am Post subject: |
|
|
| BillWho wrote: | It looks like sfdisk detected a /sda4, but not fdisk.
Just to leave no stone unturned, how would you feel doing a e2fsck -f -ckPv /dev/sda3
I can't think of anything else at this time. When I had that error with sabayon, the kernel continued on its way after entering the root block device /dev/sda3. |
OK, a funny thing happened; I basically went back to my kernel config file, went over practically every device driver option and set the ones I needed as built-in.
Now the kernel boots.
So I must not have set an option correctly.
In short, SOLVED.
Thank you for all of your help. |
|
| Back to top |
|
|
BillWho
Veteran
Joined: 03 Mar 2012
Posts: 1600
Location: US
|
| Posted: Wed Feb 13, 2013 1:10 am Post subject: |
|
|
Good to hear you got it going 
Do you remember which ones you changed I'm looking at it here and didn't notice anything that would cause that error, but maybe because it's on the hyper-v
_________________
Good luck
Since installing gentoo, my life has become one long emerge |
|
| Back to top |
|
|
ckoeber
Apprentice
Joined: 21 May 2007
Posts: 156
|
| Posted: Wed Feb 13, 2013 1:18 am Post subject: |
|
|
| BillWho wrote: | Good to hear you got it going
Do you remember which ones you changed I'm looking at it here and didn't notice anything that would cause that error, but maybe because it's on the hyper-v |
Yes, I believe one of the Hyper-V utility drivers wasn't set, and that needs to be loaded for the storage modules to work. |
|
| Back to top |
|
|
BillWho
Veteran
Joined: 03 Mar 2012
Posts: 1600
Location: US
|
| Posted: Wed Feb 13, 2013 1:23 am Post subject: |
|
|
I'll bet that was the scsi storage in device drivers
Symbol: HYPERV_STORAGE [=n] │
│ Type : tristate │
│ Prompt: Microsoft Hyper-V virtual storage driver │
│ Defined at drivers/scsi/Kconfig:650 │
│ Depends on: SCSI_LOWLEVEL [=n] && SCSI [=y] && HYPERV [=n] │
│ Location: │
│ -> Device Drivers │
│ -> SCSI device support │
│ -> SCSI low-level drivers (SCSI_LOWLEVEL [=n]) │
│
I was just going to suggest that when I saw you got it working
_________________
Good luck
Since installing gentoo, my life has become one long emerge |
|
| Back to top |
|
|
|
Installing Gentoo
