Dear all,

on boot, the system falls back into "INITRAMFS" , something to do with the 
failed iscsi disks and if i don't type anything,a log starts showing containing 
"SYNC_DISK..." among other things.. if i hit enter, it stops and i get back to 
the INITRAMFS prompt.
 support technicians in a remote collocated DC couldn't get my server back up 
and running from a degraded raid so they plugged in a new drive and installed 
debian over it (twice)
if they physically unplug all the old drives, the new debian installation boots 
up normally.
i rebooted into a live cd and made sure that nothing in fstab points to the old 
disks, though on boot i keep on seeing hdio_get_identity failed for 
dev/sdXtiming outdropping to shell
and by X i mean all 10 drives. 
after a lot of troubleshooting, i came across this interesting script 
http://bootinfoscript.sourceforge.net/and after executing it on that server in 
a ubuntu livecd i get very interesting details, this is the header though you 
could find the full details in this pastebin url: http://pastebin.com/GLgUH7ig



============================= Boot Info Summary: ===============================
 => No boot loader is installed in the MBR of /dev/sdd. => No known boot loader 
is installed in the MBR of /dev/sdf. => No known boot loader is installed in 
the MBR of /dev/sdg. => No known boot loader is installed in the MBR of 
/dev/sdh. => Grub2 (v1.99) is installed in the MBR of /dev/sdi and looks at 
sector 34     of the same hard drive for core.img. core.img is at this location 
and     looks for (mduuid/345c489c63e34d58c1c1a2ac8ff8a6b6)/grub on this drive. 
=> Grub2 (v1.99) is installed in the MBR of /dev/sdj and looks at sector 34     
of the same hard drive for core.img. core.img is at this location and     looks 
for (mduuid/345c489c63e34d58c1c1a2ac8ff8a6b6)/grub on this drive. => Grub2 
(v1.99) is installed in the MBR of /dev/sdl and looks at sector 34     of the 
same hard drive for core.img. core.img is at this location and     looks for 
(,gpt2)/grub on this drive.
                                          

Reply via email to