You are not logged in.
Pages: 1
Hi all,
I recently installed Arch Linux on one of my desktops and have been noticing the "superblock could not be read" error on some of the bootups. It doesn't happen all the time, only sometimes. I don't know what's causing it or why it's happening. Here is a picture of the error:
Here is a picture of my /etc/fstab:
Sorry for the poor quality images. My phone was the only camera I had available at the time.
Last edited by solarwind (2010-04-18 09:14:09)
Offline
reading that i have exactly the same problem, sometimes, but it all started since i set up my arch box with 64bit and ext4, nevery had that kinda of error with ext3, so could this be ext4 related, or faulty hardware?
Offline
reading that i have exactly the same problem, sometimes, but it all started since i set up my arch box with 64bit and ext4, nevery had that kinda of error with ext3, so could this be ext4 related, or faulty hardware?
I am running 64 bit on ext4 as well.
Update: I did some searching and updated my fstab to use UUIDs instead. I tried a few bootups and I'm not getting the error anymore. I'll post another update.
Offline
iirc i have UUIDs in my fstab, but can't confirm that right now thus i'm not at my flat, but will take a look at that in a few hours!
Offline
just checked my fstab and as you said, there are no UUID entries but the /dev/sd* entries, gonna change that and try again!
Offline
Pages: 1