On 29/11/12 10:13, mick wrote:
On Thu, 29 Nov 2012 09:46:08 +0000 Mark Rogers <mark@quarella.co.uk> allegedly wrote:
If it ain't broke.... Fix it 'till it is.....
(Been there, done that, got the T shirt.)
Me too! Somehow it's only obvious that's what you're doing when it's too hard to go back to where you started... Latest: Ubuntu server installed fine, but when it booted I got SOOR again! Luckily I had told the server installer to install SSH, and I was able to work out the IP it had been given by DHCP, so that allowed me to edit /etc/default/grub and set GRUB_GFXMODE=1024x768 followed by sudo update-grub It now boots fine. Also, it being a server install, it included mdadm and detected all my RAID disks without me doing anything (it was RAID5 as I had suspected). Part of the problem appears to be that grub uses a graphical terminal so adding anything at the grub prompt requires doing it blind (staring at a SOOR error). This, I believe, can be fixed with GRUB_TERMINAL=console .. also in /etc/default.grub, although I haven't tried this. (It's all very well having these settings but fixing them is a bit chicken and egg! Without SHH I'd have been pretty stuck!) Anyway, for my next trick I will [*] install Windows 8 on this server and see how well it handles the legacy hardware :-) [*] Oh no I bl**dy won't! -- Mark Rogers // More Solutions Ltd (Peterborough Office) // 0844 251 1450 Registered in England (0456 0902) 21 Drakes Mews, Milton Keynes, MK8 0ER