[EN] apt-get -f install

[laudire]

Hi all!
I am trying to run ' apt-get -f install 'and I get the following errors:

Code: [Select]


root@siductionbox:/home/rejean# apt-get -f install
Reading package lists... Done
Building dependency tree      
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
  linux-image-3.6-1.towo-siduction-686
Suggested packages:
  linux-doc-3.6
The following NEW packages will be installed:
  linux-image-3.6-1.towo-siduction-686
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
48 not fully installed or removed.
Need to get 0 B/22.0 MB of archives.
After this operation, 76.2 MB of additional disk space will be used.
Do you want to continue [Y/n]? y
Preconfiguring packages ...
(Reading database ... 127794 files and directories currently installed.)
Unpacking linux-image-3.6-1.towo-siduction-686 (from .../linux-image-3.6-1.towo-siduction-686_3.6-3_i386.deb) ...
dpkg: error processing /var/cache/apt/archives/linux-image-3.6-1.towo-siduction-686_3.6-3_i386.deb (--unpack):
 unable to create `/boot/System.map-3.6-1.towo-siduction-686.dpkg-new' (while processing `./boot/System.map-3.6-1.towo-siduction-686'): Read-only file system
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.6-1.towo-siduction-686 /boot/vmlinuz-3.6-1.towo-siduction-686
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.6-1.towo-siduction-686 /boot/vmlinuz-3.6-1.towo-siduction-686
Errors were encountered while processing:
 /var/cache/apt/archives/linux-image-3.6-1.towo-siduction-686_3.6-3_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@siductionbox:/home/rejean#


What could I do?

[towo]

unable to create `/boot/System.map-3.6-1.towo-siduction-686.dpkg-new' (while processing `./boot/System.map-3.6-1.towo-siduction-686'): Read-only file system

is saying all.

[laudire]

So I tried;

Code: [Select]


root@siductionbox:/home/rejean# chmod 744 /boot/System.map-3.6-1.towo-siduction-686
chmod: cannot access `/boot/System.map-3.6-1.towo-siduction-686': No such file or directory                                                    
root@siductionbox:/home/rejean#

[dibl]

Do you see some errors on boot, during mounting of filesystems?  I am guessing that you need to boot a live CD and run fsck on the partition that holds the OS.

[laudire]

No I don't see any errors at boot time ( just rebooted actually). It all started either when I was trying to follow the manual about installing nvidia, or during a 'apt-get dist-upgrade', not sure.
I just noticed during reboot that a check of the file system occured but everything said 'ok', no 'fail'.
P.S. I just booted into the Siduction live cd and did;

Code: [Select]


siducer@siduction:~$ fsck /dev/sda2
bash: fsck: command not found
siducer@siduction:~$ su
root@siduction:/home/siducer# fsck /dev/sda2
fsck from util-linux 2.20.1
e2fsck 1.42.4 (12-Jun-2012)
/dev/sda2: clean, 138948/686784 files, 1001046/2745856 blocks
which is my / partition.
Then I did one for my /dev/sda1 (/boot);

Code: [Select]


root@siduction:/home/siducer# fsck /dev/sda1
fsck from util-linux 2.20.1
fsck: fsck.ntfs: not found
fsck: error 2 while executing fsck.ntfs for /dev/sda1

and one for /dev/sda3 (/home)

Code: [Select]


root@siduction:/home/siducer# fsck /dev/sda3
fsck from util-linux 2.20.1
e2fsck 1.42.4 (12-Jun-2012)
/dev/sda3: clean, 1893/1281120 files, 210177/5119744 blocks
root@siduction:/home/siducer#

[laudire]

I went back to the initial problem and there is no such thing as the ones mentionned;

Code: [Select]


unable to create `/boot/System.map-3.6-1.towo-siduction-686.dpkg-new' (while processing `./boot/System.map-3.6-1.towo-siduction-686'): Read-only file system

here are the ones in my /boot folder;

Code: [Select]


root@siductionbox:/mnt/boot# ls -l
total 29832
-rwxrwxrwx 1 root root   117632 Dec 22  2011 config-3.1-6.slh.1-aptosid-686
-rwxrwxrwx 1 root root   124296 Jun 23 09:32 config-3.4-4.towo-siduction-686
drwxrwxrwx 1 root root    45056 Oct 12 21:12 grub
-rwxrwxrwx 1 root root 10501711 Oct  6 21:17 initrd.img-3.1-6.slh.1-aptosid-686
-rwxrwxrwx 1 root root 11185337 Oct  8 13:53 initrd.img-3.4-4.towo-siduction-686
-rwxrwxrwx 1 root root   176764 Oct 24  2011 memtest86+.bin
-rwxrwxrwx 1 root root   178944 Oct 24  2011 memtest86+_multiboot.bin
-rwxrwxrwx 1 root root  1484446 Dec 22  2011 System.map-3.1-6.slh.1-aptosid-686
-rwxrwxrwx 1 root root  1562633 Jun 23 09:32 System.map-3.4-4.towo-siduction-686
-rwxrwxrwx 1 root root  2508832 Dec 22  2011 vmlinuz-3.1-6.slh.1-aptosid-686
-rwxrwxrwx 1 root root  2642288 Jun 23 09:32 vmlinuz-3.4-4.towo-siduction-686
root@siductionbox:/mnt/boot#


[laudire]

Not sure I want to tackle installing nvidia yet but I did reinstalled Siduction, then I did ' apt-get update && apt-get dist-upgrade ' and there were no errors.

Oh! I also reformatted sd1 as ext4.

Should the following file have it's permissions changed?

Code: [Select]



-rw-r--r-- 1 root root  1602151 Oct  8 13:29 System.map-3.6-1.towo-siduction-686


[devil]

No, that lives in /boot and belongs rightfully to root.

greetz
devil

[laudire]

Thank you devil!

[dibl]

Not sure I want to tackle installing nvidia yet

There's no  "tackling" necessary.  Installation of the proprietary Nvidia driver is a few easy steps, exactly as stated in the manual.  Just follow the manual one time, and you are done for as long as you keep the OS.