[Now solved] MiniMe Graphics crash on start

[wedgetail]

Final status

Sunday, 22 May 2011

The problem turned out to be the order of HDD1, HDD2 and USB_HDD, If I had been a bit more attentive to the BIOS arrangement in this computer, I may have found out a lot earlier. Reading one of old-polack's tutorials on BIOS - GRUB operation did not sink in early enough to prevent me spending a lot of time on this.  

At least I now know it was not intermittent problem with the hard drive (fairly new 1 GB unit), knowing is fair consolation for me.

Update status

If you com across this topic:
The problem seems to change until it settled to very repeatable behavior. No longer able to make an install from a LiveCD.

I have found out that it has something to do with /dev/sdb the second hard drive, but only in this computer. Inserted into another comparable but not identical system I have not yet detected any problem.

Removing the drive and I can install to the first drive. Making the drive the first and only drive it will work, any other combination on this PC and the problem is there. Along the testing route member as pointed out that the grub session at the end of an install when trying to write the menu.lst update meets an unexpected problem and sits an waits.  I have not had patient to wait more than ten minutes at most.

When it fails the target drive for an install can not be unmounted, as I have been using a root konsole and {draklive-install} I find that despite grub session 'hanging' the konsole prompt is returned. It is at that stage I have tried the {umount -a}

< ----------------------------------------------- >
< ----------------------------------------------- >

I have a MiniMe system that I am using as test system for various test program installs before installing in KDE

Been working great but now suddenly it boots me to text login. In verbose booting I notice a lot of lines with "cannot create temp.."  

I can log in as root ok, attempt startx and managed to catch following:

/usr/bin/startx: line 142: cannot create temp file for here-document: Read-only file system
xauth:  error in locking authority file /root/.Xauthority
/usr/bin/startx: line 158: cannot create temp file for here-document: Read-only file system
xauth:  error in locking authority file /root/.Xauthority
/usr/bin/startx: line 158: cannot create temp file for here-document: Read-only file system


Fatal server error:
Could not create lock file in /tmp/.tX0-lock


Please consult the The X.Org Foundation support
    at http://pclinuxos.com
 for help.

giving up.

xinit:  No such file or directory (errno 2):  unable to connect to X server

xinit:  No such process (errno 3):  Server error.
xauth:  error in locking authority file /root/.Xauthority

If I try to run {video} I get following:

-bash: video: command not found

[/quote]

Suggestions to get me out of this pickle most welcome, I am fretting a bit as I am right in the middle of some serious testing of LiveHDD install

[Old-Polack]

wedgetail:

Boot to the liveCD, open a terminal, su to root, then;

[root@localhost ~]# fsck -f /dev/<whatever>                    <Enter>

Replace <whatever> with the proper / partition on the hard drive. When the filesystem has been fixed, the partition should then mount rw, and you should be able to login properly.

[wedgetail]

old-polack
Thanks, I am rescuing a few files from the partition first then will do.  

I am rather nervous as while this is my testing workhorse that now has failed I can afford to loose the partition as I have a backup from about a week back.

There is however a bit more to the story and I am trying to figure how many systems and where they are, that are having video trouble. Seems to be most on a testpartition on separate drive to MiniMe (hd0,2) problem partition (hd1,16). More later

Edit:
Presently running PoorMan install of one of my earlier MiniMe backup myliveCD, running on (hd1,x) I will use a konsole here that should work, do a umount -a first to be sure.  

Result:

Code: [Select]

[root@localhost gert]# cfdisk

[root@localhost gert]# umount -a
umount: /: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))
[root@localhost gert]#

Ah yes, did a cfdisk to check my labels, boy am I pleased I am converting to labels as best I can, I have a number of similar looking systems and constantly kept getting confused in /dev/sxy designations and toally knocked when I added an external hard drive, ... oops getting sidetrakced here

Code: [Select]

[root@localhost gert]# fsck -f /dev/sda2
fsck from util-linux-ng 2.18
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
minime2010: 121007/1831424 files (0.1% non-contiguous), 1765300/7325640 blocks
[root@localhost gert]#

Will see if that helped

[wedgetail]

Tried rebooting but I think it is no better.  This time I have let it hang and will just write what I see in the last screen.

Before the screen stopped (running verbose) I saw "cannot create temp ...", but too fast.

Arrrrgh, the screen timed out and now I just see localhost login:

I think the line was Init: Entering runlevel: 5

Can not open log file  /var/log/prcsys.log

...     /var/run/acpid.socket

I have also just seen many lines something about

rm:   seemed like program files were all Read Only I thought I had paused but it timed out and again back at login stage


No there is something very drastically wrong, I think I had better just shed a tear and cut my losses and try to recover using the backup to install.

I would love to investigate this but I don't have the time.

[Old-Polack]

wedgetail:

For what it's worth, you can use your labels when doing an fsck.

[root@fatman ~]# e2fsck -f LABEL=minime2010
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
minime2010: 350710/1986768 files (0.4% non-contiguous), 5709294/7934094 blocks

[wedgetail]

Thanks, yes I did think of that but felt a bit more comfortable with /dev/xxx.
However I am just pondering if I should take the opportunity to rsync and even older MiniMe which I did back up with rsync.

LABEL=minime2010  is the one I have lost
LABEL=MiniMe10bkup

I have /here and /there

mount LABEL=minime2010 /here
mount LABEL=MiniMe10bkup /there
rsync -a /there /here

Never tried this one before I don't think.   

Ok, it is running, but I think I should have used rsync -av /there /here

All done, the big question does it work?

[Old-Polack]

Thanks, yes I did think of that but felt a bit more comfortable with /dev/xxx.
However I am just pondering if I should take the opportunity to rsync and even older MiniMe which I did back up with rsync.

LABEL=minime2010  is the one I have lost
LABEL=MiniMe10bkup

I have /here and /there

mount LABEL=minime2010 /here
mount LABEL=MiniMe10bkup /there
rsync -a /there /here

Never tried this one before I don't think.  

Ok, it is running, but I think I should have used rsync -av /there /here

All done, the big question does it work?

You left out the trailing backslash. Should be;

[root@localhost ~]# rsync -av /there/ /here

What you will have is a directory named there with all the files and directories of that system inside.

[wedgetail]

I should have remembered the closing /   
I was 5 sec away from reformatting the partition thinking it did not work. Anyway I did re-run the operation  and it has recovered my system, well set me back some time.  I noticed fair few of my customisations gone.  Worse it had that long delay on boot up requiring initrd fix (know where one thread is)  (Now I wish I had also made an up to date rsync -av copy, well will soon have one, it is faster than going back to myliveCD copies)

Ok this will have to work for today. Quite happy to crash it out again.

What is going on presently.

From minime I test a script (thanks Just19) that generates LiveHDD installs on my /dev/sd17 sort of follows your suggestion to place all files in a partition target subdirectory, ie /"OS Name" directory, the sqfs also inside here, ie sqfs not in the target partition / directory. All seemed to work fine minor changes made on the way but I was piling in LiveHDD systems. Deleting and installing etc. 

Then persistence seemed attractive in a testing environment, for example when running up a newly downloaded minime2010.12 LiveHDD install, wanting to install Opera etc ie like to keep the customisation for later experiment on that LiveHDD install.  Not understanding properly the persistence concept. I seem to have gone right smack into a brick wall. 

I struck out on my own trying to improve my knowledge in this area and my problems arise, though I think I have multiple problems. 

Now with this MiniMe running right now I will repeat the script run for LiveHDD install, then I will revert to figure out why I could not successfully install a minime LiveCD downloaded two days ago on a new partition, only 90% (also goes to text login).   

[wedgetail]

Now I am getting worried, something in my system is wrong.

I have a poorman install of a system, on /sdb that ran perfectly a week or less ago. I was going to use that to make an install to /dev/sda2, where my minime resided. This locked up completely and I thought it was because I had just installed dropbox to make files available if I can figure how to work dropbox.

When I ran my poorman install I was sent to text log in, which I did as root I think, then used startx and to my surprise it came up working.

Decided to take a look at dmesg, and my lower lip headed south, here is the section that caused such action:

sd 4:0:0:0: [sdc] Assuming drive cache: write through
sd 4:0:0:0: [sdc] Attached SCSI removable disk
EXT2-fs (sda2): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda3): error: couldn't mount because of unsupported optional features (240)
attempt to access beyond end of device
sda4: rw=0, want=66, limit=2
isofs_fill_super: bread failed, dev=sda4, iso_blknum=16, block=32
attempt to access beyond end of device
sda4: rw=0, want=4, limit=2
EXT2-fs (sda4): error: unable to read superblock
EXT2-fs (sda7): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda8): warning: mounting ext3 filesystem as ext2
EXT2-fs (sda8): warning: maximal mount count reached, running e2fsck is recommended
EXT2-fs (sda9): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda10): error: couldn't mount because of unsupported optional features (244)
EXT2-fs (sda11): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda12): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda13): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sdb1): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sdb2): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sdb3): error: couldn't mount because of unsupported optional features (240)
attempt to access beyond end of device
sdb4: rw=0, want=66, limit=2
isofs_fill_super: bread failed, dev=sdb4, iso_blknum=16, block=32
attempt to access beyond end of device
sdb4: rw=0, want=4, limit=2
EXT2-fs (sdb4): error: unable to read superblock

As I mostly run ext4 with a few ext3 partitions to cope with LiveCD/LiveHDD work I am truly out of my depth. I can be convinced this has something to do with my video problems.

Suggestions as what to do more than welcome 

[AS]

Hello wedgetail,

I have read this thread 10 times, and still I feel the lack of the right informations:

I have a MiniMe system that I am using as test system for various test program installs before installing in KDE

Been working great but now suddenly it boots me to text login. In verbose booting I notice a lot of lines with "cannot create temp.."  

I can log in as root ok, attempt startx and managed to catch following:

/usr/bin/startx: line 142: cannot create temp file for here-document: Read-only file system
xauth:  error in locking authority file /root/.Xauthority
...snip...

All is telling you that your root filesystem is mounted read-only.

old-polack correctly suggest you to perform an fsck. (because a dirty filesystem is one of the possible reason for rootfilesystem to be mounted read-only).

old-polack
Thanks, I am rescuing a few files from the partition first then will do.

IMHO, this is not correct: first you should assure the consistency of the filesystem, and then to rescue whatever from the same fs.

I am rather nervous as while this is my testing workhorse that now has failed I can afford to loose the partition as I have a backup from about a week back.

Can't be worse when you are in "rescue mode", much better to leave the puter alone, enjoy some coffee or whatever you like and then come back to work on the issue...

There is however a bit more to the story and I am trying to figure how many systems and where they are, that are having video trouble. Seems to be most on a testpartition on separate drive to MiniMe (hd0,2) problem partition (hd1,16). More later

Edit:
Presently running PoorMan install of one of my earlier MiniMe backup myliveCD, running on (hd1,x) I will use a konsole here that should work, do a umount -a first to be sure.

Not sure 100%, but this can be the real problem, there are no info in the thread to understand about ...

I have also just seen many lines something about

rm:   seemed like program files were all Read Only I thought I had paused but it timed out and again back at login stage

Very probably the whole filesystem is still read-only...

I have /here and /there

mount LABEL=minime2010 /here
mount LABEL=MiniMe10bkup /there
rsync -a /there /here

Never tried this one before I don't think.   

Ok, it is running, but I think I should have used rsync -av /there /here

Look, you filesystem appear to be writable here ....

EXT2-fs (sda2): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda3): error: couldn't mount because of unsupported optional features (240)
attempt to access beyond end of device
sda4: rw=0, want=66, limit=2
isofs_fill_super: bread failed, dev=sda4, iso_blknum=16, block=32
attempt to access beyond end of device
sda4: rw=0, want=4, limit=2
EXT2-fs (sda4): error: unable to read superblock
EXT2-fs (sda7): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda8): warning: mounting ext3 filesystem as ext2
EXT2-fs (sda8): warning: maximal mount count reached, running e2fsck is recommended
EXT2-fs (sda9): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda10): error: couldn't mount because of unsupported optional features (244)
EXT2-fs (sda11): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda12): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda13): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sdb1): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sdb2): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sdb3): error: couldn't mount because of unsupported optional features (240)
attempt to access beyond end of device
sdb4: rw=0, want=66, limit=2
isofs_fill_super: bread failed, dev=sdb4, iso_blknum=16, block=32
attempt to access beyond end of device
sdb4: rw=0, want=4, limit=2
EXT2-fs (sdb4): error: unable to read superblock

What I see above ?
1) in green color should be swap partitions
2) in brown color ext3 partitions
3) in blue color ext4 partitions
4) the error "EXT2-fs (sdb3): error: couldn't mount because of unsupported optional features (240)"
is telling that you system is trying to mount an ext4 partition as ext2, and I think this is the main problem you have.

I know this very well, because the above error is what let me to understand why liveUSB can't work from ext4:
http://www.pclinuxos.com/forum/index.php/topic,89633.msg755635.html#msg755635

All in all, I think (and I can be very well wrong here) that while testing liveHDD, you have installed on an ext4 partition a live-image that
doesn't support ext4.

Please analyze the situation, if you see that is matching my conclusions, you can easily recover the situation:
- boot from a live CD
- copy the failing ext4  partition to a backup partition
- reformat the failing partition as ext3
- copy back from backup to the reformatted, this time ext3, partition.

HTH, AS

[wedgetail]

AS
I am real sorry, working too fast to get it over and done with.  The situation has changed but not improved. I believe I have two problems at least.

1.. My minime2010, that suddenly came up with "read only or cannot open" files, the one old-polack suggested doing the fsck upon. Here all I did was removing about 4 text files from the systems desktop holding records of what I am doing and all the install steps of customisation so I can recreate from beginning if needed (hope not)

Then ran the fsck, but this made no difference.

2.. Carried out the silly rsync -a, later corrected to rsync -av and the corrected parameters.  To my surprise this actually ran, it was a bit of an experiment. After two re-starts it failed. (Far out of sync timewise I think)

3.. I have reformatted the partition from root konsole: mke2fs -t -L minime2010 /sda2

4.. I have a newly downloaded minime2010.12 from Japan, normal repo was not available. I always download with Opera as I understand this does md5sum check in the background. Burned the ISO with k3B.

5.. Booted the CD no problem,  works fine.  Have used it to go on line and do many various things and then deciding to install to hard disk for a test (on /sda2 just prepared)

6.. On the 3rd try trying to figure out why it does not install properly I ran media check in desperation as well (of course ok) (I have also run md5sum check from konsole on the CD a few minutes ago, agrees too)

7.. The install to HD from LiveCD appears to go fine.

[DrakLiveInstall]
Installing PC LinuxOS to your computer
nice big pictorial

I am sure you know what I mean.  This picture just vanishes after about 3-5 delay, I think the screen said Please Wait.  I was expecting a few more windows to write the stanza, but they never showed. (Used already installed stanzas from previous minime, now suddenly not so sure about doing that)

The partition seems to hold a perfectly proper / system,


8.. I have even returned to much older MiniMe LiveCD, same result

Above worries me, I don't see this can have any bearing on the second part, the testing that minime was used to perform.

9.. I took up Just19 on his offer to test LiveHDD, his script and the ISO I used I placed on the Minime Desktop and ran the procedure from root konsole. Worked like a dream apart from minor adjustments as I see it. I have a partition set aside to receive output from script, /dev/sdb17 (LABEL=Just19) this is formatted ext3 (of course I tried to use ext4, as I have spare preformatted Linux partitions for testing work, an oversight despite strong warning from script, sorry Just19  , hope you had a laugh)

Conclusion:  I now believe I have two separate problems in the beginning I gave it 50/50 but not after I re-formatted the minime partition I can not see the LiveHDD testing has anything to do with not being able to install a new minime.

Right now I find it very very hard to understand why I can not install from a LiveCD, I will concentrate on getting that solved.  Actually trying to find that great thread wher old-polack gave a pictorial install to make 200% sure I am doing it right.

[AS]

Take a coffee please!     I will come back in few minutes ...

1) the next time you will do an install, please open a root Konsole and start installation from command line, if something will go wrong hopefully you should have some console messages ....

2) before to perform the installation, please try to open PCC -> System -> Set up boot System, to be sure nothing is actually preventing this program to work ....

3) this error, from a previous post, EXT2-fs (sda10): error: couldn't mount because of unsupported optional features (244)
contains a code, 244, I never had seen before, possibly an ext4 filesystem from some other distro ?

4) Are you using a swap partitions "shared" across several distro ?

5)

his picture just vanishes after about 3-5 delay

Not clear ... 3-5 secs or 3-5 minutes ?

6)

I was expecting a few more windows to write the stanza, but they never showed.

As I understand you are going to install in a ext2 formatted partition /dev/sda2. Are you using a separate /boot partition ?

7) before to install, please verify, using fdisk -l that the sda2 partition have an ID=83

end. Exhausted ideas!

AS

[Was_Just19]

wedgetail,
                  have you tested the memory lately?
Do you have that machine set up to 'delete temp at boot' or whatever the option is called?

[wedgetail]

Just19
That is good thinking. I have had such a good run with hardware that this has not yet occurred to me, I think we have memtest84 or something on LiveCD.

Deleting temp, hmmmm don't know or remember how in Linux, I have XP and I think I have it set there but hardly ever use it, though I just booted into XP to make sure that would boot, no problem.

I am in ZenMini just now writing this. As I have mentioned to you Gnome, LXDE. XFCE and now ZenMini  and my KDE still boots fine from /sdb

as
Done as instructed and I added a nice waffle for consolation for this mess. When under this sort of stress the cuppa does not seem to last long

I will mention I have done fsck on probably 20 or more of my partitions (got record too just in case) No hint of problem.

I have just run my MiniMe2010.12 LiveCD and with that double checked fdisk -l as well as cfdisk for both the hard drives I run now (the external USB backup hard drive has been removed a couple of days ago).

Minime LiveCD shut down correctly, though I thought a couple of times I had to use ctl+alt,PrtScr,B to get out but this was probably for the other systems that are baulking at me.

Now running an install from konsole, I don't think I have had to try that before, lay it on, how do I do that  

I am in ZenMini right now but

a.. yes share common swap file wit all my OS installed on HDs
b.. sorry delay is in seconds real fast, if you are not actually looking at it, window gone. ie the search for bootable devices as if overlooked
c.. oh, sda10 is my Gnome system, works fine on ext4
d.. no I am not installing to ext2 on /sda2 it will be ext4, minime ran in ext4 before

Code: [Select]

                         cfdisk (util-linux-ng 2.18)

                              Disk Drive: /dev/sda
                      Size: 1000204886016 bytes, 1000.2 GB
             Heads: 255   Sectors per Track: 63   Cylinders: 121601

    Name        Flags   Part Type  FS Type          [Label]        Size (MB)
 ------------------------------------------------------------------------------
    sda1        Boot        Primary   ntfs             [XP]            36701.20
    sda2                    Primary   ext4            [minime2010]     30005.83
    sda3                    Primary   ext4             [kde2010]       30005.83
    sda5                    Logical   ntfs             [500GB]        524287.58
    sda6                    Logical   swap             [swap4000] 4186.67
    sda7                    Logical   ext4             [xfce2010]      12576.46
    sda8                    Logical   ext3             [lxde2010]      24996.63
    sda9                    Logical   ext4             [zen2010]       20003.89
    sda10                   Logical   ext4             [gnome2010]     24996.63
    sda11                   Logical   ext4             [lxde-mini]     19995.66
    sda12 NC          Logical   ext4           [mythtvkde12]     21475.

Code: [Select]

                                 cfdisk (util-linux-ng 2.18)

                                     Disk Drive: /dev/sdb
                             Size: 1000204886016 bytes, 1000.2 GB
                    Heads: 255   Sectors per Track: 63   Cylinders: 121601

    Name           Flags        Part Type    FS Type             [Label]          Size (MB)
 ---------------------------------------------------------------------------------------------
                                             Unusable                                  1.05   *
    sdb1                         Primary     ext4              [kde2010-crash]     32217.38   *
    sdb2                         Primary     ext4                [DELTA-02]        42952.42   *
    sdb3                         Primary     ext4                [DELTA-03]        53686.41   *
    sdb5           NC            Logical     ext4                [DELTA-05]        26855.54   *
    sdb6           NC            Logical     ext4                [DELTA-06]        29002.34   *
    sdb7           NC            Logical     ext4            [sda12-mythtv-bk]     31149.14   *
    sdb8           NC            Logical     ext4              [DELTA-08-DONE]     33295.94   *
    sdb9           NC            Logical     ext4               [MiniMe10bkup]     10738.47   *
    sdb10          NC            Logical     ext4                [DELTA-10]        10738.47   *
    sdb11          NC            Logical     ext4                [DELTA-11]        12885.96  
Now that is a bit scary where are the rest of my partitions on that drive

Code: [Select]

Disk /dev/sdb: 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: 0x965c8f52

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048    62926603    31462278   83  Linux
/dev/sdb2        62926604   146818033    41945715   83  Linux
/dev/sdb3       146818034   251674288    52428127+  83  Linux
/dev/sdb4       251674289  1953520064   850922888    5  Extended
/dev/sdb5       251676337   304126513    26225088+  83  Linux
/dev/sdb6       304128562   360771703    28321571   83  Linux
/dev/sdb7       360773752   421609858    30418053+  83  Linux
/dev/sdb8       421611907   486640978    32514536   83  Linux
/dev/sdb9       486643027   507614546    10485760   83  Linux
/dev/sdb10      507616595   528588114    10485760   83  Linux
/dev/sdb11      528590163   553755986    12582912   83  Linux
/dev/sdb12      553758035   577195534    11718750   83  Linux
/dev/sdb13      577197583   602363406    12582912   83  Linux
/dev/sdb14      602365455   627531278    12582912   83  Linux
/dev/sdb15      627533327   658990606    15728640   83  Linux
/dev/sdb16      658992655   690449934    15728640   83  Linux
/dev/sdb17      690451983   721909262    15728640   83  Linux
/dev/sdb18      721911311   763854350    20971520   83  Linux

Disk /dev/sdc: 2002 MB, 2002747392 bytes
32 heads, 63 sectors/track, 1940 cylinders, total 3911616 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: 0x4c672daa

Pfeeeew must be a ZenMini oddity not handling cfdisk properly

Code: [Select]

[root@zen gert]# mount /dev/sda2 /media
[root@zen gert]# ls -l /media
total 264
drwxr-xr-x   2 root root   4096 Jul  2  2010 bin/
drwxr-xr-x   3 root root   4096 Apr 24 09:10 boot/
drwxr-xr-x  24 root root 135168 Apr 24  2011 dev/
drwxr-xr-x 104 root root   4096 Apr 24 09:35 etc/
drwxr-xr-x   3 root root   4096 Apr 24 09:11 home/
drwxr-xr-x  17 root root  12288 Jul  2  2010 lib/
drwx------   2 root root  16384 Apr 24 01:02 lost+found/
drwxr-xr-x   2 root root   4096 Apr 24  2011 mnt/
-rw-r--r--   1 root root  33486 Jul  2  2010 Module.symvers
-rw-r--r--   1 root root      0 Jul  2  2010 null
drwxr-xr-x   5 root root   4096 Mar  5  2010 opt/
drwxr-xr-x   2 root root   4096 Apr 24  2011 proc/
drwxr-xr-x  25 root root   4096 Apr 24 09:31 root/
drwxr-xr-x   2 root root  12288 Jul  2  2010 sbin/
drwxr-xr-x   2 root root   4096 Feb 22  2010 swap/
drwxr-xr-x   2 root root   4096 Apr 24  2011 sys/
drwxr-xr-x   2 root root   4096 Apr 24  2011 tmp/
drwxr-xr-x  14 root root   4096 Apr 24 09:10 usr/
drwxr-xr-x  16 root root   4096 Apr 24 09:10 var/
[root@zen gert]#

I am not quite out of zen yet, above is the installed to HD from lates Minime2010.12 but with failing to give me a stanza, so I have used the one I used before.
Returning to KDE now

[AS]

Now running an install from konsole, I don't think I have had to try that before, lay it on, how do I do that   

1) please re-read my previous post, perform all possible check before to install, at least 2 times, 
2) boot livecd, open a root Konsole, and type in drakelive-install