I have two different size drives that I am using. Three Quantum
Viking 2 drives and 2 Quantum QM-foobar drives. The drives aren't
exactly the same size. Is it possible that raid is attempting to
write to the drives that are too small? The first and last drives in
the raid array are the larger drives. It appears that the raid always
lists one of the smaller drives as the first drive to crash.
If I attempt to raidhotremove and raidhotadd a particular drive, it
tells me that it can't be added because the partition is too small.
--Drew
m. allan noah writes:
> i have seen this problem. attempt to access beyond end of device has been
> reported by several people on the list as well. in all cases, it seems to
> have been a hardware issue, in my case, ram, in other cases, it was in
> individual disk.
>
> try some hardware swapping.
>
> allan
>
> "so don't tell us it can't be done, putting down what you don't know.
> money isn't our god, integrity will free our souls" - Max Cavalera
>
> On Mon, 27 Dec 1999, Drew Norman wrote:
>
> >
> >
> > I have a problem with raid level 5. I am running linux kernel
> > 2.2.12-20 (from Redhat 6.1), and the raidtools that shipped with
> > redhat. I have a machine that is totally flaking out. After a few
> > hours/days of running the machine I get the proceeding errors in the syslog.
> >
> > Why am I getting this error? Why does the entire raid shut down? Why
> > doesn't the raid just go into degraded mode? Why is raid attempting
> > to write beyond the end of the device?
> >
> > Please help.
> >
> >
> > Thanks
> >
> > --Drew
> >
> >
> > Dec 27 16:02:48 cwb-jumbo kernel: 929388176 sector=-436190944 size=1024 count=1
> > Dec 27 16:02:48 cwb-jumbo kernel: interrupting MD-thread pid 8
> > Dec 27 16:02:48 cwb-jumbo kernel: raid5: parity resync was not fully finished,
>restarting next time.
> > Dec 27 16:02:48 cwb-jumbo kernel: raid5: Disk failure on sdc1, disabling device.
>Operation continuing on 4 devices
> > Dec 27 16:02:48 cwb-jumbo kernel: raid5: restarting stripe 3858776352
> > Dec 27 16:02:48 cwb-jumbo kernel: attempt to access beyond end of device
> > Dec 27 16:02:48 cwb-jumbo kernel: 08:41: rw=0, want=1929388177, limit=8916043
> > Dec 27 16:02:48 cwb-jumbo kernel: dev 09:00 blksize=1024 blocknr=1929388176
>sector=-436190944 size=1024 count=1
> > Dec 27 16:02:48 cwb-jumbo kernel: raid5: Disk failure on sde1, disabling device.
>Operation continuing on 3 devices
> > Dec 27 16:02:48 cwb-jumbo kernel: attempt to access beyond end of device
> > Dec 27 16:02:48 cwb-jumbo kernel: 08:31: rw=0, want=1929388177, limit=8916043
> > Dec 27 16:02:48 cwb-jumbo kernel: dev 09:00 blksize=1024 blocknr=1929388176
>sector=-436190944 size=1024 count=1
> > Dec 27 16:02:48 cwb-jumbo kernel: raid5: Disk failure on sdd1, disabling device.
>Operation continuing on 2 devices
> > Dec 27 16:02:48 cwb-jumbo kernel: attempt to access beyond end of device
> > Dec 27 16:02:48 cwb-jumbo kernel: 08:11: rw=0, want=1929388177, limit=8916043
> > Dec 27 16:02:48 cwb-jumbo kernel: dev 09:00 blksize=1024 blocknr=1929388176
>sector=-436190944 size=1024 count=1
> > Dec 27 16:02:48 cwb-jumbo kernel: raid5: Disk failure on sdb1, disabling device.
>Operation continuing on 1 devices
> > Dec 27 16:02:48 cwb-jumbo kernel: attempt to access beyond end of device
> > Dec 27 16:02:48 cwb-jumbo kernel: 08:01: rw=0, want=1929388177, limit=8883913
> > Dec 27 16:02:48 cwb-jumbo kernel: dev 09:00 blksize=1024 blocknr=1929388176
>sector=-436190944 size=1024 count=1
> > Dec 27 16:02:48 cwb-jumbo kernel: raid5: Disk failure on sda1, disabling device.
>Operation continuing on 0 devices
> > Dec 27 16:02:48 cwb-jumbo kernel: raid5: restarting stripe 3858776352
> > Dec 27 16:02:48 cwb-jumbo kernel: raid5: md0: unrecoverable I/O error for block
>1275101760
> > Dec 27 16:02:48 cwb-jumbo kernel: raid5: md0: unrecoverable I/O error for block
>3892601472
> > Dec 27 16:02:48 cwb-jumbo kernel: raid5: md0: unrecoverable I/O error for block 812
> > Dec 27 16:02:48 cwb-jumbo kernel: raid5: md0: unrecoverable I/O error for block
>11709171
> > Dec 27 16:02:48 cwb-jumbo kernel: raid5: md0: unrecoverable I/O error for block
>11709172
> > Dec 27 16:02:48 cwb-jumbo kernel: raid5: md0: unrecoverable I/O error for block
>11709173
> > Dec 27 16:02:48 cwb-jumbo kernel: raid5: md0: unrecoverable I/O error for block
>11709174
> > Dec 27 16:02:48 cwb-jumbo kernel: raid5: md0: unrecoverable I/O error for block
>11709175
> > Dec 27 16:02:48 cwb-jumbo kernel: raid5: md0: unrecoverable I/O error for block
>11709176
> > Dec 27 16:02:48 cwb-jumbo kernel: raid5: md0: unrecoverable I/O error for block
>11709177
> > Dec 27 16:02:48 cwb-jumbo kernel: raid5: md0: unrecoverable I/O error for block
>11709178
> > Dec 27 16:02:48 cwb-jumbo kernel: raid5: md0: unrecoverable I/O error for block
>11709179
> > Dec 27 16:02:48 cwb-jumbo kernel: raid5: md0: unrecoverable I/O error for block
>11709180
> > Dec 27 16:02:48 cwb-jumbo kernel: raid5: md0: unrecoverable I/O error for block
>11709181
> >
> >
> >
>
>
>
