Recent content by Mookinator

  1. M

    RAID5 drive went TOO big for the system to see

    the 2 Terabyte limit is a hardware limitation of the 32bit file system. i do not know of any way around it. until you do that you'll be limited to a 2Tb partition and a 1.5Tb partition. what i was able to do, is install a trial version of server 2003 64bit edition. that's the key, it needs to...
  2. M

    RAID5 drive went TOO big for the system to see

    OK! i got gparted installed and running. and when i select SDA1 it shows me that there is still a 1.1Tb NTFS partition on the drive, with 894Gb unallocated. Image as a link so you can see what i'm seeing. now i had thought that the migration would have expanded the NTFS but it didn't. my...
  3. M

    RAID5 drive went TOO big for the system to see

    yes, and the only thing that happens is i get the same message/list of options as if i had typed 'mount --help' ~Mike
  4. M

    RAID5 drive went TOO big for the system to see

    Protias, thanks for the link to GParted. It's a nice program but it doesn't recognise the RAID array (using liveCD), and i cannot get the regular version to install on my Ubuntu server machine. i installed the 64bit version of Ubuntu server. it recognizes the partition and correctly...
  5. M

    RAID5 drive went TOO big for the system to see

    i would love to backup my data somehow. but seeing as i cannot find any program or operating system that will read the drive, i guess i'm kinda SOL huh? ~Mike
  6. M

    RAID5 drive went TOO big for the system to see

    here's the problem: I have a Promise Supertrak EX8350 SATA RAID controller. For a year now i've had 5x320Gb drives plugged into it and have been running a RAID5 without problem. The drive was formatted as NTFS and showed 1.2Tb. i was running low on space and purchased 3 more 320Gb drives. I...
Back
Top