Gustin Johnson wrote:
> Also, the libxine is being removed because aptitude has detected it as
> being unused.  If this is not desired you can always reinstall it or
> mark it to be held.

It might be, that I compiled something that isn't recognized by the
package management, but needs libxine. If aptitude would recommend to
remove it for my experimental Lenny, I would agree, but not for my
stable* 32bit and 64bit Studio 2.1 'Etch'es. I make mistakes, but I also
keep some of my Linux stable ;). *stable excepting the hardware trouble
for audio productions with any Linux.

Okay, I could reinstall it, you're right and even if I don't know how, I
maybe can keep it by using aptitude. Instead I run parted from the Paldo
Live-CD and hat was what I did some minutes ago, see the attachment.

This is everything I did:

[pa...@virgin:~]$ mkdir /mnt/hard_disk
mkdir: cannot create directory `/mnt/hard_disk': Permission denied
[pa...@virgin:~]$ su
Password:
su: Authentication failure
[pa...@virgin:~]$ su
Password:
[r...@virgin:/home/paldo]# mkdir /mnt/hard_disk
[r...@virgin:/home/paldo]# chown paldo /mnt/hard_disk
[r...@virgin:/home/paldo]# mount /dev/sda9 /mnt/hard_disk
[r...@virgin:/home/paldo]# ls -l /dev/disk/by-id | grep Intenso
lrwxrwxrwx 1 root root  9 2009-03-10 01:32 
usb-Intenso_Rainbow_09012200230519-0:0 -> ../../sdc
[r...@virgin:/home/paldo]# dd if=/dev/zero of=/dev/sdc
dd: writing to `/dev/sdc': Input/output error
18417+0 records in
18416+0 records out
9428992 bytes (9.4 MB) copied, 1.618 s, 5.8 MB/s
[r...@virgin:/home/paldo]# killall dd
dd: no process killed
[r...@virgin:/home/paldo]# parted /dev/sdc
GNU Parted 1.8.8
Using /dev/sdc
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted)                                                                  
(parted)                                                                  
(parted) print                                                            
Error: /dev/sdc: unrecognised disk label                                  
(parted) q                                                                
[r...@virgin:/home/paldo]# dd if=/dev/zero of=/dev/sdc count=1 step=512
dd: unrecognized operand `step=512'
Try `dd --help' for more information.
[r...@virgin:/home/paldo]# dd if=/dev/zero of=/dev/sdc bs=512 count=1
1+0 records in
1+0 records out
512 bytes (512 B) copied, 0.00999582 s, 51.2 kB/s
[r...@virgin:/home/paldo]#



*Hi Gustin* :) *hi Ross* :)

I run dd and immediately there was the error, anyhow, the USB stick's LED was 
flashing, that means dd did write or tried to write to the stick, with or 
without success.

Running top in another terminal there was no dd, but
3258 paldo     20   0  233m  16m  11m R    5  0.9   0:14.65 gnome-terminal
in pool position, maybe because dd was working.

I started at <= 1:42 AM o'clock paldo-live-cd-time, the LED was still flashing 
when I run killall dd at 2:00 AM and it was falshing after that.

I planed to run '# cfdisk', '# mkfs.vfat /dev/sdc' and '# parted /dev/sdc 
print'. Instead I only run # parted /dev/sdc, while the LED was flashing at 
2:06 AM. Oops, I've forgotten to keep in mind that I need to add 'print'. 
Ctrl+C didn't stop parted or the flashing, but 'print' or Ctrl+D stopped the 
flashing and the error was displayed.

Okay, it's clear that it will take a long time to overwrite each byte on the 
USB stick, but I didn't wait, because I wonder that there was an error.

After my office work I was tired, that's why I didn't try to recover the IDE 
drive, a good decision, because I made mistakes when I tried to repair the USB 
stick, but reading again my notes in longhand, I didn't make any mistakes 
before the USB stick and the IDE drive failed and I wasn't tired when the 
devices get broken, but before each of the devices failed, I run the beta3 
installers partitioner.

Okay, a mistake like 'step' seems to be strange, but it won't, if you know a 
lot of OSs and program languages.

Independently of what was the cause when the devices failed (me or anything 
else) and independently of my mistakes today, there is one question: What might 
be the cause for 'dd: writing to `/dev/sdc': Input/output error'? Why seems dd 
to be fine when I only overwrote the MBR?

I'll stop doing anything now, I'm to tired, I made mistakes, even if I didn't 
made any serious mistakes.

I need to reboot into my 'office suite Lenny' and then into my stable 64 Studio 
2.1 Etch 64bit. I won't do anything, but (surfing) and run '# dd if=/dev/zero 
of=/dev/sdc' and let it run for hours ;).

Cheers,
Ralf

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
64studio-users mailing list
[email protected]
http://lists.64studio.com/mailman/listinfo/64studio-users

Reply via email to