Can't boot from LiveCD Caine 3.0

View previous topic View next topic Go down

Can't boot from LiveCD Caine 3.0

Post  wechse5 on Fri Oct 05, 2012 3:21 pm

I use a System with dual boot (Win7 and Linux) on a computer. The Boot - Manager are Grub.

The computer has 6 harddisk (one 2 TB).
The first disk (sda) have the both systems (win and linux) and the follow partitions

/dev/sda1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
/dev/sda2 206848 1048784895 524289024 7 HPFS/NTFS/exFAT
/dev/sda3 1048786942 3907028143 1429120601 5 Erweiterte
/dev/sda5 1048786944 3001911943 976562500 7 HPFS/NTFS/exFAT
/dev/sda6 3001913344 3001944063 15360 82 Linux Swap / Solaris
/dev/sda7 3001946112 3907028143 452541016 83 Linux

The disk 2 - 6 are a fake-raid0 under windows. I can mount an read/write the partition (~ 9 TB with NTFS - FileSystem) under the installed linux (ubuntu 11.x).

With the livecd I cant boot this system nor caine 3.0 install. After the booting process stops the system with a flashing screen.

from the installed linux I make the command:
dmesg | grep "sd"

950269] sd 2:0:0:0: Attached scsi generic sg2 type 0
[ 1.950408] sd 2:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[ 1.950592] sd 2:0:0:0: [sda] Write Protect is off
[ 1.950597] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.950985] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.002541] sda: sda1 sda2 sda3 < sda5 sda6 sda7 >
[ 2.003399] sd 2:0:0:0: [sda] Attached SCSI disk
[ 2.444538] sd 3:0:0:0: Attached scsi generic sg3 type 0
[ 2.444700] sd 3:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[ 2.445027] sd 3:0:0:0: [sdb] Write Protect is off
[ 2.445032] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 2.445078] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.454079] sdb: unknown partition table
[ 2.454538] sd 3:0:0:0: [sdb] Attached SCSI disk
[ 2.956083] sd 4:0:0:0: Attached scsi generic sg4 type 0
[ 2.956217] sd 4:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[ 2.956639] sd 4:0:0:0: [sdc] Write Protect is off
[ 2.956651] sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 2.956804] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.968296] sdc: unknown partition table
[ 2.968862] sd 4:0:0:0: [sdc] Attached SCSI disk
[ 3.454931] sd 5:0:0:0: Attached scsi generic sg5 type 0
[ 3.455070] sd 5:0:0:0: [sdd] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[ 3.455365] sd 5:0:0:0: [sdd] Write Protect is off
[ 3.455377] sd 5:0:0:0: [sdd] Mode Sense: 00 3a 00 00
[ 3.455506] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 3.473529] sdd: unknown partition table
[ 3.474029] sd 5:0:0:0: [sdd] Attached SCSI disk
[ 3.953753] sd 6:0:0:0: Attached scsi generic sg6 type 0
[ 3.953871] sd 6:0:0:0: [sde] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[ 3.954207] sd 6:0:0:0: [sde] Write Protect is off
[ 3.954213] sd 6:0:0:0: [sde] Mode Sense: 00 3a 00 00
[ 3.954347] sd 6:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 3.970305] sde: unknown partition table
[ 3.971125] sd 6:0:0:0: [sde] Attached SCSI disk
[ 4.452745] sd 7:0:0:0: Attached scsi generic sg7 type 0
[ 4.452817] sd 7:0:0:0: [sdf] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[ 4.453139] sd 7:0:0:0: [sdf] Write Protect is off
[ 4.453144] sd 7:0:0:0: [sdf] Mode Sense: 00 3a 00 00
[ 4.453359] sd 7:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 4.473727] sdf: unknown partition table
[ 4.474547] sd 7:0:0:0: [sdf] Attached SCSI disk
[ 5.340101] EXT4-fs (sda7): INFO: recovery required on readonly filesystem
[ 5.340106] EXT4-fs (sda7): write access will be enabled during recovery
[ 6.764140] EXT4-fs (sda7): recovery complete
[ 6.766216] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null)
[ 11.265008] Adding 15356k swap on /dev/sda6. Priority:-1 extents:1 across:15356k
[ 11.855212] EXT4-fs (sda7): re-mounted. Opts: errors=remount-ro
[ 32.499439] EXT4-fs (sda7): re-mounted. Opts: errors=remount-ro,commit=0

also the command
fdisk -lu


Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255 Köpfe, 63 Sektoren/Spur, 243201 Zylinder, zusammen 3907029168 Sektoren
Einheiten = Sektoren von 1 × 512 = 512 Bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x70855bc8

Gerät boot. Anfang Ende Blöcke Id System
/dev/sda1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
/dev/sda2 206848 1048784895 524289024 7 HPFS/NTFS/exFAT
/dev/sda3 1048786942 3907028143 1429120601 5 Erweiterte
/dev/sda5 1048786944 3001911943 976562500 7 HPFS/NTFS/exFAT
/dev/sda6 3001913344 3001944063 15360 82 Linux Swap / Solaris
/dev/sda7 3001946112 3907028143 452541016 83 Linux

Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 Köpfe, 63 Sektoren/Spur, 243201 Zylinder, zusammen 3907029168 Sektoren
Einheiten = Sektoren von 1 × 512 = 512 Bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Gerät boot. Anfang Ende Blöcke Id System
/dev/sdb1 1 4294967295 2147483647+ ee GPT

Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
255 Köpfe, 63 Sektoren/Spur, 243201 Zylinder, zusammen 3907029168 Sektoren
Einheiten = Sektoren von 1 × 512 = 512 Bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes
255 Köpfe, 63 Sektoren/Spur, 243201 Zylinder, zusammen 3907029168 Sektoren
Einheiten = Sektoren von 1 × 512 = 512 Bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/sde: 2000.4 GB, 2000398934016 bytes
255 Köpfe, 63 Sektoren/Spur, 243201 Zylinder, zusammen 3907029168 Sektoren
Einheiten = Sektoren von 1 × 512 = 512 Bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/sdf: 2000.4 GB, 2000398934016 bytes
255 Köpfe, 63 Sektoren/Spur, 243201 Zylinder, zusammen 3907029168 Sektoren
Einheiten = Sektoren von 1 × 512 = 512 Bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/mapper/isw_bjgdjhjdbb_Volume_0000: 10002.0 GB, 10001983733760 bytes
255 Köpfe, 63 Sektoren/Spur, 1216005 Zylinder, zusammen 19535124480 Sektoren
Einheiten = Sektoren von 1 × 512 = 512 Bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 131072 bytes / 655360 bytes
Disk identifier: 0x00000000

Gerät boot. Anfang Ende Blöcke Id System
/dev/mapper/isw_bjgdjhjdbb_Volume_0000p1 1 4294967295 2147483647+ ee GPT
Partition 1 does not start on physical sector boundary.

Platte /dev/mapper/isw_bjgdjhjdbb_Volume_0000-part1: 134 MByte, 134217728 Byte
255 Köpfe, 63 Sektoren/Spur, 16 Zylinder, zusammen 262144 Sektoren
Einheiten = Sektoren von 1 × 512 = 512 Bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 131072 bytes / 655360 bytes
Alignment offset: 113664 bytes
Disk identifier: 0x00000000


Disk /dev/mapper/isw_bjgdjhjdbb_Volume_0000-part2: 10001.8 GB, 10001846370304 bytes
255 Köpfe, 63 Sektoren/Spur, 1215988 Zylinder, zusammen 19534856192 Sektoren
Einheiten = Sektoren von 1 × 512 = 512 Bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 131072 bytes / 655360 bytes
Disk identifier: 0x66205247

Das sieht nicht wie eine Partitionstabelle aus.
Sie haben wahrscheinlich das falsche Gerät ausgewählt.

Gerät boot. Anfang Ende Blöcke Id System
/dev/mapper/isw_bjgdjhjdbb_Volume_0000-part2p1 ? 1380404564 3216423027 918009232 a OS/2 Bootmanager
Partition 1 does not start on physical sector boundary.
/dev/mapper/isw_bjgdjhjdbb_Volume_0000-part2p2 ? 1309281536 3263005284 976861874+ 69 Unbekannt
/dev/mapper/isw_bjgdjhjdbb_Volume_0000-part2p3 ? 1735554131 3688805757 976625813+ 6d Unbekannt
Partition 3 does not start on physical sector boundary.
/dev/mapper/isw_bjgdjhjdbb_Volume_0000-part2p4 ? 2978742282 2978797514 27616+ 66 Unbekannt
Partition 4 does not start on physical sector boundary.

Partitionstabelleneinträge sind nicht in Platten-Reihenfolge

regards

K.W.

ps: by translate.google.com



wechse5

Number of posts : 8
Registration date : 2010-03-30

View user profile

Back to top Go down

Re: Can't boot from LiveCD Caine 3.0

Post  slo.sleuth on Fri Oct 05, 2012 6:24 pm

If you are booting Caine from a CD-ROM, then your hard disk structure and the number of hard disks is irrelevant. Therefore, I can't tell what the exact problem is from the information you provided.

The issue is likely related to your graphics card. You can try to boot Caine in "safe mode" and if that fails, try passing the nomodeset grub boot option (for nvidia graphics).

Caine might also fail to boot a graphical desktop if you run out of RAM or have bad RAM. Booting in text mode is an effective way to use Caine in low RAM systems or when you have incompatible graphics cards.
avatar
slo.sleuth

Number of posts : 43
Registration date : 2009-03-31

View user profile http://linuxsleuthing.blogspot.com

Back to top Go down

Re: Can't boot from LiveCD Caine 3.0

Post  nannib on Fri Oct 05, 2012 7:46 pm

Check your caine3.0.iso MD5 hash code.
Try to re-burn your dvd....maybe it's corrupted.
bye

Nanni Bassetti

_________________
-------------------------
Nanni Bassetti
Caine Project Manager
http://www.nannibassetti.com
avatar
nannib
Admin

Number of posts : 273
Age : 47
Registration date : 2008-10-28

View user profile http://www.nannibassetti.com/

Back to top Go down

Re: Can't boot from LiveCD Caine 3.0

Post  wechse5 on Mon Oct 08, 2012 12:32 pm

I think the problem is the graphic card. it's a Matrox Millenium P 960 PCIe x16.
I will replace them.

How can I start the installation from the console after boot in a safe mode?
I will it test with the matrox card (before replace).

thanks
K.W.


Last edited by wechse5 on Mon Oct 08, 2012 1:24 pm; edited 1 time in total

wechse5

Number of posts : 8
Registration date : 2010-03-30

View user profile

Back to top Go down

Re: Can't boot from LiveCD Caine 3.0

Post  nannib on Mon Oct 08, 2012 12:39 pm

Excuse me but the:
"dmesg | grep "sd"
message you post here...has been made from your Ubuntu Linux system not from Caine Live cd? Is it right?
Thanks


_________________
-------------------------
Nanni Bassetti
Caine Project Manager
http://www.nannibassetti.com
avatar
nannib
Admin

Number of posts : 273
Age : 47
Registration date : 2008-10-28

View user profile http://www.nannibassetti.com/

Back to top Go down

Re: Can't boot from LiveCD Caine 3.0

Post  wechse5 on Mon Oct 08, 2012 1:21 pm

nannib wrote:Excuse me but the:
"dmesg | grep "sd"
message you post here...has been made from your Ubuntu Linux system not from Caine Live cd? Is it right?
Thanks


yes. lubuntu 11.10.

K.W.

wechse5

Number of posts : 8
Registration date : 2010-03-30

View user profile

Back to top Go down

Re: Can't boot from LiveCD Caine 3.0

Post  slo.sleuth on Mon Oct 08, 2012 9:48 pm

wechse5 wrote:
How can I start the installation from the console after boot in a safe mode?
I will it test with the matrox card (before replace).

In short, you can install from the boot menu "install" option. If that fails to start, you would be best to solve your graphics card issues before you try to install Caine. While it is possible to install from the command line, the process is more extensive and you will still not have a graphical desktop until you fix the issue with your graphics card. Search the Ubuntu forums with your graphics card model and you're very likely to find a solution




I think this would be a good place to discuss Caine boot options and solving boot problems. If you are interested, please read on:

In the Caine 3.0 boot (grub) menu, you have several boot options to try:
  • live - Caine will try to detect your graphics card and boot into a graphical desktop (works almost every time, newer hardware could be a problem
  • xforcevesa - Caine will use basic graphics driver supported by nearly all graphics cards, resolutions and refresh rates may not be desireable
  • textonly - Caine does not boot into a graphical desktop
  • nomodeset - Caine will not let the kernel handle the display settings and will pass the responsibility to the X server. This option will usually solve booting to a "blank" screen problems
  • debug - Caine will display startup messages to try to help you determine the source of your boot problem
  • install - start a graphical installer directly: may not work if you are having graphics cards issues, but don't assume that.
  • memtest - Since Caine Live runs in a RAM disk, you can test that boot problems aren't the result of bad memory
  • hd - Caine will try to boot from the first detected drive, rather than boot the Caine Live OS. Use with caution!

Generally, the order to try booting is as follows:
  1. live
  2. xforcevesa
  3. nomodeset
  4. textonly #still allows for the running of command line tools, so imaging and sleuthkit examinations are still very possible.

If you have an exotic (meaning: unsupported) graphics card on a computer you wish to install Caine, research the card online in relation to grub boot options. If you find a solution, you can pass the boot options to Caine by pressing TAB in the boot menu to add the option to an existing boot option (press ESC to return to the boot menu). Alternatively, you can pass an entirely custom boot option by pressing ESC (press enter on a blank line to return to the boot menu). Some of the boot codes you might need to try are:
  • older Intel devices: i915.modeset=1 or i915.modeset=0
  • nVidia: nomodeset
  • Generic: xforcevesa or nouveau.modeset=0
  • Radeon: radeon.modeset=0

Once you determine the appropriate boot option, you can make it permanent on installed CAINE by editing the '/etc/default/grub' file. You can add the boot option to the GRUB_CMDLINE_LINUX_DEFAULT setting. For example, to add 'nomodeset',

change:
Code:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to:
Code:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"
Whatever change you make, you must update grub for it to take effect:
Code:
$ sudo update-grub
$ sudo reboot
Finally, two more boot options can help if the boot freezes before you reach the desktop of terminal: 'noapic' and 'nolapic'. These will generally skirt problems with power control conflicts between Linux and the bios that can halt the booting process.
avatar
slo.sleuth

Number of posts : 43
Registration date : 2009-03-31

View user profile http://linuxsleuthing.blogspot.com

Back to top Go down

Re: Can't boot from LiveCD Caine 3.0

Post  Sponsored content


Sponsored content


Back to top Go down

View previous topic View next topic Back to top

- Similar topics

 
Permissions in this forum:
You cannot reply to topics in this forum