RE: F19 raid 1 stuck read only after reboot

2013-07-22 Thread Alan Gagne
Alan Gagne https://admin.fedoraproject.org/mailman/listinfo/users>> writes: >>/ >>/ />/ Jul 19 07:35:26 knucklehead..com kernel: device-mapper: table: />>/ />>/ />/ 253:4: linear: dm-linear: Device lookup failed />>/ />>/ />/ Jul 19 07:35:26 knucklehead..com kernel: device-mappe

Re: F19 raid 1 stuck read only after reboot

2013-07-21 Thread lee
Alan Gagne writes: >> >>/ />/ Jul 19 07:35:26 knucklehead..com kernel: device-mapper: table: >> />>/ />/ 253:4: linear: dm-linear: Device lookup failed >> />>/ />/ Jul 19 07:35:26 knucklehead..com kernel: device-mapper: ioctl: >> />>/ />/ error adding target to table >> />>/ / >>

RE: F19 raid 1 stuck read only after reboot

2013-07-20 Thread Alan Gagne
>>/ />/ Jul 19 07:35:26 knucklehead..com kernel: device-mapper: table: />>/ />/ 253:4: linear: dm-linear: Device lookup failed />>/ />/ Jul 19 07:35:26 knucklehead..com kernel: device-mapper: ioctl: />>/ />/ error adding target to table />>/ / />>/ It seems likely that this is wh

Re: F19 raid 1 stuck read only after reboot

2013-07-19 Thread lee
Alan Gagne writes: >> >>/ "SMART is not a reliable warning system for impending failure >> />/ Maybe not, but when I had one of these drives going bad about a year >> ago. >> />/ It did a great job of warning that I had an impending drive failure. >> />/ The relocated sector count would jump

RE: F19 raid 1 stuck read only after reboot

2013-07-19 Thread Alan Gagne
>>/ "SMART is not a reliable warning system for impending failure />/ Maybe not, but when I had one of these drives going bad about a year ago. />/ It did a great job of warning that I had an impending drive failure. />/ The relocated sector count would jump in small blocks over time. / Intere

Re: F19 raid 1 stuck read only after reboot

2013-07-19 Thread lee
Alan Gagne writes: >> "SMART is not a reliable warning system for impending failure > Maybe not, but when I had one of these drives going bad about a year ago. > It did a great job of warning that I had an impending drive failure. > The relocated sector count would jump in small blocks over time.

RE: F19 raid 1 stuck read only after reboot

2013-07-19 Thread Alan Gagne
>>/ >>/ >/ # cat /proc/mdstat />>/ />>/ />/ Personalities : [raid0] [raid1] />>/ />>/ />/ md124 : active raid1 sdb[1] sdc[0] />>/ />>/ />/293032960 blocks super external:/md125/0 [2/2] [UU] />>/ />>/ />/ />>/ />>/ />/ md125 : inactive sdb[1](S) sdc[0](S) />>/ />>/ />/

Re: F19 raid 1 stuck read only after reboot

2013-07-19 Thread lee
Alan Gagne writes: >> >>/ >/ # cat /proc/mdstat >> />>/ />/ Personalities : [raid0] [raid1] >> />>/ />/ md124 : active raid1 sdb[1] sdc[0] >> />>/ />/293032960 blocks super external:/md125/0 [2/2] [UU] >> />>/ />/ >> />>/ />/ md125 : inactive sdb[1](S) sdc[0](S) >> />>/ />/

RE: F19 raid 1 stuck read only after reboot

2013-07-19 Thread Alan Gagne
>>/ >/ # cat /proc/mdstat />>/ />/ Personalities : [raid0] [raid1] />>/ />/ md124 : active raid1 sdb[1] sdc[0] />>/ />/293032960 blocks super external:/md125/0 [2/2] [UU] />>/ />/ />>/ />/ md125 : inactive sdb[1](S) sdc[0](S) />>/ />/6184 blocks super external:imsm />>/

Re: F19 raid 1 stuck read only after reboot

2013-07-19 Thread lee
Alan Gagne writes: >> >/ # cat /proc/mdstat >> />/ Personalities : [raid0] [raid1] >> />/ md124 : active raid1 sdb[1] sdc[0] >> />/293032960 blocks super external:/md125/0 [2/2] [UU] >> />/ >> />/ md125 : inactive sdb[1](S) sdc[0](S) >> />/6184 blocks super external:imsm >> />

RE: F19 raid 1 stuck read only after reboot

2013-07-18 Thread Alan Gagne
>/ # cat /proc/mdstat />/ Personalities : [raid0] [raid1] />/ md124 : active raid1 sdb[1] sdc[0] />/293032960 blocks super external:/md125/0 [2/2] [UU] />/ />/ md125 : inactive sdb[1](S) sdc[0](S) />/6184 blocks super external:imsm />/ />/ md126 : active raid0 sdd[1] sde[0] />

Re: F19 raid 1 stuck read only after reboot

2013-07-18 Thread lee
Alan Gagne writes: > # cat /proc/mdstat > Personalities : [raid0] [raid1] > md124 : active raid1 sdb[1] sdc[0] > 293032960 blocks super external:/md125/0 [2/2] [UU] > > md125 : inactive sdb[1](S) sdc[0](S) > 6184 blocks super external:imsm > > md126 : active raid0 sdd[1] sde[0] >

RE: F19 raid 1 stuck read only after reboot

2013-07-18 Thread Alan Gagne
On Jul 18 11:45, Alan Gagne wrote: >/ Having an odd problem with my raid 1 array after upgrade to F19. />/ Upgraded using fedup from 18 to 19. Did not have any problems />/ with the upgrade itself but since my raid 1 array is stuck read only after />/ each reboot. />/ />/ This is a bios int

Re: F19 raid 1 stuck read only after reboot

2013-07-18 Thread Corinna Vinschen
On Jul 18 11:45, Alan Gagne wrote: > Having an odd problem with my raid 1 array after upgrade to F19. > Upgraded using fedup from 18 to 19. Did not have any problems > with the upgrade itself but since my raid 1 array is stuck read only after > each reboot. > > This is a bios intel raid set-up I h

F19 raid 1 stuck read only after reboot

2013-07-18 Thread Alan Gagne
Having an odd problem with my raid 1 array after upgrade to F19. Upgraded using fedup from 18 to 19. Did not have any problems with the upgrade itself but since my raid 1 array is stuck read only after each reboot. This is a bios intel raid set-up I have been using for a little over three years.