Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: bloodshoteye on June 06, 2008, 02:23:34 PM
-
Hi all
System is 7.3 fully Raid1 with 3 x 250GB sata drives.
Removed 2 and fitted a 1TB drive.
Intention is to sync the 1 250Gb drive and the 1 TB drive.
After restart su Adim shows
md2: active raid1 sda2[0]
244091520 blocks [2/1] [U_]
md1: active radi1 [sda1[0]
104320 blocks [2/1] [U_]
The free disk count must equal one.
Manual intervention may be required.
From what I've read on the forum, if I then do:
mdadm /dev/md2 -a /dev/sdb2
a resync should start, however the system reports:
mdadm: cannot find /dev/sdb2: No such file or directory
Could someone please point out my incorrect reasoning?
-
Hi..
I suggest you to use the console to add the hd to your raid.
if you want to do it manually, you have to create partitions on new hd..
HTH
Ciao
Stefano
-
When you say use the console, do you mean su admin > Manage disk redundancy?
If so, there are no selections I can make there - just gives current raid status (which I partly quoted in my post)
-
well..
Are you sure your new hd is detected?
look into /var/log/messages and/or on dmesg.
IMO if the new hd is detected, you should see it in console -> manage disk redundancy and you should be able to add it.
Ciao
Stefano
-
Are you sure your new hd is detected?
Looks like it:
ata2.00: configured for UDMA/133
Vendor: ATA Model: ST3250620AS Rev: 3.AA
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
SCSI device sda: drive cache: write back
sda: sda1 sda2
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Vendor: ATA Model: ST31000340NS Rev: SN04
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sdb: 65134 512-byte hdwr sectors (33 MB) <<< supposed to be a 1TB disk!
SCSI device sdb: drive cache: write back
SCSI device sdb: 65134 512-byte hdwr sectors (33 MB)
SCSI device sdb: drive cache: write back
sdb: unknown partition table
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
device-mapper: 4.5.5-ioctl (2006-12-01) initialised: dm-devel@redhat.com
md: raid1 personality registered as nr 3
md: md1 stopped.
md: bind<sda1>
raid1: raid set md1 active with 1 out of 2 mirrors
md: md2 stopped.
md: bind<sda2>
raid1: raid set md2 active with 1 out of 2 mirrors
-
Vendor: ATA Model: ST3250620AS Rev: 3.AA
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
SCSI device sda: drive cache: write back
sda: sda1 sda2
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Vendor: ATA Model: ST31000340NS Rev: SN04
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sdb: 65134 512-byte hdwr sectors (33 MB)
SCSI device sdb: drive cache: write back
SCSI device sdb: 65134 512-byte hdwr sectors (33 MB)
SCSI device sdb: drive cache: write back
sdb: unknown partition table
As far I can see it looks like your hw does not support such a disk..
try
fdisk /dev/sdb
ciao
Stefano
-
Looks like it :sad:
]# fdisk /dev/sdb
Command (m for help): p
Disk /dev/sdb: 33 MB, 33348608 bytes
255 heads, 63 sectors/track, 4 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
I thought Linux could handle any size drive no matter what the BIOS said.
-
it could be a mb issue..
read the documentation and search the mb's manufacturer.
good luck :-)
Ciao
Stefano
-
Had a look at the tested hard drives list. Only Hitachi 1000GB is listed, not Seagate Barracuda, which I have.
However, a Seagate 750GB is listed... Hey nenonano, need some drives?
I suppose just because the mobo is capable of working with the Hitachi doesn't mean it can use the Seagate.
-
Had a look at the tested hard drives list. Only Hitachi 1000GB is listed, not Seagate Barracuda, which I have.
wait.. maybe there will be a bios update..
However, a Seagate 750GB is listed... Hey nenonano, need some drives?
thank you, but you are "slightly" far from here.. (Italy, Treviso, near Venice) :-)
I suppose just because the mobo is capable of working with the Hitachi doesn't mean it can use the Seagate.
I repeat.. wait.. or wrote to mb's manufacturer support and ask infos.
ciao
Stefano
-
i maybe wrong but does not the drives have to be the same size for raid 1 to work one 250 and 1 1000 i would not have thought that would work they both have to be 1000MB each to work in raid one
-
nenonano
lol - hope you have some nice pasta and wine this weekend! (my favorites)
Well, I got hold of the server supplier - they advise me to flash the BIOS, which I did. Didn't make any difference :sad:
The guy at the shop had the exact same server on his workbench. he fetched the exact same Seagate 1TB drive, plugged it in and it registered the drive.
Must be a fault with my server - the BIOS picks up the unit, but says 0.0GB! I tried all the ports, no change. I plug the 250GB back in and sme says "Do you want to add this drive to the array"
Now I'm back to where I started - well in 45min or so.
I'm going home to chillie tacos and red wine. Speak to you again.
-
I had to put brand new 1TB drives on the shelf and buy 750GB Seagate drives for this Intel server board. They were picked up by the BIOS and SME did what it does so well - added one drive at a time to the RAID 1 array.
I then did
mdadm --grow /dev/md2 --size=max
pvresize /dev/md2
lvresize -l +100%FREE main/root
ext2online -C0 /dev/main/root
as per contribs howto and now the client has sufficient space for awhile :)
Thanks to all who helped with this, past and present.