I tried to update from kernel 3.7.10-antix.3-486-smp to 3.16.0-0.bpo.4-686-pae on raid 0 btrfs filesystem but it fails to boot. I've uploaded screenshots of loading screen and grub loading options.
I tried to use btrfs device scan, btrfsck --repair,btrfs check --repair btrfs-zero-log but they didin't fixed it.
Anyone have an idea how to fix it?
13 posts
• Page 1 of 1
-
Posts: 7
- Joined: 21 Sep 2015
-
Posts: 7
- Joined: 21 Sep 2015
#2
Also btw I'm using raid 0 for performance and more comfortable file managing and data safety isin't important for me on drives I use for raid 0 more important files I'l backup on non raid drive.
-
Posts: 325
- Joined: 04 Nov 2011
#3
My English skills are not sufficient for an exact explanation
1. grub2 can only"read-only" to btrfs
2. Is your GRUB version old (1.99-27 + deb) Currently 2.02 ~ beta2-28
3. antix at sdb1, kernel 3.7.10 ... which is (hd1, msdos1)
the 3.16 PAE kernel is with them set root = (hd4, msdos1) ? RAID?
Do not use a btrfs
use the current grub2 __{{emoticon}}__
1. grub2 can only"read-only" to btrfs
2. Is your GRUB version old (1.99-27 + deb) Currently 2.02 ~ beta2-28
3. antix at sdb1, kernel 3.7.10 ... which is (hd1, msdos1)
the 3.16 PAE kernel is with them set root = (hd4, msdos1) ? RAID?
Do not use a btrfs
use the current grub2 __{{emoticon}}__
-
Posts: 7
- Joined: 21 Sep 2015
#4
Thanks for the reply but updating grub didin't solved my issue the title(though I can still boot the old kernel) says sdb1 instead of sde1/sdd1 (devices are usb flash drive and micro sd card)because I haven't changed the title. Kernel(I mannualy edited menu entry because grub failed to detect the kernel but it detected the old one) is actually on raid sdd1/sde1(devices are micro sd card and usb flash drive).
same kernel boots up on other nearly same antix installation but with ext4 filesystem.
I want to use btrfs since it supports file system compression and raid
also I want to update kernel for more stable btrfs drivers and better performance.
same kernel boots up on other nearly same antix installation but with ext4 filesystem.
I want to use btrfs since it supports file system compression and raid
also I want to update kernel for more stable btrfs drivers and better performance.
-
Posts: 1,444
- Joined: 09 Feb 2012
#5
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://www.google.com/?gws_rd=ssl#q=linux+btrfs+fsck+died+with+exit+status+8"
linktext was:"https://www.google.com/?gws_rd=ssl#q=li ... t+status+8"
====================================
Thread: Fsck died on bootup exit status 8
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://ubuntuforums.org/showthread.php?t=1043160"
linktext was:"http://ubuntuforums.org/showthread.php?t=1043160"
====================================
linux software raid, raid levels, LVM, btrfs and Kali Linux
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://blog.sjas.de/posts/linux-software-raid-raid-levels-LVM-btrfs-and-Kali-Linux.html"
linktext was:"http://blog.sjas.de/posts/linux-softwar ... Linux.html"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://www.google.com/?gws_rd=ssl#q=linux+btrfs+fsck+died+with+exit+status+8"
linktext was:"https://www.google.com/?gws_rd=ssl#q=li ... t+status+8"
====================================
Thread: Fsck died on bootup exit status 8
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://ubuntuforums.org/showthread.php?t=1043160"
linktext was:"http://ubuntuforums.org/showthread.php?t=1043160"
====================================
linux software raid, raid levels, LVM, btrfs and Kali Linux
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://blog.sjas.de/posts/linux-software-raid-raid-levels-LVM-btrfs-and-Kali-Linux.html"
linktext was:"http://blog.sjas.de/posts/linux-softwar ... Linux.html"
====================================
-
Posts: 7
- Joined: 21 Sep 2015
#6
I've tried checking thoose links but I haven't found solution for my issue.
Anyone has any more ideas or perhaps I should try asking on btrfs irc or mailling?
Anyone has any more ideas or perhaps I should try asking on btrfs irc or mailling?
-
Posts: 307
- Joined: 23 Aug 2015
#7
I cannot think of any solution yet, but can you tell me which devices are set up as RAID0? There are also other kernel versions availabe now, 4.1 or liquorix 4.2. I didn't try RAID with btrfs myself.
-
Posts: 7
- Joined: 21 Sep 2015
#8
Devices are 64 gb micro sd card connected using micro sd to usb adapter 32 gb partition and 32 gb usb flash drive.I managed to solve boot up issue but I was getting parent transid failures,csum errors,filesystem was forced mounted read only
I've tried fixing it with btrfs rescue zero-log and it isin't mountable anymore.I'l try to recreate array I didin't had anything important anyway.
I've tried fixing it with btrfs rescue zero-log and it isin't mountable anymore.I'l try to recreate array I didin't had anything important anyway.
-
Posts: 1,444
- Joined: 09 Feb 2012
#9
That might account for the"9 times out of 10" symptom you described.
If the micro sd card is an older/slower Class2 or Class4 card, that might explain the suspected"timeout" issue I mentioned.
If your ports old/slow USB1.1, that might be the limiting factor instead.
All of them? Okay, well, first of all there's Steve, waaaay up there on the shelf... and Suzie, she's the cute l'il Maxxtor...
Seriously, how can you expect someone to know the answer?
According to the screenshots,"job control turned off"...so, the seemingly obvious answer is"none".
Does the grub entry consider UUIDs? If not, there's no guarantee that the same device will be assigned to"sde1" each boot.I mannualy edited menu entry because grub failed to detect the kernel but it detected the old one) is actually on raid sdd1/sde1(devices are micro sd card and usb flash drive).
That might account for the"9 times out of 10" symptom you described.
If the micro sd card is an older/slower Class2 or Class4 card, that might explain the suspected"timeout" issue I mentioned.
If your ports old/slow USB1.1, that might be the limiting factor instead.
???can you tell me which devices are set up as RAID0?
All of them? Okay, well, first of all there's Steve, waaaay up there on the shelf... and Suzie, she's the cute l'il Maxxtor...
Seriously, how can you expect someone to know the answer?
According to the screenshots,"job control turned off"...so, the seemingly obvious answer is"none".
-
Posts: 7
- Joined: 21 Sep 2015
#10
UUID Is specifed in grub,micro sd card is class 10 I think,usb port is 2.0
Both of the devices were in raid.
I deleted the array and tried to boot with mdadm soft raid at first it failed but I managed to make it bootable by regenerating mdadm.conf file and running while in chroot but then I had troubles with csum errors,parent transid errors and a huge list of other erros so I deleted that array and atm trying to do it(raid) with btrfs built in raid.
here are some portions from error log while I was trying to fix partition on mdadm( I think from btrfs check)
I've tried to use
root 5 inode 300565 errors 2001, no inode item, link count wrong
unresolved ref dir 188550 index 0 namelen 8 name f_000160 filetype 1 errors 6, no dir index, no inode ref
root 5 inode 300566 errors 2001, no inode item, link count wrong
unresolved ref dir 188550 index 0 namelen 8 name f_000161 filetype 1 errors 6, no dir index, no inode ref
root 5 inode 300573 errors 2001, no inode item, link count wrong
unresolved ref dir 188582 index 0 namelen 46 name https_people.directory.live.com_0.localstorage filetype 1 errors 6, no dir index, no inode ref
root 5 inode 300574 errors 2001, no inode item, link count wrong
unresolved ref dir 188582 index 0 namelen 54 name https_people.directory.live.com_0.localstorage-journal filetype 1 errors 6, no dir index, no inode ref
parent transid verify failed on 576012288 wanted 3603 found 3082
Ignoring transid failure
parent transid verify failed on 576012288 wanted 3603 found 3082
Ignoring transid failure
parent transid verify failed on 576012288 wanted 3603 found 3082
Ignoring transid failure
parent transid verify failed on 576012288 wanted 3603 found 3082
The full list was very long.
Both of the devices were in raid.
I deleted the array and tried to boot with mdadm soft raid at first it failed but I managed to make it bootable by regenerating mdadm.conf file and running
Code: Select all
update-initramfs -u -k all
here are some portions from error log while I was trying to fix partition on mdadm( I think from btrfs check)
I've tried to use
Code: Select all
btrfs check btrfs check --init-csum-tree,btrfs check --init-extent-tree, btrfs check --check-data-csum,btrfs check --repair , btrfs rescue chunk-recover ,btrfs rescue super-recover,btrfs rescue zero-log(after using it btrfs partition became unmountable so I deleted it afterwards)
I think running btrfs check --init-csum-tree was temporary fixing uncorectable csum erros detected by btrfs scrub
unresolved ref dir 188550 index 0 namelen 8 name f_000160 filetype 1 errors 6, no dir index, no inode ref
root 5 inode 300566 errors 2001, no inode item, link count wrong
unresolved ref dir 188550 index 0 namelen 8 name f_000161 filetype 1 errors 6, no dir index, no inode ref
root 5 inode 300573 errors 2001, no inode item, link count wrong
unresolved ref dir 188582 index 0 namelen 46 name https_people.directory.live.com_0.localstorage filetype 1 errors 6, no dir index, no inode ref
root 5 inode 300574 errors 2001, no inode item, link count wrong
unresolved ref dir 188582 index 0 namelen 54 name https_people.directory.live.com_0.localstorage-journal filetype 1 errors 6, no dir index, no inode ref
parent transid verify failed on 576012288 wanted 3603 found 3082
Ignoring transid failure
parent transid verify failed on 576012288 wanted 3603 found 3082
Ignoring transid failure
parent transid verify failed on 576012288 wanted 3603 found 3082
Ignoring transid failure
parent transid verify failed on 576012288 wanted 3603 found 3082
The full list was very long.
-
Posts: 307
- Joined: 23 Aug 2015
#11
@skidoo: Your humour(?) is lost in translation for me, sorry. __{{emoticon}}__
Sorry for the late reply (but your reply was late, too). IMHO it is a very exotic setup for RAID, especially RAID0. The drives should be more similar in their capabilities. It is your computer, so you decide. But I would simply advise to use an SSD or HDD for your system and only use it in RAID if you have a second SATA port.Eimant wrote:Devices are 64 gb micro sd card connected using micro sd to usb adapter 32 gb partition and 32 gb usb flash drive.I managed to solve boot up issue but I was getting parent transid failures,csum errors,filesystem was forced mounted read only
I've tried fixing it with btrfs rescue zero-log and it isin't mountable anymore.I'l try to recreate array I didin't had anything important anyway.
@skidoo: Your humour(?) is lost in translation for me, sorry. __{{emoticon}}__
-
Posts: 7
- Joined: 21 Sep 2015
#12
Thanks for the reply I found out that it seems like this problem affects only micro sd card and doesn't appear on usb flash drive.Perhaps I'l stick to single device for some time(found out that btrfs file system compression can improve performance even better then raid.How can I lock this thread?good luck all.
-
Posts: 307
- Joined: 23 Aug 2015
#13
You are welcome! There are numerous tweaks which can improve the performance of btrfs. New kernel, BFQ I/O schedulers - both available with Liquorix kernel, fstab option commit=300 or more (then it writes caches to the drive every 300 seconds = 5 minutes).