New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CentOS 6.4 - Rescue Boot Failed: VFS: Cannot open root device "(null)" or unknown-block(253,0) #293
Comments
Try |
I did examine the temp directory root fs and the generated image both by unpacking and by using lsinitrd. The logs didn't indicate anything to me when I looked. I didn't try chrooting into it. I'll try that. I am suspecting my kernel. I found options to enable small system support. I built a new zImage with them on but haven't tested it yet. I'll do that on Monday and rebuild, check the logs again, and try the chroot. |
I can chroot into the tmp rootfs but I couldn't use 'ls' and so I checked and it is not even present. I noticed that it seems other files are missing as well including '/init'. Compared to one of the working "initramfs*.img" under my '/boot', they have one under '/'. The one in the rear rootfs is a broken symbolic link to 'bin/init'. Using 'lsinitrd' on the generated 'initrd.cgz' file shows the same things missing. I haven't yet tested my kernel build with small system support but maybe I don't need it if the rootfs is indeed missing files. Checking the log, there were no error indications, but there were some warnings that seem unrelated. root@iommi /var/log/rear# cat rear-iommi.log | grep -v "++" | grep -i "warn"
|
Enabling small systems support in the kernel did not do anything. It was a shot in the dark but at least we know for sure. |
After the test, I ran another
This looks to be about what I get and I'm not seeing I don't think they are printed from the conf but I see this debug in the log:
This would suggest that |
I added a debug log to the end of each script that ran for my configuration to print out the I tried to add a custom program to be included and I broke the Here is an example of what I did in the INCORRECT:
CORRECT:
I didn't notice on my other server because I added this after I had validated the configuration and never actually tested the new image. I'll be re-doing all my images after this. Marking this as solved. |
Using OUTPUT=ISO, BACKUP=RBME on CentOS 6.4 (up-to-date with epel and remi repos) I am unable to boot from the recovery media (burned from the iso dropped on the backup server) or from the grub-installed local kernel/initrd stanza.
I tried adding root=/dev/ram0 to the kernel command line params and that gets me a different error: No filesystem could mount root, tried: iso9660
This is a group development server that is not yet in use (initial testing and recovery verification only). I can mess with whatever settings or reboot as needed.
Unfortunately I haven't been able to get the serial output working from this server so I haven't been able to read the entire kernel output during boot.I was able to get the serial output from the boot and there didn't appear to be any errors until the panic.Thanks in advance for any assistance.
root@iommi /var/log/rear# rear -v -d -D mkbackup
root@iommi /var/log/rear# echo $?
root@iommi /var/log/rear# rear -v dump
The text was updated successfully, but these errors were encountered: