Hi folks

 

I've problems to perform a clean shutdown of the UnRaid server, since the update to 4.5.6

After I hit the power down button in the GUI I get the following message of the Unraid server.

 

"mount can't find / in /etc/fstab or /etc/mtab"

 

What I also recently changed:¨

I replaced the last IDE harddrive with a SATA harddrive.

 

My system consists now of the following hardware:

- ASUS M2N68-AM PLUS

- AMD Sempron 3000+

- 2 Promise SATA controllers (300 TX4 and 150 TX4)

- 9 SATA harddrives

 

The overall performance is in my opinion slow (i.e. drive replacement < 12'000 KB/sec)

I added the syslog file. Could someone please help?? 

 

Thanks, Ulan from Switzerland

syslog.txt

Your speed issue is your use of the PCI Bus. I think you have at least 8 drives on the PCI Bus via 2 Promise Controllers. That is your speed issue. The PCI Bus is a shared bus with a maximum upper limit of 133 MB/s bandwidth. With 8 drives on it, that leaves a maximum theoretical limit of 16.6 MB/s ( 133 split by 8 drives) in performance limited situations: parity builds, parity checks, failed drive situation, drive rebuilds, simultaneous writes, and simultaneous reads.

 

Please read the following posts/threads to further understand the issue:

http://lime-technology.com/forum/index.php?topic=7520.msg72845#msg72845

http://lime-technology.com/forum/index.php?topic=7526.msg72896#msg72896

 

 

Along with the speed issue, you also have larger issues with your disks that were once installed on a Gigabyte motherboard or similar system to cause an HPA infection on at least 3 of your drives. http://lime-technology.com/wiki/index.php?title=UnRAID_Topical_Index#HPA

 

Oct 27 03:01:46 Tower kernel: ata1.00: HPA detected: current 2930277168, native 18446744072344861488

Oct 27 03:01:46 Tower kernel: ata1.00: ATA-8: ST31500341AS, CC1H, max UDMA/133

Oct 27 03:01:46 Tower kernel: ata2.00: HPA detected: current 976771055, native 976773168

Oct 27 03:01:46 Tower kernel: ata2.00: ATA-7: SAMSUNG HD501LJ, CR100-05, max UDMA7

Oct 27 03:01:46 Tower kernel: ata4.00: HPA detected: current 976771055, native 976773168

Oct 27 03:01:46 Tower kernel: ata4.00: ATA-7: SAMSUNG HD501LJ, CR100-05, max UDMA7

 

 

Thank's for the fast reply.

Indeed, the first motherboard that I used was a Gigabyte. I replaced it with the ASUS.

I have to figure out the HPA problem, I didn't know about that.

 

Any hints why the server doesn't shut down properly?

 

Thanks!

 

Ulan

Thank's for the fast reply.

Indeed, the first motherboard that I used was a Gigabyte. I replaced it with the ASUS.

I have to figure out the HPA problem, I didn't know about that.

 

Any hints why the server doesn't shut down properly?

 

Thanks!

 

Ulan

The server will not shut down if it is unable to un-mount the disks.  Disks cannot be un-mounted if they are busy.

Disks are busy if they are in use, either by having file on them open, or by being the "current" directory for a process.

 

For example, if you log in and change directory to /mnt/disk1, then disk1 will be busy since it is your current working directory.

If you were to start a process while there, that direct willl be the current working directory for that process.  That too would prevent the disk from being un-mounted until the process is terminated.

 

So... stop any add-on programs you might have started, log off any telnet sessions, and then you should be able to shut down the server.