my debian is :
Asus A8N-VM(nforce 430) with maxtor sata2 200GB

when I first install the debian onto it, it's always hanged.
I google the error message and found that it can be solved by adding pci=noacpi like this:

title Debian GNU/Linux, kernel 2.6.15-1-k7
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-1-k7 root=/dev/sda1 ro pci=noacpi
initrd /boot/initrd.img-2.6.15-1-k7
savedefault

however, today when I got up, I found that my web server was down.
I ssh into it and the system turns into "read-only"
I can't edit any files.
The trouble thing is I even can't restart the debian.
When I type "shutdown -r now", it doesn't work.

At last, I have to turn off the power and turn on again.
Then the debian works normally again.

But it's the second time that it turned into "read-only filesystem".

I think it's the harddisk's problem.
How can I solve it?

Can anyone teach me how to restart it remotely when "shutdown -r now" doesn't work?

Thank you!

If shutdown -r now doesn't work, you basically have to pull the power on it. And if shutdown doesn't work, you do have major problems. Does dmesg show any errors, particularly ATA/IDE errors?

Because the server is not in my home, I want to reboot immediately when it turns into "readonly file system"
so i want to know if there is other method to reboot it remotely

here is part of the dmesg:
sata_nv 0000:00:0e.0: version 0.8
PCI: Setting latency timer of device 0000:00:0e.0 to 64
ata1: SATA max UDMA/133 cmd 0xE800 ctl 0xE482 bmdma 0xE000 irq 5
ata2: SATA max UDMA/133 cmd 0xE400 ctl 0xE082 bmdma 0xE008 irq 5
ata1: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4773 85:7c69 86:3e01 87:4763 88:407f
ata1: dev 0 ATA-7, max UDMA/133, 398297088 sectors: LBA48
ata1: dev 0 configured for UDMA/133
scsi0 : sata_nv
ata2: no device found (phy stat 00000000)
scsi1 : sata_nv
Vendor: ATA Model: Maxtor 6V200E0 Rev: VA11
Type: Direct-Access ANSI SCSI revision: 05
PCI: Setting latency timer of device 0000:00:0f.0 to 64
ata3: SATA max UDMA/133 cmd 0xDC00 ctl 0xD882 bmdma 0xD400 irq 5
ata4: SATA max UDMA/133 cmd 0xD800 ctl 0xD482 bmdma 0xD408 irq 5
ata3: no device found (phy stat 00000000)
scsi2 : sata_nv
ata4: no device found (phy stat 00000000)
scsi3 : sata_nv
SCSI device sda: 398297088 512-byte hdwr sectors (203928 MB)
SCSI device sda: drive cache: write back
hdb: ATAPI 40X CD-ROM drive, 128kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
SCSI device sda: 398297088 512-byte hdwr sectors (203928 MB)
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 sda4 < sda5 >
sd 0:0:0:0: Attached scsi disk sda
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting. Commit interval 5 seconds
EXT3-fs: sda1: orphan cleanup on readonly fs
ext3_orphan_cleanup: deleting unreferenced inode 2763494
ext3_orphan_cleanup: deleting unreferenced inode 2763493
ext3_orphan_cleanup: deleting unreferenced inode 2763492
EXT3-fs: sda1: 3 orphan inodes deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
Adding 3911816k swap on /dev/sda2. Priority:-1 extents:1 across:3911816k
EXT3 FS on sda1, internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda5, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.

In those messages, I see no problems or signs that anything is amiss. Why do you want to reboot immediately upon it going to read-only mode?

Last time ive had that happen to me it was a hard drive failure. Does that drive have SMART? if so try testing it with the smartmon tools

I think there is no error message because I had reboot it already?

I want to reboot it because in the read-only mode, my web server can't be run. My web server contains many php pages which needs to access mysql.

Here is the output of " smartctl -i /dev/sda"
Device: ATA Maxtor 6V200E0 Version: VA11
Serial number: V40B4H6G
Device type: disk
Local Time is: Mon Jul 24 00:18:53 2006 HKT
Device does not support SMART

So I think it doesn't support SMART.

smartmontools does not yet support SATA. The output of dmesg following an error would be more demonstrative, allowing us to (possibly) determine the cause of the problem.

Most likely, your hard drive is on its last legs.

but I bought it two months ago.
Then if it turns into "read-only" mode again, where can I check out the error msg or why it turns into "read-only" mode?

dmesg will show details on why it has switched to read only mode. Have you noticed any unusual sounds from the disk? You may also want to try using maxtor's tools and seeing if it can check the drive's performance.

I heard some people said maxtor's sata HD is not working quite well with nForce 430.
And actually, if I didn't add "pci=noacpi" to grub's config, it's hanged so frequently even when using aptitude.

Are there any maxtor's tools for debian?