Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hello We have DRBD 0.6.4 running on two IBM Netfinity 5100 with a RAID5 array. (Linux Suse 8.2). Primary DRBD server name = pascal Secondary DRBD server name = descartes After a disk crash on the primary DRBD server (Pascale) we replaced the disk and rebuilt it to the RAID. The secondary DRBD server (Descartes) is now running as primary: descartes:~ # cat /proc/drbd version: 0.6.4 (api:61/proto:62) 0: cs:WFConnection st:Primary/Unknown ns:53548436 nr:11002921 dw:68278315 dr:71328254 pe:0 ua:0 When I "drbd start" on the broken server (Pascale) DRBD starts synchronizing but the DRBD drive on the temorary primary server (Descartes) is not accessable anymore and the following log messages are created in /var/log/messages: . . . Oct 4 11:36:20 pascal kernel: SCSI disk error : host 2 channel 0 id 1 lun 0 return code = 70000 Oct 4 11:36:20 pascal kernel: I/O error: dev 08:11, sector 316256 Oct 4 11:36:20 pascal kernel: drbd0: The lower-level device had an error. Oct 4 11:36:20 pascal kernel: SCSI disk error : host 2 channel 0 id 1 lun 0 return code = 70000 Oct 4 11:36:20 pascal kernel: I/O error: dev 08:11, sector 316640 Oct 4 11:36:20 pascal kernel: drbd0: The lower-level device had an error . . . We completely checked the RAID 5 array (sector r/w test) and did not get an error. When I start drbd manually I do: 1. modprobe drbd 2. drbdsetup /dev/nb0 disk /dev/sdb1 -d 8809069 3. drbdsetup /dev/nb0 net 22.214.171.124 126.96.36.199 C At step 3 the errors start. Can anybody help how I get this system running again? This is a productive system and there is not much trying around. (... and I know that we should upgrade...:-)) Thanks Marc