Casper.Dik at Sun.COM wrote: >> > > You have a lot of power failures; but the system should be able to > bot.
Thought so. > > >> It was pointed out to me, that the problem was a corruption of the >> boot archive by a third party driver. >> > > Which particular driver would this be? > According to that link, VirtualBox, e.g. > >> My questions/suggestions are: >> >> Ought boot archive not be an independent process, that creates a >> proper backup in case of any modification, from any stupid handling? >> Should a recycling reboot not be noted, if just by a flag (in case we >> have r/w of a drive), including a redirection of the messages into a >> file? >> Should we not keep track of a proper roll-back point to offer to boot >> to in case of failing/recycling boots? Maybe something like 'last >> successful boot'? >> > > With ZFS this should become possible; this looks like an interest project > in itself. At the end of boot, you would clone the root and record it as > the "last-successful-boot". > Let's leave out that unfortunate error as above. My main gripe is that here I have a double-digit percent chance of a corrupted boot archive after a power outage. In a place with 150+ thunderstorms per year, that may happen. Combine it with a sub-standard power company, and everyone will ask: "why no UPS?" Let's say for testing operating systems on their behaviour at power outages. It is a tad crazy that 1 out of n times (5 < n < 15) I need boot, Failsafe, boot, mount, 'yes', init 6. That is, 3 boots to correct a boot archive. Uwe
