Gleiche Problem
Hallo,
nach dem Update auf der neuen DSM 4.1 habe ich ebenfalls eine grauenhafte CPU Auslastung
fdisk -url hat folgendes Ergebnis gebracht:
DiskStation> fdisk -ul
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/sda1 256 4980735 2490240 fd Linux raid autodetect
Partition 1 does not end on cylinder boundary
/dev/sda2 4980736 9175039 2097152 fd Linux raid autodetect
Partition 2 does not end on cylinder boundary
/dev/sda3 9437184 1953520064 972041440+ fd Linux raid autodetect
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 256 4980735 2490240 fd Linux raid autodetect
Partition 1 does not end on cylinder boundary
/dev/sdb2 4980736 9175039 2097152 fd Linux raid autodetect
Partition 2 does not end on cylinder boundary
/dev/sdb3 9437184 1953520064 972041440+ fd Linux raid autodetect
Disk /dev/sds: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/sds1 63 625137344 312568641 c Win95 FAT32 (LBA)
Kann mir einer von euch helfen?