BT5 R2 in Persitant USB boot error

I have the same error, too.
at first, i tried the "synch" command before shutting down.

it worked the first 2-3 times, then i get the error loop.
anyone knows how to fix this?

Quote:

---

Originally Posted by dafuq

Dear fjecp,

b.
I also had 'end_request: I/O error, dev fd0, sector xxxxx' while booting.
I solved that one by disabling 1.44 floppy in bios.

a.
I also have the 'Warning: Unable to find the persistent home medium' problem.
Found anything for that?
How do you hide the (boot)splash screen?
I press ESC but I'm paranoid that that actually cancels the current operation (like a Ctrl+C command).

c.
Also I have 'EXT2-fs (loop1) error: ext2_lookup: xxxxxxx inode referenced: yyyyy' problem.

What do you specifically type when you say you use 'the sync' command?

I noticed that logging off first and then type shutdown -h 0 reduced them to 7 or 8 lines indeed. (instead of endless lines).
Others suggest using poweroff instead.

I

---

I also have the same problem. I installed BT5 R2 on a 32GB flash drive. FAT32 was used with 4GB persistent storage. I used http://www.linuxliveusb.com/ install BT on the drive. Everything went well and after reading several post about how to increase persistent storage I was able to successfully make use of the remaining disk space using the tutorial http://www.pendrivelinux.com/create-...per-partition/. Everything went well until I updated backtrack using apt-get upgrade && apt-get update. I have the error found on the image below and can no longer use persistent mode.

https://dl.dropbox.com/u/34599277/20...2017.58.26.jpg

Quote:

---

Originally Posted by nulled644

I also have the same problem. I installed BT5 R2 on a 32GB flash drive. FAT32 was used with 4GB persistent storage. I used http://www.linuxliveusb.com/ install BT on the drive. Everything went well and after reading several post about how to increase persistent storage I was able to successfully make use of the remaining disk space using the tutorial http://www.pendrivelinux.com/create-...per-partition/. Everything went well until I updated backtrack using apt-get upgrade && apt-get update. I have the error found on the image below and can no longer use persistent mode.

https://dl.dropbox.com/u/34599277/20...2017.58.26.jpg

---

Please, have a look to my previous posts in this same thread. You will probably (and hopefully) find a solution to the problem doing similar things I did.

Good luck.

I found the same problems using a sd card. seems like while saving the data during shut down some process cant wait for the data to be written. a shame. without persistency unusable

I was having the exact same error messages, then I found this thread here on the forums and it worked perfectly. It was a bit of a long process to get it installed but now that it's done I am loving it. Hope that helps.

Quote:

---

Originally Posted by raymon432

I also experience similar problems after installing backtrack 5 with persistence to a 16 gb Sandisk usb. The first boot was ok and i logged out of kde with end session,then did poweroff from commandline. Afterwards when I try to boot get to the splash screen with continous error messages:

EXT-fs (loop1): error ext2_lookup: deleted inode referenced: 786458

When I press CTRL+C the "root@bt#" appears where one is supposed to enter startx, but the constant-error messages instantly reappears.
I used Unetbootin to create the persistent usb from the image. Strange that the first boot went ok. I do not want to disable floppy-drive in bios since I now only can boot from the live-dvd. The computer is an Acer travelmate from 2007.
Should there have been any changes made before booting out of the first session with the live-usb?

---

Please let me know if you figure this out I have the exact same issues on my compaq and all this is jibberish to me I m pretty new to this I also have system disabled due to load higher than 2.0 and wonder if thats not the cause aswell but do not understand this either damn Im lost. Please Help us.