https://bugzilla.novell.com/show_bug.cgi?id=653081 https://bugzilla.novell.com/show_bug.cgi?id=653081#c2 Jiri Slaby changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |jslaby@novell.com InfoProvider| |nothereforever@hotmail.com --- Comment #2 from Jiri Slaby 2010-11-12 09:14:51 UTC --- (In reply to comment #0)

1. have a collection of windows partitions on the drives 2. run setup and it reports incorrect

Incorrect in what manner? Could you attach /var/log/boot.msg (transferred e.g. via network or USB disk) and output of fdisk -l? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=653081 https://bugzilla.novell.com/show_bug.cgi?id=653081#c4 --- Comment #4 from Charlie Barfield 2010-11-12 20:40:02 UTC --- what sort of steps do i do to get out of setup to get this output or get a text output from setup? i could try to photograph but i guess a text output is better... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=653081 https://bugzilla.novell.com/show_bug.cgi?id=653081#c6 --- Comment #6 from Charlie Barfield 2010-11-12 23:29:37 UTC --- the output of Fdisk -l ON SUSE 11.2 follows (if i can do runlevel 3 on 11.3 setup i might be able to properly give its confused interpretation of my arrangement, if i install 11.3 it somewhat sees my partitions -- see Bug 640380) last drive is a usb. linux:/home/linux # fdisk -l Disk /dev/sda: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xd646fea2 Device Boot Start End Blocks Id System /dev/sda1 * 1 2741 22017051 7 HPFS/NTFS /dev/sda2 2742 3263 4192965 7 HPFS/NTFS /dev/sda3 3264 24321 169148385 7 HPFS/NTFS Disk /dev/sdb: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000001 Device Boot Start End Blocks Id System /dev/sdb1 1 16709 134215011 7 HPFS/NTFS /dev/sdb2 * 16710 24321 61143390 7 HPFS/NTFS Disk /dev/sdc: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x0a8dd031 Device Boot Start End Blocks Id System /dev/sdc1 * 1 38913 312568641 7 HPFS/NTFS linux:/home/linux # -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=653081 https://bugzilla.novell.com/show_bug.cgi?id=653081#c8 Jiri Slaby changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|nothereforever@hotmail.com | Resolution| |NORESPONSE --- Comment #8 from Jiri Slaby 2011-04-19 14:38:45 UTC --- Closing due to lack of response. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=653081 https://bugzilla.novell.com/show_bug.cgi?id=653081#c Charlie Barfield changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Component|Installation |Installation AssignedTo|kernel-maintainers@forge.pr |bnc-team-screening@forge.pr |ovo.novell.com |ovo.novell.com Product|openSUSE 11.3 |openSUSE 12.1 Summary|setup sees my disk |setup sees two independent |partitions incorrectly on |drives as ONE unit on SATA |SATA controller |controllerS ie, | |/xyz_2x200GB OS/Version|openSUSE 11.3 |openSUSE 12.1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=653081 https://bugzilla.novell.com/show_bug.cgi?id=653081#c11 Charlie Barfield changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|NORESPONSE | --- Comment #11 from Charlie Barfield 2012-03-06 22:13:24 UTC --- evidently the bug must be in mapper as that is where this 2x200Gb is found. last comment:....i do not know how to seperate them in linux and stop .... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=653081 https://bugzilla.novell.com/show_bug.cgi?id=653081#c kk zhang changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kkzhang@novell.com AssignedTo|bnc-team-screening@forge.pr |jslaby@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=653081 https://bugzilla.novell.com/show_bug.cgi?id=653081#c13 --- Comment #13 from Charlie Barfield 2012-03-10 00:07:24 UTC --- i probably should write what happens in the os/live cd. what do i get instead of seeing the files as i did in 11.2? well i had the patience to sit around the computer and i see 12.1's dolphin now works as it did in ll.2 however i did get errors because things were timing out due to CDROM access. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=653081 https://bugzilla.novell.com/show_bug.cgi?id=653081#c15 --- Comment #15 from Charlie Barfield 2012-03-14 03:35:05 UTC --- i have more information. i placed the drives into a dell however i only had one R/A sata connector so i only connected one. the raid firmware was active and it said my raid failed, it called it 2x200gb. so i will explain how i de-raided my drives. on the gigabyte mainboard, all i did was move the plugs from the onboard SATA raid to the onboard intel sata controller. deleted all the partitions and repartitioned. i didnt delete via the raid controller. i looked in the dell controller setup and it does have an option to de-raid but it warns of loosing data -- i did so and my data was still accessible. --- so its up to you if you want to persue this. drives were set to raid0. so mapper read the disk raid data and presumed disks were still raided - and appears to be prepared to perform software raid. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=653081 https://bugzilla.novell.com/show_bug.cgi?id=653081#c17 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |nothereforever@hotmail.com --- Comment #17 from Jeff Mahoney 2012-03-28 14:09:44 EDT --- Yeah, RAID controllers typically warn of losing all your data but they usually don't. It's a "just in case something happens, you should be prepared" kind of warning. The dirty little secret about these "RAID" controllers is that that they don't actually do anything other than have a bit of nvram, some basic firmware that can write some metadata to the disks, and *sometimes* may have something basic like an xor accelerator that is nearly always slower than the subsequent generation of CPU doing it itself. The main reason they're "RAID" controllers rather than a regular controller with a software raid front-end is so that generic ATA/AHCI drivers don't claim them as separate disks. For Windows, I suppose the driver probably claims the disk, reads the metadata and sets up software raid. I don't know for sure. For Linux, dmraid claims the devices after reading the metadata off the disks. I'm not a dmraid expert but I expect that the 'dmraid -x' will also remove the metadata from the disks without having to involve the firmware. That's also why when you moved it to a different type of controller, it still came up. I'm having trouble parsing the situation you're in now. Did going through the RAID controller firmware succeed in un-RAIDing your disks? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=653081 https://bugzilla.novell.com/show_bug.cgi?id=653081#c19 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |INVALID --- Comment #19 from Jeff Mahoney 2012-05-02 16:17:00 EDT --- Thanks for the feedback. I've used it to write up an SDB article to describe the issue. It still needs work, but it's a start. http://en.opensuse.org/SDB:DMRAID -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.