EXT3-fs (xvda): error: ext3_journal_start_sb
I'm trying to configure my server.
What I did:
1. Splitted my disk to several disks (/dev/xvda, /dev/xvdb, /dev/xvdc etc.);
2. Installed Debian on /dev/xvda (/dev/xvdb is used as Swap);
3. Deboostrapped another distro on /dev/xvdc;
4. Installed a custom kernel;
5. Modified /boot/grub/; [1, 2]
6. Modified /etc/fstab;
7. Edited my configuration profile:
Kernel: pv-grub-x86-64;
/dev/xvda debootstrapped distro;
root device * Standard: /dev/xvda;
8. Rebooted the server.
Everything looks right, but when I try to connect via Lish I see this error:
end_request: I/O error, dev xvda, sector …
end_request: I/O error, dev xvda, sector …
Buffer I/O error on device xvda, logical block …
Aborting journal on device xvda
EXT3-fs (xvda): error: ext3journalstart_sb: Detected aborted journal
EXT3-fs (xvda): error: remounting filesystem read-only
(If I change everything back, I'll be able to boot via Debian.)
I've also tried to use barriers=0 in /etc/fstab [3], but it didn't work out.
Debootstrapped distro: gNewSense Parkes
Kernel: Linux-libre 3.3.0
/etc/fstab:
/dev/xvda / ext3 noatime,errors=remount-ro 1 2
/dev/xvdc none swap sw 0 0
/boot/grub/menu.lst:
default 0
timeout 5
title Foo
root (hd0)
kernel /boot/vmlinuz-3.3.0 root=/dev/xvda ro quiet
Tell me if you need any additional info.
[1]
[2]
[3]
3 Replies
@retrograde inversion:
I have nobarrier in /etc/fstab for each ext3/ext4 entry, as well as rootflags=nobarrier in /boot/grub/menu.lst as one of the kernel params. Try that second thing as well.
Thanks! It helped.
There is another issue:
Now I can connect via SSH (which was configured by me), but I can't login via Lish.
Is it OK? I thought that Lish sits on top of VM so it can get access to any machine.
Should I set it up to have an ability to connect via Lish? Or it's just another way to restrict unauthorized access from the Manager?
BTW, I've read that it could be bad to have nobarrier option enabled because it may cause a loss of data. Is it right?
@peterthegreat:
Now I can connect via SSH (which was configured by me), but I can't login via Lish.
Is it OK? I thought that Lish sits on top of VM so it can get access to any machine.
Should I set it up to have an ability to connect via Lish? Or it's just another way to restrict unauthorized access from the Manager?
Lish should definitely work. A couple thoughts on this:
1. Check
2. Check /etc/inittab - for the section where it defines your terminals, the first line should have 'hvc0' instead of 'tty1'. (Comment out any lines for tty2 through tty6, you don't need them.) After doing this I found I had to disable Xenify Distro in the Linode Configuration Profile as well.