[ solved ] Howto install it in HDD?

[tomlohaveModerator]

ok, i will test the shutdown script.

[tomlohaveModerator]

should be solved with commit r13683 http://hg.openbricks.org/openbricks/rev/aa01dcf37358

[akostadinovMember]

@tomlohave: thanks for looking into that problem. Is there a place with snapshot with your changes? Latest thing I can see on the download server is before this commit.

Unfortunately I couldn’t test the changes applying manually. The initrd I’m creating doesn’t work for some reason. I get an error root cannot be mounted. No idea if I’m doing something wrong editing the initrd image. I use these commands to extract/create:
unxz -c /mnt/tmp/initrd | cpio -i # extract initrd
find | cpio -H newc -o | xz > ../initrd # create initrd

btw other linux distros always sync before actually shutting down/rebooting the machine just to be sure everything is done to preserve user data. Another suggestion I have is to have e2fsck before mounting casper-rw. I think it would make the whole sthing much more reliable.

Regards and Merry Christmas!

[craigusMember]

As far as I can tell, http://download.openbricks.org/geexbox-devel-20111224-r13686-i386.iso has the fix built in.

[akostadinovMember]

Thank you for download link. But I don’t see any difference with this build. I tried to debug the problem. I entered emergency mode with “systemctl emergency”. I could “mount -o remount,rw /” but I cannot “mount -o remount,rw /.data”. It says it’s in use. I can’t see anything using it with fuser. Perhaps some weird behavior because of aufs?

When shutting down I see error messages that loop0 and loop1 are busy and cannot be umounted. Also lots of failed to write sector ### on ext2 filesystem. But I know filesystem is ok. It’s a newly created one and I have run a badblock test on the HDD so I know there are no physical disk issues. Any ideas how to fix or debug further?

[tomlohaveModerator]

interesting i have testing this 10x with a ntfs paartition containing rootfs and casper-rw file and it was ok. No error
i will test with sync … No other idea for now.

[tomlohaveModerator]

can you post the result of command line (if you can boot) dmesg ?
Thanks
retrying today and i’m unable to break my casper-rw file under a ntfs partition

[akostadinovMember]

@tomlohave, by saying you cannot corrupt your casper-rw do you just mean that it works or is it cleanly umounted? When I copy my casper-rw to a linux machine and run e2fsck, it tells that it was not cleanly umounted. I guess it is very environment and usage specific after how many unsuccessful umounts a filesystem breaks but it is inevitable to break at some point.

I can copy the output to a flash drive and send it later today. What is an appropriate place to put the output, pastebin?

just FYI after some more observations I could see some errors at the beginning of shutdown process:
systemd[1]: .root.mount mount process exited, code=exited status=1
systemd[1]: .data.mount mount process exited, code=exited status=1
systemd[1]: .squashfs.mount mount process exited, code=exited status=1

Then at some interval kernel prints IO error messages about loop1 [1]. Could it be that systemd screws the .root mount where casper-rw resides and it is impossible later to perform a clean umount?

Unfortunately messages move too fast after this point in time and I can’t use scroll lock to stop them hence can’t see a big part pf the log :/

Regards.

[1] I’m inserting “sh” lines into /run/initramfs/shutdown to have stop points where I can inspect what’s going on. When I’m staying on such shell called by /shutdown I see the kernel IO error messages about loop1.

[tomlohaveModerator]

forgot my request, problem is gone …
i was able to reproduce it so now i can work on it

[akostadinovMember]

@tomlohave, any hope this can be fixed? Is this a problem only for NTFS?

[rubikiMember]

e2fsck ? good. learned a new command. fixed many errors.

[akostadinovMember]

@rubiki, what are you trying to say? Did you read the thread?

[krestianMember]

I am having the same issue (ext2_lookup: deleted inode referenced and then stall on boot) on an HDD install using unetbootin… here’s my specs:
- CPU is an AMD Duron 800
- RAM is 256 MB
- Graphics Card is Nvidia GeForce 2 MX400
- HDD is SATA connected to a PCI SATA card based on VIA VT6421 / also tried on an HDD directly connected to PATA (regular IDE) on-board controller with same results.
- persistent is set to 512 MB, or 256 MB, with same results.

My journey began when GeexBox didn’t like my video card so I need to install the old xf86-video-nvidia-old_96.43.20-1_i686.opk driver first. What I have noticed after countless attempts is that GeexBox gives me the same deleted inode referenced errors even without rebooting…. after installing the old driver and hitting Ctrl-D I get the same. I have never been able to fully boot it in this machine.

BTW… If i don’t “opkg remove xf86-video-nvidia” first, installing the old driver does not complain about dependency clash, and does indeed seem to load upon Ctrl-D. The other way around, I have to force-overwrite, but either way I get stuck on the deleted inode referenced scenario.

[krestianMember]

Sorry forgot one spec… both drives formatted to NTFS. Casper file also copied to root (C:\). I can confirm Casper is being written to, or at least updated, because Windows shows a newer last-modified timestamp for the file at C:\

[tomlohaveModerator]

@krestian : please test devel iso : http://download.openbricks.org/
(take the latest). You shouldn’t need anymore xf86-video-nvidia-old
but (yes there is a but …)
read on NTFS partitions is well supported, write not very good ….

[Author]

Posts