vm scsi drive overlaying my hdd on ubuntu 14.04 lts
 

Hi. my issue is that i never put the scsi drive on my comp and have no way to remove it as yet. The bios i think has been overlay-ed as "corrupt snmp entry". Their are extra 2 hotplug cpu`s now running, 6gig of memory unclaimed,Even though logs show memory rerouted I get 3gig. I believe 2 fake nodes re-routing my IO`s + IRQ`S through my 2 graphics cards, can`t get passwd -r unknown user 0

mobo ASUS M2N32SLI DELUX WIFI EDITION
CPU AMD ATHLON X2 5400 2.4GHZ
GRAPHICS 2X GEFORCE GT9600 LINKED UP
HDD SEAGATE 500 BARRACUDA
DISTRO UBUNTU 14.04 LTS OR (14.04-VMLINUX)

I will post any logs required. This is affecting more than one of my computers any help would be gratefully appreciated.

PLEASE DO NOT JUST POINT ME TO MAN PAGES.

I NEED SERIOUS HELP

I don't get this.

Your say your issue is this, "i never put the scsi drive on my comp" Are you saying that when you created a virtual machine, your host drive was attached as a physical drive?

More info
 

Hi jefro
When i said "i never put the scsi drive on my comp" i mean i never put this on my computer i have run vm `s before however, this was always done through my main OS and always install and removed correctly. This sda SCSI drive is the main os i cannot get to what is behind it. It is booting from a fd, which is not installed on my machine. I have been able to format the fd and disrupt the boot which enabled me to see the logs.

" this was done by some one i once called friend " I built 2 new comps to upgrade my systems same thing on both running on a WWN address i am using this comp to find a method of removing this issue.

Their is a extended partition on the drive i am unable to remove using root,live disk, recovery tools and am unable to create a swap partition on install. What i am looking for help with, is some one to look at the logs to see how it has been re routed in essence to enable me to remove it. I have read so many man pages to rectify this and still trying "not deterred at all" But not having the ability to fully understand the paths in the logs i have been reluctant to play with them hence the post.

Thanks for the reply and interest.
sorry about the Rant lol

LIKE I POSTED ANY LOGS REQUIRED WILL BE POSTED ASAP

I still have to apologize. The question you have is still not clear to me.

Let us start again maybe.

A virtual machine generally offers two types of interfaces. One being ide(eide) and the other being sata. They are virtual adapters not real adapters. This is the physical layer. The client linux would view either as a scsi. Hence the /dev/sdX naming. Only very old kernels would report /dev/hdX.

Is this what we are talking about?

Is this what we are talking about
 

Hi jefro.
The drive is connected via sata cable and the drive does show as dev/sda if this helps explain your question.

hi jefro
Yes is was attached as a phisical drive.

There is a virtual drive however, it is not me that has control of it.I believe that some thing similar to flame or stux net are has been over-layer on me sys.

I believe the source to be a ipab and a xbox360. As soon as i switch on my system it pings the WWN address to either the xbox or ipad; Which then boots my system and takes control, giving the illusion of control.

I have been out for a while. Didn't forget you.

There is nothing wrong with this.
" connected via sata cable and the drive does show as dev/sda"

There is nothing wrong with this.
 

Hi jefro
All good mate. you say the its ok i understand why it shows up as a sda prefix no issus their lol.

I maybe just missing some thing then but the two hot pluged cpu reconfigured memory and pci address i feel are an issue. I have tried to flash the bios, and have ordered a new chip to help rectify the boot sequence.
I was hoping to rectify this by accessing the files on the disc as on the laptop with the same problem i tried to repair by booting from live disc booted the hard drive as a usb drive removed over 380 corrupt files i checked most of them out serious stuff. i tried to reinstall from the disc and drivers but dropped back to a network connection and froze me out due to the reworking of internal i/o addresses.

thanks for the reply
mad11

Maybe make a new post on this cpu issue?

You should be able to delete any partition that you want to with 'g-parted live'.
Boot the Live CD of g-parted and that will allow you to modify any partition you want.
http://gparted.org/download.php

You might want to list all partitions on your machine before you delete one of them. That way we can see what they look like first just to be on the safe side.

Their is a extended partition on the drive i am unable to remove using root,live disk, recovery tool
 

Hi Ztcoracat.
I have all ready tried fdisk ,parted,and gdisk,fsck,e2fsck. I am having miss-aligned sector`s,-over-lapping sector counts.As i mentioned in the other posts it`s redirected from boot process and am unable to get past it. I can get to part of the system now but not all.

I will post a couple of logs showing my issues in code enabling you more enlightened people to see what is going on.

Maybe make a new post on this cpu issue
 

Hi jefro
YEH LOL. Is that with the memory, pci, i/o, boot, graphic, wifi post`s

Maybe have to. But will start from boot first thats whats stopping me seeing and editing the PARTITIONS. when me new bios chip arrives.

I will if i can find it,
post the boot log as you may see my issue more clearly

This kind of behavior makes me suspicious of the RAM going bad.
You might want to run Memtest overnight.
http://www.memtest.org/

The dmesg log kicks out a lot of output so if you can post it on paste bin and give us the link to read the log.
http://pastebin.com/

Dmesg m2n32sli
 

Hi Ztcoracat.
Here is the log you wanted to look at mate.This will help explain my situation better than i can explain it.

http://pastebin.com/StC6iCdX

"Dmesg m2n32sli" is paste bin title:

Thanks Mad11

Here's a message in the dmseg log about the RAM-

I didn't see any ERRORS or Warnings in the dmesg log.
I'm not sure how the BIOS would corrupt low RAM so maybe try running Memtest and see if the RAM is bad.