Do not use fsck on faulty hardware.
I would remove the drive attach it to another linux box with free storage
space on a file system larger than that of the whole damaged drive. Use
ddrescue to rebuild as much of the failed drive as possible them mount
the image produced from ddrescue and
2010/2/19 Slack-Moehrle mailingli...@mailnewsrss.com:
a hd in my server failed.
I noticed when I went to SSH in and get a copy of some files in /var/www/html
I tried to tar the files and I was told No, read-only file system.
I restarted and tried running FSCK manually (without -a or -p) and
Also, what would have caused this all of the sudden? This box has been
running fine for months.
Well, do you think that computer hardware lives forever?
They don't? /me stares at 486dx with a working floppy drive and working
floppies from the eighties and early nineties.
And I deal with
m.r...@5-cent.us wrote:
Also, what would have caused this all of the sudden? This box has been
running fine for months.
Well, do you think that computer hardware lives forever?
They don't? /me stares at 486dx with a working floppy drive and working
floppies from the eighties and early
On 2/19/2010 8:48 AM, m.r...@5-cent.us wrote:
Also, what would have caused this all of the sudden? This box has been
running fine for months.
Well, do you think that computer hardware lives forever?
They don't? /me stares at 486dx with a working floppy drive and working
floppies from the
a hd in my server failed.
I noticed when I went to SSH in and get a copy of some files in /var/www/html
I tried to tar the files and I was told No, read-only file system.
I restarted and tried running FSCK manually (without -a or -p) and I get inode
errors, short reads, etc.
I tried booting
On Thursday 18 February 2010, Slack-Moehrle mailingli...@mailnewsrss.com
wrote:
Also, what would have caused this all of the sudden? This box has been
running fine for months.
Every hard drive will fail eventually. Some take days. Some take decades.
Most fail somewhere in between those
7 matches
Mail list logo