On Sat, 10 Oct 1998, MOLNAR Ingo wrote:
> if you have lots of data on your RAID0 array and cannot do a backup, then
> this is how it goes. But if you can recreate the RAID0 array after backing
> up all data in it, you can put this into your raidtab:
>
> persistent-superblock 1
>
> and the (newly created, with destroying all data content) RAID0 array will
> be autostartable just like RAID5.
Thanks for the guidance. I was thinking about recreating both the RAID0
and RAID5 arrays from scratch. I'll give it a try.
I can confirm Tommiy's report of both the "/dev/mdx: Invalid argument"
upon raidstart of RAID0 and RAID5, and "unresolved symbol
md_interrupt_thread" upon attempting to load the RAID modules directly. I
compiled the kernel with the "autostart RAID" option, and the kernel
messages indicate that RAID personalities are registered.
I get the following errors in the boot log. I can provide a more complete
log and my raidtab via private email if you need it.
...
(read) sdb1's sb offset: 104320
md: invalid raid superblock magic on sdb1
md: sdb1 has invalid sb, marking faulty!
can not autostart based on faulty sdb1!
export_rdev(sdb1)
autostart sdb1 failed!
(read) sda3's sb offset: 128448
md: invalid superblock checksum on sda3
bind<sda3,1>
...
Thanks!
Geof
DISCLAIMER: The comments above are my own and may not represent the views
of my employer.
+-------------------------------+-------------------------------------------+
: Geoffrey P. Goodrum : US Department of Commerce :
: +1-301-457-5100 : NOAA/NESDIS National Climatic Data Center :
: [EMAIL PROTECTED]: Satellite Services Branch :
+-------------------------------+-------------------------------------------+
